Posted: June 6, 2014 at 2:17 pm
|
Upgraded today to the most current version of EE4 and now get a fatal error when trying to checkout – Fatal error: Call to a member function _add_relation_to() on a non-object in /home/content/84/9677984/html/wordpress/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/EED_Single_Page_Checkout.module.php on line 557 http://theurbanartbar.com/reservations Running most current version of wordpress as well… Please advise. |
Hi Frank, We are not able to reproduce this issue on our sandbox server. Can you please verify that it is not a conflict with another plugin and or their theme? Do you mind if we take a look at the files on your server? Please send WordPress admin level log in credentials via this form: |
|
|
Any thoughts? |
Hi Frank, I’ve passed your info over to our developers. However, they may not be around over the weekend. Would you like me to send over the previous version? Also, one more question. Are you using the EE Arabica child theme or any of the EE template files in your theme? |
|
|
No not using any EE themes…yes please send me previous version. Thanks |
|
same issue with me too..after upgrade |
|
my error is : Fatal error: Class ‘EE_Admin’ not found in functions.php on line 4 |
@Sudhir that is a different error. Please start a new thread so we can take care of the specific error that Frank reported. |
|
Frank, Do you remember what version you had prior to the update? |
|
|
I completed the setup, and went to view the page, and I saw an error message…. |
|
Seth I was current on updates so what ever the immediately prior version was it what I had. |
@Frank I sent over version 4.2.4 via email. Please let me know if that fixes the issue. |
|
|
Hi Seth have not received the file yet – did you send it to frank@theurbanartbar.com? Thanks |
Yes, can you check your spam box? |
|
I just resent the email. |
|
@Patrick can you please start a new thread for your specific error? Although, it looks like your error is caused by your theme (newElegantBiz), NOT Event Espresso: |
|
Hi Frank, I’m Event Espresso’s lead developer, and the one who did the troubleshooting on your site. The error you experienced is a bit of a thorn in our side. Basically, in one of our core systems, we had a choice of two ways of doing things, let’s call them A & B. Either option **might** throw errors depending on someone’s server configuration and setup. EE 4.2.4 was using option A, but there wasn’t really a way to easily fix that issue, so EE 4.2.5 switched to option B, which doesn’t have the same issue that option A has, but has problems if you use a WP date format that is incompatible with some of PHP’s core functions (PHP is the server side language that is installed on your server and what both WP and EE are written in). You were using “j F, Y” as your date setting on the WP General Settings page, which produces dates that look like this: “9 June, 2014” Unfortunately, some of PHP’s core functions choke on this date format and throw fatal errors (but interestingly enough do not choke on “j F Y”). There is nothing we can do about this, as we have no control over PHP or the software installed on your server. There WAS however, a tiny logic bug in EE 4.2.5 that prevented the REAL error caused by this date format issue from appearing, and instead threw a different error. I updated your installation of EE 4.2.5 with a fix that allowed the real error to appear. Then, to fix the date format issue, I simply changed your site’s date format in the WP General Settings to “F j, Y”, which produces dates that look like this: “June 9, 2014”. You are welcome to change it to anything else, because there is now a check in place that will NOT allow incompatible date formats to be set. So you won’t be able to save “j F, Y” anymore, but could use “j F Y” (without the comma) if you want to get as close as possible to your old format. When WP drops support for PHP 5.2 (which is no longer even supported by the people that make PHP) then we will be able to completely eradicate this issue, but until then we are forced to choose the lesser of two evils (or bugs). I hope that this is acceptable as it is something that is somewhat beyond our control at the moment. @Sudhir Gupta
|
|
The support post ‘EE4 Fatal Error – Checkout’ 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.