Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Corrupt Venues after migration | Event Espresso - Staging Server

Support

Home › Forums › Pre-Releases › Corrupt Venues after migration

Corrupt Venues after migration

Posted: April 4, 2014 at 9:39 am

Viewing 1 reply thread


tgrady

April 4, 2014 at 9:39 am

I am getting this error when I try to delete a corrupt venue after the migration.

An error occurred. The venue could not be moved to the trash because a valid venue status was not not supplied.

How can I get rid of these rogue venues.


Lorenzo Orlando Caum

  • Support Staff

    •

April 4, 2014 at 12:15 pm

Hello,

I have not seen this error before. Thanks for bringing it to our attention.

Is the venue available in the Venues overview screen?

If so, could you click on it and try changing the status (toggle to draft and then to published)?

Then please try removing it again.

—
Lorenzo
Viewing 1 reply thread

The support post ‘Corrupt Venues after migration’ 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.

Home to preview versions of next-generation Event Espresso products.

Status: closed

Updated by Lorenzo Orlando Caum 10 years, 9 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server