Support

https://eventespresso.com/wiki/how-to-upgrade-event-espresso/#update-event-espresso-4

Support Staff

June 22, 2016 at 2:57 am

Hi Phil,

We do not advise installing your license key on your development site, doing so will invalidate your key each time you do and you will then need to request a reset before it can be used again.

You can however installed the updates manually on your development site:

The steps with core are the same steps used for add-ons.

In a nutshell you backup your site, de-activate and delete the current version fo the plugins, download the latest version to your desktop and install that new version through Plugins -> Add New -> Upload Plugin.

None of your existing data will be lost when doing the above but we always recommending backup your data before running any updates (not just EE updates but any plugin, themes and WP updates)

June 22, 2016 at 3:40 am

Hi Tony,

Thanks for the quick reply. That will work for me. I was not sure if i could update without the license key or if it was essential. I know i need it for the automatic updates.

My concern with using that method was whether i would i have to import all the data back in after deleting the plugin. But if that is not the case then perfect, I have already backed up my development data this morning so il give it a shot.

Is it possible to keep this topic open in case i require assistance? or would you prefer i opened a new one if i have any issues.

Thanks

Phil B

Support Staff

June 22, 2016 at 3:49 am

My concern with using that method was whether i would i have to import all the data back in after deleting the plugin.

EE does not remove its data on plugin de-activation/delete. We have functions to do that should you wish, but we will never call those automatically 🙂

Is it possible to keep this topic open in case i require assistance? or would you prefer i opened a new one if i have any issues.

Sure, its fine to keep topics open.

We (support staff) will generally not close a thread unless it is very clear the thread is resolved, either by the user posting stating it is resolved or updating the status to resolved themselves.

However one thing to note is that threads automatically close after 2 weeks of no activity, if that happens (with any thread) please feel free to open up another and link to the close thread if relevant. We can open closed threads and/or merge the new thread into that if needed 🙂

June 22, 2016 at 4:05 am

Excellent stuff Tony. Much appreciated. Looks like i know what I’m doing this afternoon.

Regards

Phil B

Support Staff

June 22, 2016 at 4:23 am

You’re most welcome.

Any problems just let us know.

June 22, 2016 at 6:26 am

Hey so the update seems to have gone off without a hitch, quite pleased with that.

I installed the update as suggested FORUM POST

Like i say, it seems to have gone through quite easily. Whilst looking for the options to set the new registrations redirect i checked back to that previous topic and realised it should be automatic. Unfortunately this is not the case and no redirect takes place.

I thought i might have to activate my account and the redirect would happen then but having tried that as well it doesnt seem so.

I have noticed a change in the URL though when i register for an event on my test server, there seems to be some extra parts to it referring to EE and the checkout, where as on live this doesnt happen (i havent updated this yet) so it looks as though there is every intention of redirecting the user afterwards.

Is there a setting i would need to configure to get this working? I can provide a link to the test site and and a test event if someone would like to have a look.

Regards

Phil B

Support Staff

June 22, 2016 at 7:20 am

There’s no setting, so if you have the most recent version of the WP User Integration add-on installed and it’s not redirecting the new user to the next step after they create an account, that could be another plugin that’s preventing the redirect.

You can rule this out by temporarily deactivating any other installed WordPress plugins one by one.

June 22, 2016 at 7:53 am

Hi Josh, this is what i thought when i couldnt find it and then when i checked your reply to my previous topic i realised. Unfortunately it is not working currently. The login page on WordPress seems to be broken also. It will log me in but i get a internal server error 500.

I have just updated some other plugins as well so i have been going through and deactivating them all to try and solve it. Failing that il start digging through the apache logs again

Thanks

Phil B

Support Staff

June 22, 2016 at 8:10 am

You can also turn on debugging to find the error that’s causing the log in page to break.

You can set wp_debug to true by editing the wp-config.php file.
You can use an [FTP client][1] and [a text editor][2] to access change this line to the site’s wp-config.php file:
define(‘WP_DEBUG’, true);
[1]: http://codex.wordpress.org/FTP_Clients
[2]: http://codex.wordpress.org/Editing_Files#Acceptable_External_Editors

June 22, 2016 at 8:33 am

Thanks Josh, i will try that now. I’ve disabled the other plugins except all EE plugins. the only ones left are buddyPress and BBPress and i dont know if they remove all the forum and community data when deactivated.

FTP can be a struggle for me, il have to do it from the terminal. Thanks again Josh.

Phil

June 22, 2016 at 8:48 am

Hey so i have got the error message from the wordpress logs.

Fatal error: Uncaught exception ‘EE_Error’ with message ‘The EEM_Attendee model can not be loaded before the “AHEE__EE_System__load_espresso_addons” hook has been called. This gives other addons a chance to extend this model.’ in /opt/wordpress-4.4.2-0/apps/wordpress/htdocs/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php:417 Stack trace: #0 /opt/wordpress-4.4.2-0/apps/wordpress/htdocs/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Soft_Delete_Base.model.php(37): EEM_Base->__construct(NULL) #1 /opt/wordpress-4.4.2-0/apps/wordpress/htdocs/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_CPT_Base.model.php(122): EEM_Soft_Delete_Base->__construct(NULL) #2 /opt/wordpress-4.4.2-0/apps/wordpress/htdocs/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Attendee.model.php(166): EEM_CPT_Base->__construct(NULL) #3 /opt/wordpress-4.4.2-0/apps/wordpress/htdocs/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php(599): EEM_Attendee->__construct in /opt/wordpress-4.4.2-0/apps/wordpress/htdocs/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Base.model.php on line 417

Im not sure what is going on, but as i say i have disabled all the plugins that are there except for the event espresso and its plugins, and the BBpress plugins which i havent updated yet.

I initially thought it was the extra updates i had installed for other plugins until i disabled them but now im not too sure whats happening.

Could you please advise on this,

Thanks. Phil B

June 22, 2016 at 10:00 am

Support Staff

I’m pretty sure that BuddyPress and bbPress do not remove any data when deactivated. Does your site have the current versions of BuddyPress and bbPress?

June 22, 2016 at 10:07 am

Not currently no, i was going to update EE and check that worked and then update both of them.

I discovered the login problem before i had chance to update them.

Regards

Phil

June 22, 2016 at 10:25 am

Support Staff

It might help if those are updated to their current versions. I’ve got the current versions of bbPress and BuddyPress installed on a site that has EE4 and I’m not seeing any errors there.

June 23, 2016 at 2:04 am

Hi Josh sorry for the delayed reply.

I will try them now and see if it has any effect. Failing that i will probably have to revert back to the snapshot i took before i did the update and try again.

Thanks,

PhilB

June 23, 2016 at 3:23 am

Great news!!

I have tracked down the problem and the cause of it. I followed your advice and updated BBPress and BuddyPress, but unfortunately this made no difference. So i started on the error logs again and worked out that the problem itself is with some custom development work we had done. It looks as though their plugin is calling a function or class in the EE core and cannot find it. I disabled this plugin and the issue went straight away so i have passed it on to the developers.

Im also wandering if this is why the auto redirection did not seem to work also.

Not sure how i missed it yesterday, i think after all day trying to fix it my brain had turned against me.

Can i just ask, since the update was there any changes made to the Class ‘EEM_Attendee’ with the latest update? im just thinking maybe the dev guys are referencing something that has been moved or changed.

Il post back the results i get from the dev guys to this topic in case anybody else has a similar issue.

Thanks for the help guys,

PhilB

Support Staff

June 23, 2016 at 5:36 am

Nice job finding the cause 🙂

No changes to EEM_Attendee.

However since 4.8.39 EE checks for wp-login.php or register.php and prevents its functions from loading. Depending on how the developer is hooking in they made be trying to run EE functions that have not loaded. That would fit with the error being thrown…

The EEM_Attendee model can not be loaded before the “AHEE__EE_System__load_espresso_addons” hook has been called.

What is the custom function used for?

June 23, 2016 at 6:16 am

Hi Tony,

Basically when a new user signs up for the golf lessons we sell, they are put into a group for their ‘coach’ and a group called ‘love.golfers’. Obviously the issue is once we start getting more and more people signing up adding them in manually becomes tedious.

The plugin we had created adds the new users into the right groups once they have registered to save us doing it one by one. It uses the BuddyPress groups plugin to do so.

With what you said about the wp-login and register files it seems quite plausable as its the login page that would give me the error. Im also wandering if thats why i couldn’t get the auto redirect part working when i tried it, if it is using the wp register page. im hoping once the developers have taken a look and fixed their code then the whole thing should work, which would make my week.

I haven’t heard anything from the developer yet but as i said in my previous post, once they get back to me with a solution il post the results in this topic in case it can help anyone else with a similar issue.

Thanks guys, helpful as always!

Regards,

PhilB

https://github.com/eventespresso/event-espresso-core/commit/a9f7063dc3df4ca4d6bf1a6eccae6e04f25c8fc9

Support Staff

June 23, 2016 at 9:11 am

Your developers can make use of the parameter that was added in this commit:

June 23, 2016 at 9:32 am

Thanks Josh i will pass that on to them now. Im still waiting for them to get back to me.

Regards,

Phil