[Barry]

OK … I mean to me, both the main events page at http://happinessis.co.za/events/ and one of your single event pages like http://happinessis.co.za/event/herbs-for-animals-foundation-hfa1/ look fine. So my understanding is that the problem you are describing only surfaces when you use the Default Events Template.

Is that correct and, if so, is there a reason you can’t simply keep using the Default Page Template? I could be misunderstanding you of course, please just let me know if so.

Thanks!

[Barry]

Thanks for sharing those details: yes, I can envision there being problems under those circumstances – and we do have an issue on the tracker to address just this point. Ordinarily we don’t recommend tampering with core plugin code but in this case, if you feel comfortable doing so, you might be able to get some relief here by editing the following file:

events-calendar-pro/lib/tribe-geoloc.class.php

The method we’re interested in is TribeEventsGeoLoc::estimate_center_point() which lives in lines 723-764. Within that if you look for the following line:

set_transient( self::ESTIMATION_CACHE_KEY, $data, 5000 );

This sets the number of seconds that the geographic centre is cached for. Changing 5000 to something like 604800 (one week) or 2419200 (one month) would result in this running less frequently – and if your events generally take place in the same area then that is probably a valid way to go.

set_transient( self::ESTIMATION_CACHE_KEY, $data, 604800 );

The major downside to editing core code is of course having to restore changes after updates, but though I can’t offer up any guarantees I’d like to think we will have a better solution (at least so you can set up a filter to achieve the same thing) available in one of our next releases.

Thanks again – and apologies for the inconvenience in the interim.

[Barry]

I’m glad you got the notice up 🙂

Yes, troubleshooting on a dev or testing site is by far preferable if you can also replicate the problem there. Just to clarify, yes, I was commenting that the body_class() issue (which commonly causes something similar to what you are experiencing) does not seem to be the problem here – instead it seems to be that something is causing the date field in the Tribe bar to be populated.

I think the best thing at this point would be to see if the team over at iThemes can think of anything, but please do post back here with the results of that (even if there is nothing further they can do).

Thanks!

[Barry]

I’m sorry you’re experiencing this issue.

Yes, there is a conditional that might be helpful and that is tribe_is_month() – you might alternatively use the setting we provide in the Events → Settings → Display admin screen which lets you add some content to show above event pages.

To the problem at hand, I visited your site and a common reason for this problem (a lack of body_class support in themes) doesn’t seem to be the problem. Instead, I notice that when I try to page forward a month the tribe date field is populated with “2014-02-06” (Feb 6) and that value takes precedence over the requested month.

I’m not sure why that is, but it would be well worth running through our standard steps and deactivating all other plugins and switching to a default, unmodified theme – then checking if the same problem still takes place. Please note if you are using a caching plugin you should take especial care when troubleshooting to ensure it has been fully deactivated (refer to the plugin vendor’s instructions – basically though, deactivating a caching plugin, if you have one, does not guarantee that all of its effects will instantly stop).

Let us know!

[Barry]

Hi!

We are aware that query can be a fairly intensive one, and so its result is actually cached so that it doesn’t need to run on every single page load. It’s role is essentially to calculate the geographic centre of all events that have geolocation data attached to them (so that the map in map view can be appropriately centred, etc).

I would note that we may anyway be revising this as it currently pulls in events that have since passed or are not published – and that may be part of the reason you are hitting this issue.

We’d certainly be interested to know how many events you have that might cause such a long delay, though – can you provide even an approximate figure?

[Barry]

(I’ll move this out of presales and into the WooCommerce Tickets forum first of all, as it looks and sounds like you have already made the purchase 🙂 )

Also My events have a set number of allowed people but I want to sell Adult and Child tickets at different prices. In Woo Commerce this is done using the variable product feature. Woo Tickets doesn’t seem to support that either. Am I correct?

Yes, that is correct. We don’t directly support product variants or “pooled inventory” at this time, but it’s certainly something we are considering introducing.

Is there any way to put adult tickets for one price and child for another maxing out the total inventory of both combined?

Right now I’m afraid there is nothing baked into WooCommerce Tickets itself to facilitate this. I can fully appreciate this is frustrating, but we are investigating both these items as candidates for future improvements.

[Barry]

I can think of no reason why that wouldn’t work, certainly we haven’t seen any reports to the contrary.

[Barry]

That is strange.

Do you find that whenever you create a new venue this behaviour occurs? Is it only when you create a venue from within the event editor? If so, trying this with no other plugins and only a default theme running would definitely be a worthwhile test. In the meantime, with any affected venues, you should (hopefully!) be able to edit the slug and change it to something suitable.

Let us know!

[Barry]

Hi – great question! This guide might be useful here (the section on the TRIBE_DISABLE_SHOP constant in particular). Does that help?

[Barry]

Hi!

That’s an interesting problem. Would it be possible for you to create a custom translation, where each translated string contains the text in both languages, by compiling .po and .mo files (like regular single language translations)? That way you ought to catch pretty much everything including the string you are currently missing.

Though it’s beyond what we can do here to coach you through using POEdit (or a comparable tool), there are various resources on the web that run through how to do this.

Does that help?

[Barry]

Hi – sorry for the delay.

When I visit your main events page (which I’m taking to be /events/) I don’t see quite that problem. Can you confirm if this has since been resolved or else point to an example of the issue?

[Barry]

This reply is private.

[Barry]

This reply is private.

[Barry]

It’s important to have, in terms of days, the time for an event and event occurrence to roll off. Example, I may want to show an event that has passed two weeks ago. But for a weekly occurrence, I want it to roll off the next day.

OK – however this sort of thing is likely to remain the preserve of customizations, as not everyone would find that desirable. Though what I would recommend is putting your thoughts together and posting this as a feature request on UserVoice – that way others can endorse or otherwise comment on the idea (and we’d gain a better sense of whether or not it had enough traction to warrant a change to core plugin code).

I also noticed that if I delete a recurring event that has past, that event with all the recurrences will be deleted. My suggestion in the admin is to have a “Master” occurrence and then display the recurrences underneath. If you delete a recurrence, no problem. If you need to make a major change, you edit the “Master” occurrence.

You should be able to edit past recurring events and – so long as you are within the actual editor and not the list – trash that instance and that instance alone. Intereestingly, your concept of a master event with individual instances that are subordinate to it is very close to what is being developed during the refactoring process – so it certainly seems like we are indeed headed in a direction you’ll be pleased with.

Right now though there isn’t too much more we can offer: please do monitor the forum and blog for updates and if you would like to make one or more feature requests relating to this they would be very welcome 🙂

Thanks!

[Barry]

You probably just need to add a little CSS. However, I don’t believe this problem is the result of our code (to bear this out, try deactivating any Modern Tribe plugins and see if the issue persists). In light of which, it would be more appropriate to seek help from the team at Woo or from your theme vendor.

Thanks!

[Author]

Posts