Can you send an actual URL of the event on your site/dev site?
If you don’t want to post that in a public forum, then you can email to info@opentickets.com if you would.
We use ‘post name’ on several installs.
Also, what version of WP/WC are you using?
Thanks, I’ll need to email you anyway as it’s a test site that’s behind a ‘maintenance mode’ plugin so you’ll need an account on it to see it – do you need to be a higher level of user than subscriber?
Versions: the latest ones, downloaded from here yesterday. So that’s WP 4.0, WC 2.2.2 and OT 1.4.0.
While I remember, do you need to use / publish the calendar, rather than having a page that says ‘select one of these, and possibly one or more of these, for each person’? The use case is one event (guess when!) that has a range of prices for the basic ticket plus assorted optional add-ons.
Having to click around a calendar to find the event feels it should be unnecessary.
Mine is doing exactly the same thing, I thought it was because I had a CPT called events
Maintenance Mode should not affect OpenTickets. We use WooDojo on sites in development, and it has never caused a problem. (It causes issues with other items, just not OT)
@lovingboth and @123digi we suspect a new issue with WC 2.2.2. WooCommerce made a lot of substantive changes with 2.2 release, but the 2.2.2 might have some issue.
That is escalated to Priority on our bug list, so we appreciate the reports.
If these are purely isolated Dev sites, and not production, it would help us to more quickly identify the issue if we could have a temporary WP admin login. (You of course should remove that afterward). If you want to do that, it might help identify the issue, since we haven’t run into that on our test or live sites. Please only do this if this is an isolated dev site.
If you want to do that, please make user openticketsdev and set whatever password you want to email info@opentickets.com .
Hey there guys,
We released the changes required for the new WooCommerce update. Since then I have tested the issue you are reporting, and I am able to reproduce it on my environment. A patch for this is currently in the works.
Loushou
Alright. A patch has been applied. Update to 1.5.1. That should resolve the problem immediately. If it is not immediately resolved, simply deactivate and reactivate the OpenTickets Community Plugin after updating, and it will be.
Loushou
