Forum Replies Created
-
Posts
-
So far I don’t think much in the way of a public API/template tags have been put in place (in respect of ticketing) so the best advice I can really provide here is to look at the tickets.php view (the original can be found in plugins/wootickets/views/tickets.php) and use that as a jumping off point top build your own specific solution.
Unfortunately Eventbrite is not fully compatible with PHP 5.4. We’re aware of this and a fix is detailed in this thread if you want to try fixing it. The next release of Eventbrite Tickets will include a permanent fix.
Sorry for any inconvenience!
So this looks to me rather like a caching problem.
If I try to visit http://www.girlswritenow.org/event/marchchapters/ it redirects, incorrectly, to a venue page as you’ve noticed. But if we add some random values in the form of a URL query, like this:
http://www.girlswritenow.org/event/marchchapters/?avoid=caching&random=2314213
Then hopefully, as I did, you will see the correct page.
On the caching front I can see that you are using W3 Total Cache and also Cloudflare. My hunch is that this is an issue stemming from W3TC rather than Cloudflare, but that’s just a hunch.
In the first instance I would suggest adding exceptions so that event/venue pages are not cached. If you can’t solve it that way – or even by turning off W3TC – then you may also need to look at and tweak your Cloudflare settings.
Hope that helps 🙂
OK, well we’ll certainly reach out to the author/team behind that plugin and see if there is any interest in working through this. I’ll post any updates here 🙂
Graham: did you hear anything back from Types’ developers? If so please do feel free to post an update.
Hi again Khaled.
So on this occasion we aren’t going to be able to provide a fix (for 2.0.11) as it is anyway fixed in 3.0 – which will be available shortly.
Once again if you want to evaluate 3.0 (bearing in mind it is still beta code and so not completely real-world tested) you are welcome to do so – please just email us as directed in my last post … and thank you for your patience while we looked into this 🙂
Hi Marco.
If I’m understanding you correctly and you want to stop certain custom fields from displaying then you will probably want to modify your custom single.php template a little. If you aren’t sure of how to do this, please refer to:
The basic idea would be to find the code that prints out custom/additional fields, which looks like this and replace it with code that ignores the field (or fields) you specify, something like this.
You would of course have to change the value of $ignore to whatever is appropriate in your case. Hope that helps 🙂
And, for what it’s worth, I’ve not experienced any problems in testing with WooTickets 1.0.1 and WooCommerce 2.0.3, so you should be good to go.
I’m going to close this thread now, but please do create a new one if you update and experience problems.
OK. Unfortunately, given we don’t actually support IE7, there’s not a great deal I can offer up.
One option would be to create custom views so that the tooltips can be generated in a different way or even two different ways (different markup that will work with IE7). You might even dispense with tooltips and present the information is some different form. Some good resources from our end:
Interesting – does this happen with a default theme such as Twenty Twelve, too?
I’ll add however that the minimum version of Internet Explorer supported by The Events Calendar is 8.0.
Great, is there anything you think might be worth sharing for the benefit of other users? If not, I’ll go ahead and close the thread in a few days 🙂
I’ll guess you’re all sorted since it’s been a while since we heard from you and will now close this ticket.
Thanks!
Hi Khaled, I’d hope to get back to you no later than tomorrow with a more definitive answer. One of the dev team are currently looking at this to see if we can get a fix in place.
What I can tell you is that it is not a problem in our 3.0 code (3.0 is the next major release and should be available soon). If you like, we could certainly send you a copy of our 3.0 beta code and – though it is not officially production ready – you could assess it and even use it on your client site if you felt it was stable enough.
Note also that we don’t support beta code on the forums as it has yet to be released officially, but it might provide you with an alternative path in case we can’t solve this with 2.0.11. If you are interested in this, please email us ([email protected]) and include a link to this thread and we’ll be happy to help you out.
I will in any case update you tomorrow and let you know what progress we have made.
Thanks for your patience!
