Forum Replies Created
-
Posts
-
That is correct; however this is being revised for the next release. It’s possible to customize the PDFs however I’m afraid its sufficiently complex that we can’t guide you through it.
I believe some users have worked around this by incorporating the date into the ticket title, though.
Sorry I can’t offer up more on this occasion.
Apparently if products are set to both virtual and downloadable the order will be marked as complete immediately in most cases.
So we can’t actually replicate this issue; though I appreciate you annotated that you ran through our basic troubleshooting steps when you opened this thread can I just confirm those steps and that they made no difference to this problem?
- Please ensure that your Modern Tribe plugins are up-to-date and in-synch … for instance if you are using The Events Calendar 2.0.11 you must also use Events Calendar PRO 2.0.11 (and, in your case, Eventbrite Tickets 1.0.5)
- Deactivate all other plugins and change your theme to a default, unmodified one such as Twenty Eleven or Twenty Twelve
- Now test to see if the problem still exists
- If the problem has been solved by these steps, start reactivating everything one-at-a-time, testing at each point to see if the issue has returned
- If the issue does return, take note of whichever plugin (or theme) you reactivated immediately before it started again – it’s likely there is a conflict with this item
(Moving this to the WooTickets forum.)
This sounds like a known bug which I believe was fixed in WooTickets 1.0.1 … can you confirm that that is the version you are using and that you are still seeing this behaviour?
I’m not sure they are documented anywhere except for within the code itself, but essentially they are all prefixed with tribe_ so they are easy to tell apart from other post types.
- tribe_events
- tribe_venue
- tribe_organizer
Sounds like there might be a problem with your WooCommerce setup. Can you take a look at WooCommerce > System Status > WC Pages and check that everything looks ok there?
The shortcode that should be on the cart page is:
[woocommerce_cart]So perhaps that shortcode you are seeing is a remnant of an older version of WooCommerce, or of a different e-commerce solution?
OK – I’ve asked a dev to look at this and will pass that clarification on to him – and will he or I will update you as soon as we can 🙂
Hi Jesse,
They also conclude that an “upcoming 3.0 release” will resolve this… though I’m not so sure because those threads indicated the bug occurs only whilst using the Free version.
By virtue of the detail in your post I think this may be an angle we hadn’t considered previously; please bear with me as I want to test out what you are describing.
I’ll update you as soon as I can.
I’d suggest taking that question across to the support team at WooThemes, you’d need to turn off or negate whatever validation checks WooCommerce runs during the checkout process to do this.
That’s all possible, though it probably isn’t quite the sort of task Modern Tribe would take on – but there are a load of competent developers out there who could help.
If you haven’t already done so you could also consider using a caching plugin, so that the pages are saved as raw HTML and don’t have to be generated from scratch every time they are requested.
I’m not quite sure I understand what you’re proposing for your second option, but I think the approach I would take is to filter the event query (testing first to see if the upcoming events list is being viewed) and changing the parameters accordingly.
However, we don’t have any snippets to offer up on this occasion.
