|
Annette Neumiller
|
July 31, 2014 at 2:14 pm
upgrading to 4.2 from 4.1.5 I am in full maintenance mode and have two options – Migrate my ee4.1.5(reg)Core to ee3.2.0 Core
just start ee4.2.9 and delete data
I am trying to select the first option, and nothing happens. Please advise
WordPress Version:
3.9.1
PHP Version:
5.4.29
MySQL Version:
5.5.37
Event Espresso Version:
4.2.9.p
WordPress Address (URL):
http://kickbackevents.us
Site address (URL):
http://kickbackevents.us
|
|
Jonathan Wilson
|
July 31, 2014 at 4:18 pm
Hi Annette,
I’m sorry for the trouble.
May we log into your site to have a look? If so, please send us WP Admin credentials through the form on this page: https://eventespresso.com/send-login-details/
To prevent delays in troubleshooting, be sure to double check your information on the form before submitting.
The submit button for the form appears after you have answered “Yes” to the last question.
|
|
Jonathan Wilson
|
August 1, 2014 at 8:30 am
Hi Annette,
Thanks for sending the credentials. I’m curious to know whether the Custom Event Espresso Event Displayer plugin you have installed is causing a conflict. There is a javascript error mentioning that plugin on the Event Espresso migration page. Can you try deactivating the Custom Event Espresso Event Displayer plugin and then running the migration again? I didn’t want to in case you are using the shortcode from that plugin. I don’t want to break anything.
|
|
Annette Neumiller
|
August 1, 2014 at 9:27 am
Jonathan,
When I first tried the update, that was disabled. I’ve disabled it again, still no change…please advise, we are trying to stage an event to engage a developer later today
|
|
Tony
|
August 1, 2014 at 9:52 am
Hi Annette,
There are Javascript errors being thrown on the page which is preventing EE4 JS from running when the button is clicked – http://take.ms/dAkmO
This could literally be any plugin (or even the theme)
You can enable script_debug in wp-config.php so WordPress will load the un-concatenated/un-minified scripts so you can find the exact one causing the issue.
Details on script_debug can be found here:
http://codex.wordpress.org/Debugging_in_WordPress#SCRIPT_DEBUG
|
