[Barry]

That seems like a great idea and I’ll log it so we can potentially roll this into a future release. In the meantime, you might be able to use some code like this (which you could add to your theme’s functions.php file):

add_action( 'tribe_pre_get_view', 'occassionally_kill_pro_title_filter' );

function occassionally_kill_pro_title_filter() {
	remove_action( 'tribe_pre_get_view', 'occassionally_kill_pro_title_filter' );
	if ( ! tribe_is_photo() ) return; // You could extend or further limit when this runs
	remove_filter( 'tribe_get_events_title', array( TribeEventsPro::instance(), 'reset_page_title'));
}

Does that help here? (… and thanks for reporting this issue!)

[Barry]

Hi Loakine,

Sorry you’re facing difficulties here. I wonder if you might be hitting an issue with duplicate recurring events: in the first instance can you try using the cleanup plugin as documented here and see if that alleviates the situation?

Let me know how you get on!

[Barry]

Hi – I’m sorry you’re experiencing difficulties. That’s definitely an odd problem.

I do see you already tried deactivating all other plugins and switching to a default, unmodified theme: can you confirm what if any impact that had on this problem? If it resolved the issue, were you able to identify anything – your theme, or perhaps a social media plugin – as conflicting? I do for instance see some extra code relating to Facebook being injected and that appears to be causing the breakage.

As an extension of that, do you have any customizations such as snippets in your theme’s functions.php file or any custom templates within a tribe-events subdirectory in your theme (and if so can you try temporarily removing or disabling them)?

Let me know how you get on!

[Barry]

Excellent – glad you figured it out (and thanks for sharing the solution) 🙂

[Barry]

You have exceeded your daily request quota for this API.

That would definitely explain it!

So to answer your question about when a request is made to Google – basically, any time a venue is created or a change in the geoaddress (the _VenueGeoAddress post meta field) is detected it connects in order to update the coordinates. If you do a batch import of a large number of events, then, yep it’s not impossible you’d exceed the free daily limits.

Does TEC also make requests to Google anytime a user uses the map view or location search via the events bar? We have about 2.5 million Page Views/month, so that’d make a big difference.

Well, above and beyond queries used to get venue coordinates, a map is of course being embedded on various pages which might be relevant here especially given the high number of page views you’re describing. Typically this is dynamic and not impacted by caching, so you can see how the numbers might add up here.

We have an account with MapQuest. Given that, is it possible to change the source (from Google to MapQuest) that the geocoordinates are pulled from when an event is submitted/created?

I’d definitely view that as an advanced customization – the best advice I can really give here is to look at and study the actions and filters used by the existing system. Take a peak at the TribeEventsGeoLoc constructor (in events-calendar-pro/lib/tribe-geoloc.class.php) – you can build up a picture of how and when it queries Google for geodata.

Potentially, you could remove all of those callbacks and replace them with your own in a system geared toward integrating with MapQuest.

I hope that helps – and good luck 🙂

[Barry]

I certainly can do so (please share them as a private reply).

Without wanting to sound too alarmist, though, please backup before providing access and note that we cannot accept responsibility for any issues arising from our logging in and accessing the admin pages of your site (initially, of course, my intent is only to take a look).

Thanks!

[Barry]

Unfortunately, Series Engine is known to conflict and this sounds very similar to issues others have experienced.

We did obtain a copy in order to try and replicate this issue but, unfortunately, were unable to do so. Is it possible to switch from Series Engine to a different, comparable plugin?

[Barry]

Is it possible to have the month view default on the desktop version and have the list view for the mobile view?

Switching dynamically between view types is possible as a customization, certainly – and at least for a straightforward implementation many of the tools you need for this are already baked into WordPress itself and also The Events Calendar:

• wp_is_mobile() (detect if the visitor is using a mobile/handheld device)
• TribeEvents:get_event_link() (find the correct URL for a given type of event view, like the upcoming events list)
• wp_safe_redirect() (move the visitor to a different URL)

So building something on top of those functions is definitely one possibility.

Since it seems to be a theme issue what should I look into to fix? Inovado is a responsive theme and the website was launched earlier this month and is now live.

It’s difficult to say – but let’s cover a few more basics first of all just in case there’s a simple answer we’ve missed:

• Do you have any customizations at all (such as snippets in your theme’s functions.php file relating to The Events Calendar or even a tribe-events directory containing custom templates)? If so, can you try removing them and see if that makes a difference here?
• Can you additionally try switching to a different template via the Events → Settings → Display admin screen and see if that helps?

Thanks – and let me know how you get on 🙂

[Barry]

Great – thanks Simon.

I’ll go ahead and close this thread but of course if we can help with anything else please don’t hesitate to create new threads as needed 🙂

As an aside: if you have a moment and would like to leave a review of your experiences so far that would be fantastic and much appreciated.

[Barry]

OK – glad you figured everything out!

[Barry]

Awesome 🙂

[Barry]

Thanks Bill – looking at your other thread though it does look though like this turned out to be the result of a conflict with your theme:

I use the headway drag and drop theme, I changed it to twenty twelve and tested it. It worked like it was suppose to on twenty twelve. So it is for sure something with my theme.

Thanks for you help

kris10haley: it’s not impossible it’s a conflict in your case, too. The basis of determining this is to deactivate all other plugins and use a default and completely unmodified theme and see if the same problem occurs.

Of course, given the nature of the problem, leaving your live site in that state may not be feasible or may simply be an unattractive proposition 🙂 … but if perhaps you could set up a test site (could be as simple as a fresh installation of WordPress in a subdirectory) and see if you can replicate the issue there – when running only our plugins – that would be great.

If you find everything is fine under those conditions, start adding the same stack of plugins/theme that you have on your live site – by a process of trial and error we should be able to find the culprit.

Is that viable here?

[Barry]

It did cause some new problems, as my calendar stopped working all together.

That’s not good 🙁

Can you provide a little more detail though – was your site completely inaccessible, including the front page and admin screens? Or was the problem limited to all other pages, etc?

With the default permalink, the event link would be something like: http://www.hoofdkwartier25.nl/?tribe_events=eventname
with ptetty permalinks, it became ‘www.hoofdkwartier25.nl/event/test-me-2′. However, I could still find events under the old name, including new events I made.

Right – so generally speaking using pretty permalinks doesn’t mean you can’t also use default permalinks. That said, I’m not sure I understand what the actual problem is on a practical level – can you clarify/illustrate with an example?

[Barry]

Hi – thanks for confirming.

I can definitely see what you mean. I think though a problem here is that some limitations are imposed by the Eventbrite API: when we pull in the event data it is definitely possible to determine that the ticket visibility is hidden – so potentially we could choose not to record the prices of any hidden tickets.

The catch though is that, best I can tell, we are unable to retrieve additional data surrounding the ticket visibility – like when exactly the ticket once again becomes visible – without implementing a significantly more complicated mechanism with challenges and possibly shortcomings of its own.

So, it seems like a slightly sticky situation here and we’re to some extent at the mercy of the Eventbrite API. Given that, what would you like to see here (bearing in mind we’ll need to balance up any changes with what others in the community may like)?

I can’t make any guarantees but we’d be interested in hearing your thoughts here and if we can reasonably accommodate them we will try our best to do so 🙂

[Barry]

Excellent!

I’ll go ahead and close the thread since it looks like you’re all sorted.

If you happen to have a moment though and would like to leave some feedback on our review page that would be awesome – it’s always really useful to hear about people’s experiences with The Events Calendar 🙂

[Author]

Posts