|
Brent Vincent
|
June 16, 2016 at 1:55 pm
Hey there,
I’m having issues with events over $1000 in EE3. For instance, I have an event price $1250, but once you go through the process of purchasing a ticket to the event it discounts the event $1249 so that it costs $1.
Similarly, I tested the event at $2000, and it discounted the event $1998 so that it cost $2.
Note: I’m not having this problem with events priced under $1000. I have some events priced $250, and I tested at $900, and there were no issues.
Not really sure what the problem is, and I could really use some help
|
|
Josh
|
June 16, 2016 at 2:02 pm
Hi there,
Is the version of Event Espresso you have installed current? Were there any customizations made to Event Espresso’s core functions or via a custom plugin?
|
|
Brent Vincent
|
June 16, 2016 at 2:17 pm
Readme.txt states this: “Current Version: 3.1.30.”
I do know there’s been modifications done to it, but I believe most of those modifications pertained to things like email and some custom PDF certificates to send to event attendees.
|
|
Josh
|
June 16, 2016 at 2:46 pm
That’s not a real version, you probably have 3.1.37.0, which was released back in February 2015. This looks like it’s a result of the combination of running older EE software on a newer version of WordPress. Can you try switching to the current version of EE3? The current version of EE3 is available as a download from your account page. It’s currently 3.1.37.8.
|
|
Brent Vincent
|
June 17, 2016 at 6:17 am
Previous to me there was custom work done directly to the plugin to fit some of the needs of the site, so, my first preference is not to do an update because I don’t want to lose those changes.
I know that’s less than ideal.
|
|
Brent Vincent
|
June 17, 2016 at 6:18 am
Are there solutions we could try before we resort to that?
|
|
Josh
|
June 17, 2016 at 9:30 am
Hi Paul,
There’s really one solution: Find out what’s causing the bug, and fix/remove the code that’s causing. One challenge in this particular case is, we know Event Espresso 3 on its own isn’t causing the problem because everything works on all of the other sites out there that have ticket prices above $1000.
Do you know if the customizations were ever tested to make sure that they didn’t affect the pricing module in EE3? Do you have a list or change log of the changes made to EE3 and its add-ons?
If you’re absolutely certain that it’s not the customizations causing the issue, you could try ruling out a plugin conflict. You can rule this out by temporarily deactivating any other installed WordPress plugins.
|
|
Josh
|
June 17, 2016 at 10:22 am
Update:
I was able to narrow things down a bit by FTPing into your site, then I downloaded your modified copy of EE3, then installed it on a local site. Then on that local site I tested a registration for a $1000 ticket and the price got changed to $1.00 after the registration form was submitted.
I can comb through the code and look for your customizations, but there’s quite a bit of code that executes when the registration form is submitted. If you have any clues about where the the customizations were made to the plugin please let me know.
|
|
Josh
|
June 17, 2016 at 11:36 am
Looks like there were code changes made throughout Event Espresso 3’s pricing and registrations modules. The one change that seems to be the culprit is on line 433 of your copy of /includes/process-registration/add_attendees_to_db where it has this:
'final_price' => number_format(round($final_price),2)
An unmodified copy of EE3 will have this instead:
'final_price' => $final_price
You can revert the above change and that should fix the pricing issues you’re seeing. The caveat is since there are a number of other changes throughout your copy of EE3, while it may work to just change that one line back to its original state, you will need to go through and test to make sure some of the other customizations are not relying on the above change.
Please keep in mind that your copy of EE3 may eventually need to be updated at some time in the future. This will happen when WordPress makes a change that breaks functionality for the current version of EE3 or your older version of EE3 (and we’re aware of a few possible changes in WP 4.6 that have this potential). Going forward your solution will be to extract the customizations out from EE3 into a separate plugin, and then you’ll be able to keep the software maintained and up to date.
|
|
Brent Vincent
|
June 17, 2016 at 11:56 am
Hey Josh,
Thank you very much sir. That did the trick.
And totally agree on the next steps. Just needed it fixed for a current event, but my plan is to get with the person who actually modified the plugin to extract those changes.
Really appreciate your help.
|
