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 new host - upgrading to 3.1.27.1.P and getting 404 error | Event Espresso - Staging Server
I just moved from godaddy to a new host. Its so much faster again.
The new install is sort of working.
Only EE and Calendar pluggins are able to activate.
When I attempt to activate the following ones, it breaks by giving me a white screen on the plugins folder in wp-admin or not letting me in wp-admin at all. Then I have to rename the plugins folder, log into wp-admin, and then rename the folder back. All the plugins are deactivated at again. Then I start over. I was thinking installing the latest version might solve some of this. But I get the 404 error when I try to do that.
Not activated now is:
Must have:
Groupons
recurring
Optional?:
Udesign designate short code insert button
From my hosting service – West Host (they are good!) “I also increased the memory_limit in php.ini from 32M to 64M, which may have been responsible for the trouble.”
All my wp-admin and plugin problems are gone! Thanks!
This reply was modified 12 years, 3 months ago by sconklin.
This reply was modified 12 years, 3 months ago by sconklin.
Viewing 2 reply threads
The support post ‘new host – upgrading to 3.1.27.1.P and getting 404 error’ 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.