Posted: April 2, 2017 at 12:42 pm
|
Customer is trying to edit locked transactions which have failed to remove transaction before deleting…. getting error when clicking to edit transaction: Fatal Error: Class ‘EE_Processor_Base’ not found in /wp-content/plugins/event-espresso-core-reg/core/EE_Payment_Processor.core.php on line 16 Ideas? We are at latest version, cleared cache. Error log shows same error and this one occasionally: Ideas? |
Hi Bob,
Can you provide further details on this please? I’m not sure what you mean by failed to remove the transaction before deleting.
That error usually means allow_url_fopen has been disabled on your site and DOMPDF can’t open the image. If you download a PDF of your invoice can you see that logo? (Its not connected the issue above) |
|
|
Customer now reporting the clients can check out, make payment via MC/VISA through Mijireh gateway but they get a fatal error after payment and the payment is not confirmed in Event Espresso. So all is working but final confirmation back from Mijireh. Has there been updates or changes, this is how it’s been running for a couple years? |
|
Ok so there’s a list of incomplete payments from customers getting error when going to Mijireh (I think that is fixed now). So to go back and edit the “incomplete list” We can open the registration, change to approved, declined but anytime we want to edit the transaction and remove it to remove the padlock we get the error |
|
FYI allow_url_open is ON
|
We are investigating this currently and will update this thread with any news.
Hmm, then something else is blocking the connection, it could be mod_sec or some other security your host is using. Does it happen with every PDF? |
|
|
I know what a PDF is but we are simply trying to edit the failed transaction in the registration?? Is that a PDF? |
No, its not a PDF it’s a separate issue. We are investigating the fatal error you reported when viewing the transactions. |
|
The fatal error you saw:
is something that could happen with 4.9.35.p. Event Espresso 4.9.36.p is released and includes a fix for that error. |
|
|
Excellent and thanks, I’ve applied the update and yes we can edit the locked registrations now. Customer is now testing the transactions work so we can stop the locked transactions from happening from Mijireh. I’ll update you soon |
|
Customer reports transactions are now processing! Thanks for the udpate, we’ll keep monitoring and advise if anything changes |
The support post ‘Fatal Error when trying to view locked transaction/registration’ 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.