Ticket Programming Issues

[Paul]

I’ve had a couple of persistent issues when programming tickets this week…

Issue #1: After inputting the ticket price and saving, the saved ticket resets to “Free”. I need to click “edit”, and then a second, new ticket price field appears and I have to re-enter the ticket price into the new field . THEN it saves. Unless I go back in to edit other things. Then I lose it again, unless I refill these fields again.

Issue #2: The system will not save AM or PM for either the “Start Sale” and “End Sale”. It does save the number I assign.

I’m about to be go on sale with about fifty shows. So rectifying this will be important!

Thanks.

[Geoff B.]

Good evening Paul and welcome back!

Thank you for reaching out to us.

We are sorry to hear about the issues you had to deal with this week.
I would love to help you with these topics.

Issue #1: After inputting the ticket price and saving, the saved ticket resets to “Free”. I need to click “edit”, and then a second, new ticket price field appears and I have to re-enter the ticket price into the new field . THEN it saves. Unless I go back in to edit other things. Then I lose it again, unless I refill these fields again.

This is very odd indeed! As a first troubleshooting step, could you please provide us with your system information in a private reply ? (following the instructions found in the link)

Issue #2: The system will not save AM or PM for either the “Start Sale” and “End Sale”. It does save the number I assign.

Once again this is not the normal behaviour. It sounds like there could be a theme, customization or plugin conflict at play.

Could you also please go through our testing for conflicts procedure (preferably in a staging/dev environment or local install of your WordPress website) and let us know what you find out.

Basically the goal here is to revert back to a bare WordPress installation to see if the problem persists. It also allows us to pinpoint what the cause of the issue is.

Hang in there as we try to identify the cause as fast as possible.

Best regards,

Geoff B.

[Paul]

This reply is private.

[Paul]

OK. I couldn’t help myself. I stayed up late and went through the testing for conflicts procedure. I switched to the 2015 theme and deactivated all plugins except the following:

TEC
TEC Pro
WooCommerce
TEC WooCommerce Tickets

I regret to say that the problem persisted.

Back to you!

[Geoff B.]

Good evening Paul,

Thank you for going through all the tests and for providing your system information.

I believe the cause of your issue is that you are using the Events Calendar Woocommerce Tickets plugin.
This plugin has been deprecated and replaced by the Events Calendar Event Tickets Plus (which you can download and install).

But, before you do, I would recommend reading the following: https://theeventscalendar.com/knowledgebase/moving-to-event-tickets-plus/ and more importantly, doing a backup of your database.

Let me know how that goes.

Best regards,
Geoff B.

 

 

[Paul]

Thanks Geoff. We’re getting there. Almost everything seems more stable now except that the “AM” & “PM” designations still aren’t saving. Thoughts?

[Paul]

A couple more questions arising from installing Events Tickets Pro and replacing Woocommerce tickets…

1) Where can I disable the QR code check-in that now appears on my tickets? I don’t currently have the infrastructure to do this at my multiple venues.

2) When I was using Woo Tickets, I had flat rate shipping set up in order to apply a $2 service fee to all my orders (on the total order, not individual tickets). Now with ETP, my tickets default to Virtual Products and I’ve lost the ability to easily apply the service fee. That is, unless I go through all my Woocommerce products and unclick Virtual Product. I can do that, but other threads on the topic suggest using Virtual Products for tickets is essential to ETP functionality.

[Geoff B.]

Good evening Paul,

I’m stoked to see we are making some progress 🙂

So let’s finish what we started.

Almost everything seems more stable now except that the “AM” & “PM” designations still aren’t saving. Thoughts?

This is indeed very odd. It could very well be that there is a conflict either with your WordPress theme, a customization done in the WordPress theme or another plugin.

My next recommended step for that would be to go through our testing for conflicts procedure (preferably in a staging/dev environment or local install of your WordPress website) and let us know what you find out. Basically the goal here is to revert back to a bare WordPress installation to see if the problem persists. It also allows us to pinpoint what the cause of the issue is.

While you are at it, could you also tell me if that’s the case for a completely new event (and ticket) ?

1) Where can I disable the QR code check-in that now appears on my tickets? I don’t currently have the infrastructure to do this at my multiple venues.

Good news! You can actually do that with the following plugin: https://theeventscalendar.com/knowledgebase/hide-qr-code-from-event-emails/

2) When I was using Woo Tickets, I had flat rate shipping set up in order to apply a $2 service fee to all my orders (on the total order, not individual tickets). Now with ETP, my tickets default to Virtual Products and I’ve lost the ability to easily apply the service fee. That is, unless I go through all my Woocommerce products and unclick Virtual Product. I can do that, but other threads on the topic suggest using Virtual Products for tickets is essential to ETP functionality.

Good call. I strongly suggest keeping the tickets as virtual. Otherwise, the other threads are right. You are bound to run into issues.

Our Community tickets add-on actually does exactly that (provide the option of adding a flat fee on tickets via the Events -> Settings -> Tickets tab). So the good news is that it can be accomplished with some template customization (adding a snippet to the functions.php of your theme).

Just to set expectations, as you might know, the scope of our support is mostly to get our wonderful customers started on the right track to customize their site and to help them in case of issues. We unfortunately do not provide complete support for customization.

Let me know if that helps.

Have a great day!

Geoff B.

 

[Paul]

Well… this is getting to be no fun. 🙁

As you will see above, I went through the testing for conflicts procedure, so now we’re repeating ourselves. I can do it again, I guess, if you think we’ll discover something new. But I don’t have the tech know-how to create a test environment. This means I do it live and have to reconfigure all the plug-ins I knock out.

And now… your advice to me is that I buy the Community Events plug-in at $149 USD and pay a tech to customize something I had perfectly configured before you had me migrate to Events Tickets.

And I announce my festival in five days.

You’re killing me, dude.

So to recap…

– Do you REALLY need me to repeat the testing for conflicts procedure, even though I did it just a couple of days ago?

– Any chance you can hook me up with a license for the Community Events feature without incurring the additional cost? I’ll have to pay my IT guy $100 an hour to figure out the customization.

[Paul]

I should add… that the AM/PM problem is persisting with new tickets and by editing old tickets.

[Paul]

Me again.

I changed the time format in my WordPress settings from AM/PM to am/pm and now it’s starting to save when I schedule my tickets. So that’s a step in the right direction.

Because I’m disinclined to purchase Community Tickets and then pay for customization to activate service charges (which, as I say, I had humming along nicely before changing ticketing plugins), I’ve decided to revert to Woo Tickets and deactivate Events Tickets.

Still, with Woo Tickets, Issue #1 as described at the very top of this thread is persisting. But this is the lesser of the evils. It’s clumsy, duct tape solution, but at least I’m getting the system to do what I need it to do.

[Geoff B.]

Good afternoon Paul,

I am sorry about about the extra work involved. Perhaps I miscommunicated what I meant.
My apologies.

As you will see above, I went through the testing for conflicts procedure, so now we’re repeating ourselves. I can do it again, I guess, if you think we’ll discover something new. But I don’t have the tech know-how to create a test environment.

The idea behind testing for conflicts again was to do it after the upgrades of the plugins. I realize this is not much fun, but it’s a necessary evil to leave no stone unturned (which also translates to faster resolution).

As for the test environment, it’s actually pretty useful to avoid nasty surprises when updates roll in.
The good news is that you can totally set it up on your own computer for free using the instructions found in one of the 2 following links (depending if you are a PC or Mac user):

• https://codex.wordpress.org/Installing_WordPress_Locally_on_Your_Mac_With_MAMP
• https://premium.wpmudev.org/blog/setting-up-xampp/

And now… your advice to me is that I buy the Community Events plug-in at $149 USD and pay a tech to customize something I had perfectly configured before you had me migrate to Events Tickets.

This is absolutely my bad. I should have been more thorough in my answer.

I totally understand that this worked fine for you prior to the update to ETP. That being said ETP is a far more stable and robust product than WooTickets was.
<span style=”line-height: 1.5;”>In other words, I sincerely believe it solves more issues than it creates. </span>

Some of our users choose to keep older versions of our plugins in place (which you can absolutely revert back to should you prefer) because they have a specific workflow and do not want to break it. But of course, that also means that over time, these plugins are bound to not be compatible with newer WordPress versions and will not benefit from bugfixes, security patches, etc…

But back to my previous answer, what I meant to say is that you will need some customization to make your flat fee happen with ETP.
There are quite a few ways to go about this and it is not as bad or complicated as it sounds nor a complicated snippet.

But before we go there, just to set expectations, as you might know, the scope of our support is mostly to get our wonderful customers started on the right track to customize their site and to help them in case of issues. We unfortunately do not provide complete support for customization.

With that in mind and understanding I am actually looking to provide you with options, you could:

• Use the local installation of WordPress suggested above to run some tests and see if changing the tickets to non-virtual breaks anything for you
• Scour the web to find a snippet to add a flat fee on a specific WooCommerce product type OR to enable Shipping fees on a Virtual Product
• Temporarily buy our Community Tickets add-on to analyze how this is done ( your are fully entitled to a refund if you want one since you are within 30 days of your purchase. To obtain the refund, you just need to follow the procedure described here).
• Hire one of our recommended customizers to do the customization for you.

I changed the time format in my WordPress settings from AM/PM to am/pm and now it’s starting to save when I schedule my tickets. So that’s a step in the right direction.

Kudos on figuring that one out and thank you for sharing!

Still, with Woo Tickets, Issue #1 as described at the very top of this thread is persisting. But this is the lesser of the evils. It’s clumsy, duct tape solution, but at least I’m getting the system to do what I need it to do.

I totally understand and respect where you are coming from on this.

The cause of this specific issue is that WooTickets no longer plays nicely with the latest version of our the Events Calendar plugins. Unfortunately, short of rolling back the Events Calendar other plugins to an earlier version (prior to 4.0) this will be hard to fix.

I wish I had a better answers for you, but for now these are sincerely the best ones I have.

Best regards,

Geoff B.

[Paul]

Thanks Geoff. I appreciate the time you’re putting into helping me out.

I think the most comfortable solution is to revert back to an earlier version of TEC so everything works as I intended when I set it up a few months ago. I’ll stay with this until the end of my June festival and then, over the subsequent summer months, sit in my back yard with my laptop and a beer and get to work on bringing everything up to date as you suggest.

So, one final question for now: Can you point me toward some directions on reverting to an older version of TEC?

[Geoff B.]

Hey Paul,

Thank you for your understanding. In the end, we do share the same goal 🙂

I totally understand your choice as a quick solution. That being said, I would still advise doing that on a local install to ensure nothing breaks.

You can download past versions of our free plugins here:

• https://wordpress.org/plugins/the-events-calendar/developers/
• https://wordpress.org/plugins/event-tickets/developers/

You will find previous versions of our premium add-ons under your account page on this site.

Let me know how that goes.

Best regards,
Geoff B.

[Paul]

OK, it seems as though I was successful in changing back to TEC 3.12.6 and now everything is behaving as intended (knock wood). I’ll leave it that way for the next couple of months and, as I mentioned above, work on upgrading and updating everything in July, when things quiet down for my organization.

You’ve been helpful, Geoff. Thanks.

[Author]

Posts