[Barry]

Hi – I’m sorry you’re facing difficulties.

It looks like you already ran through our standard troubleshooting steps which is awesome – they often make it possible to quickly identify any conflicts that may be present:

YES, I’ve deactivated all other plugins to check for a plugin conflict.
YES, I’ve reverted to the 2011 default WordPress theme (with other plugins still deactivated) to check for a theme conflict.

Can you confirm what the outcome of that test was – did everything work as expected once you deactivated all the other components and did you uncover any conflicts?

[Barry]

Hi wallyglenn,

Yes that should be possible – in broad outline this is the sort of strategy I’d suggest here:

• You need to “listen” for the widget being displayed … the widget_display_callback hook will effectively allow you to do this and to differentiate between different instances of the same widget – letting you target just one of them
• Once you identify the widget you need to modify you can set up a further filter using the tribe_events_list_widget_query_args hook – this makes it possible to alter the arguments used in the event list widget query
• Alter the query by adding a tribeHideRecurrence query variable (and set it to 1)
• Don’t forget to clean up! You’ll need to remove your filter callback to avoid impacting on any other events list widgets

I hope that helps 🙂

 

[Barry]

Hi – great question!

A lot depends on the actual calendar software being used by each person. Often though they can simply make use of the ical feed, see this example:

http://wpshindig.com/events/upcoming/ical/?ical=1&tribe_display=list

Depending on the calendar app, it may be they need to change the http:// segment at the start to webcal:// for this to work.

Does that help?

[Barry]

I’m sorry your experiencing difficulties.

Even if the URL in our license key page seems to match your own, can you try deleting it and then return to your website and try to reactivate?

If that doesn’t work, can you confirm (by private reply if you prefer) which URL this relates to?

Thanks!

[Barry]

Hi, I’m sorry you’re experiencing difficulties.

You won’t be able to delete events via FTP, I’m afraid. Just like pages and posts, events live in the database rather than each being represented by an individual file.

Can you confirm where you are seeing the 505 error? Is it only on event-related admin pages, or is it across the entire admin environment?

 

[Barry]

Hi!

Looks like your theme’s stylesheet sets some rules that impact on lists like the one in this widget. A few extra CSS rules should straighten things out, though:

.tribe-events-list-widget ol {
margin-left: 0;
}

.tribe-events-list-widget ol li {
border: none;
padding-left: 0 ;
}

You can add these to a custom tribe-events/tribe-events.css stylesheet within your theme directory – more details on setting this up can be found in our Themer’s Guide.

I hope that helps 🙂

[Barry]

I’m sorry to hear that, Cal, but please feel free to email us at pro (at) tri (dot) be with your request. Please also include a copy of the purchase receipt and a link to the thread, just to help give some context to the team member handling your request.

Thanks again and I’m sorry it didn’t work out on this occasion.

[Barry]

Hi!

Why not just create an option to show only 1 instance of recurring events in search results. (why only list-view?)

Generally speaking it doesn’t make as much sense to apply this setting to views like month view: applying this setting across the board therefore could cause some confusion which is why it is applied only to list-style views.

Regardless, is it possible to at least provide us the logic / code that can be leveraged in a search query to exclude recurring events except a single instance?

It actually seems to do pretty much this already – if you enable the setting you referenced then you should only see one instance of a given recurring event.

The only potential problem I see is that if the sequence of recurring events started in the past then it may be the oldest event which appears, rather than the next upcoming event. Just to clarify, is that the problem you need to resolve here, or are you finding the setting is no impact whatsoever (and are seeing multiple recurring events)?

[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread (and so it will no longer be monitored by staff). If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

Interesting that the theme requires default permalinks.

Really, other than following the same course of action as you already did (deactivating day view) I could only suggest waiting until we deliver a fix in a future release (and we’ll do our best to post an update in here when we do so).

Thanks again!

[Barry]

Hi!

I’ve edited the default edit-event.php as you suggested and it worked just fine. My only concern with that approach is that the change could revert during future upgrades. Correct me if I’m wrong, but I was under the impression that was why it was originally suggested to go the other route and place that file within the theme directory.

Sorry for any confusion – I didn’t actually mean that you should edit the default template file itself, rather when I suggested replacing it with the (current) default one I meant you should make a fresh copy and then re-apply the change.

In other words, this should still be done from within your theme’s tribe-events directory and not by modifying the original plugin template itself.

Does that clarify things?

[Barry]

I don’t see why not.

For my own interest though (in case the problem is something other than I understand it to be) can I ask if this is indeed something you/your client only see when manually resizing a browser window on a desktop machine? Or do you also see this when you open the web page up in a device that anyway has a small screen size?

[Barry]

Definitely a nice idea (and currently possible, in fact, as a customization that listens for 404s being set on events pages and redirects to some other page or post).

I’m a little uncertain as to how much uptake there would be for such a feature if it were “baked in” but certainly if you post it on UserVoice – and of course you are also welcome to post any further suggestions with regards to this issue in general or any other topic – we’ll monitor the number of votes it is given by the community and give it our consideration.

At this point though I’m not sure we can do too much more in the short term and will close this thread, but as ever please don’t hesitate to create new threads as needed if we can help with anything else.

Thanks again 🙂

[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

No problem. I’ll go ahead and close out this thread but I’ve linked it to the bug report (on our internal tracker) and we’ll do our best to post an update once a fix is in place.

Thanks 🙂

[Author]

Posts