|
laurian Horowitz
|
December 2, 2015 at 2:56 pm
Hello,
We have a website that uses event espresso. Currently, the live website is still on event espresso 3. We recently restored the website onto a development website in order to redesign the site.
We received many, many error messages from the get-go. As soon as the website was restored onto the dev site, the main error messages were “Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the “PagesSidebar2” sidebar. Defaulting to “sidebar-17”. Manually set the id to “sidebar-17″ to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in …wp-includes/functions.php on line 3622”
We then updated Event Espresso to the new version, Event Espresso 4. This fixed some of the error messages, but we are still getting some, including “Notice: Trying to get property of non-object in …./wp-admin/edit-form-advanced.php on line 419”
When we deactivate event espresso, these error messages go away. it is only when event espresso is activated that we see the errors.
Plus, I just went into some of the events and to make updates. the events were able to update fine, but some received this message:
“An error has occurred:
Event Details saved successfully but something went wrong with saving attachments.
Events_Admin_Page – _insert_update_cpt_item – 752”
Like I said the events updated fine, but it still gave an error message
Lastly, when I am in the ‘Event Espresso – Events’ back-end page, where I see the list of my events, the page is giving me problems. I cannot easily click on an event to edit, as the black ‘status legend’ pop up window appears every time i hover over an event, making it difficult to view and edit events.
I know that this is a lot, but is there any way we can receive some answers to these issues?
Thanks!
|
|
Josh
|
December 2, 2015 at 4:25 pm
Hi there,
Notice: register_sidebar was called incorrectly is usually from the active WP theme.
With the WP core error, for edit-form-advanced.php, we’ll need to know which version of WP you have to answer your question.
The last two issues sound like they may be the result of some affects from the WordPress theme. Can you try changing to the default WordPress theme to see if the errors go away?
|
|
laurian Horowitz
|
December 2, 2015 at 4:32 pm
We did already change the theme on the dev site. The live site is using U-design, and the dev site is simply using Twenty-Fifteen. changing the theme did also help with the error messages, but didn’t get rid of all of them.
Also, the website is on the newest version of WordPress, version 4.3.1
|
|
Josh
|
December 2, 2015 at 4:41 pm
WP 4.3.1’s edit-form-advanced.php line 419 reads as:
if ( isset( $post_new_file ) && current_user_can( $post_type_object->cap->create_posts ) )
You might try creating a new user account on the dev site. It may be the user accounts from the live site were not corrected exported/imported.
The hover issue isn’t something we’ve seen before, so it may help to try disabling any other plugins that are active since you’ve ruled out the WP theme.
|
|
laurian Horowitz
|
December 3, 2015 at 1:15 pm
Thanks for your quick responses yesterday!
I did try and create a new user, but the error messages were still showing up.
I am now going to try and restore the website again to see if that can fix any issues.
|
|
laurian Horowitz
|
December 4, 2015 at 12:13 pm
Josh,
Just wanted to let you know that I did restore the website again, and this time around there are no errors whatsoever. I did the manual migration from EE3 to EE4, and event espresso is working just fine now.
It seems like all the errors we were experiencing was due to a bad backup file that we used for the restore. Even the ‘status legend’ issue has been fixed.
Thanks for your help though!
|
|
Josh
|
December 4, 2015 at 12:44 pm
You’re welcome Laurian.
|
