Posted: March 13, 2024 at 9:08 pm
Just updated to latest version Version 5.0.18.p and now experiencing a problem. |
|
Can you send us screenshot of the error you see? Can you also send the error log here? for the wrong computation, can you give more details on your ticket and its pricing? Does this happen on all your event or just on particular event? Can you send link of the event here? you can send it as private message if needed. thanks |
|
How do I send the screen shot? Can you please send me a copy of the previous version of EE so I can reload it. |
|
This reply has been marked as private. | |
https://tatsa.com.au/wp-content/uploads/PayPal-Error.png How do I send the file error log to you? |
|
I’ve just tested registering onto an event, checkout shows the correct values: https://monosnap.com/file/VOM1hULZqBPMSsQvIiRJEnOFr0sxj9 So this only happens after the registration has been finalized?
Send it over to support@eventespresso.com and I’ll take a look. |
|
Thanks Tony, Error log emailed |
|
I have rolled back to prior version. In a few days I will do the update and see how it goes. |
|
Awesome, please let us know if you experience any problem or if you have question and concern. Have a wonderful day. thanks |
|
Thanks, Rolled back to Version 5.0.17.p Still got the problem as per first post here: When I click on Pay Menthods option in EE, I get a page showing this message: Any ideas on what is causing this? |
|
Were you able to send the error log to what tony said?
Do you experience any problem aside from that warning? here’s the guide on how you enable error log, Then you can also fill the form so we can check it. https://eventespresso.com/send-login-details/ thanks |
|
Rio, yes log sent 15/03/2024 |
|
Just noticed the same error in calulation has occured. Seems to be limited to when student pays with PayPal. |
|
This reply has been marked as private. | |
I have updated to the latest version and will monitor what happens. As mentioned the error has only occurred when paypal payment option is selected and payment made. The error with accessing the payment methods tab is still happening. The previous log was emailed to EE, do you need another log? The file contains a lot of data so it would be quite extensive to post it here. |
|
Hi John, I can’t find any log files within our support inbox. However, rather than sending them over, can can do a quick search for ‘Illegal mix of collations’ within the log file? If that’s the error being thrown I already know the fix for it. If not we can investigate further. |
|
A partial payment? Whats the setup for this? Line items (which is what would be breaking this) are created outside of payment methods so I need details of how this is set up to see if I can reproduce |
|
As per first post, the payment due is $250 + GST 10% = $275, however the system is shows it is due $300 ie charging the GST twice. What do you mean “what is the set up for this?” I’m not sure what log file I should be sending. It would be better if I granted you access to the the control panel and find it as you would know which one to search for. |
|
I understand that part but you mentioned this is only happening with PayPal payments, so any partial payments? Moved registrations? Or is this simply a ‘standard’ registration? Line items (the items that make up a transaction, to which a payment will apply to) are generated outside of payment methods so it is really strange that is would only be happening when using PayPal. Any custom code on the site to hook and charge based on the selected payment method at all? (Or any custom code at all for EE?)
Sure, if that’s what you prefer to do, you can send credentials over using this form: |
|
Hi Tony, |
|
This reply has been marked as private. | |
This reply has been marked as private. | |
This reply has been marked as private. | |
This reply has been marked as private. | |
This is someting WebAware (the author of the Eway Payment Gateway plugin) needs to fix. In their latest version they changed this file:
and changed this line of code:
To be:
But the file holding the Changing the code back will fix it but then a fatal error will be thrown again when you update unless they update their code. I recommend opening a support ticket with them to have them fix that fatal. |
|
The support post ‘Incorrect calculation in shopping cart’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.