WordPress not allowing me to create posts upon migration
-
Hi there
We have recently moved our WordPress site from host A to host B. The migration has went smoothly except for an issue where we cannot create any new content correctly, ie a post, user or page.
The following screenshot shows the WYSIWYG has disappeared once we click on “new post”. Custom fields remain.
We have tried replacing all wp-include and wp-admin files with a “fresh” copy directly from WordPress 3.7.5, plus other loose files in the wp directory but the problem still exists.
We have tried disabling all 25 plugins and reverting our theme to Twenty Twelve.
We have also tried repairing the database, but none of these options allowed us to post or create content.
Thanks in advance.
-
– Your browser can help you identify JavaScript issues or conflicts. Do you have any Javascript errors in the console when looking at the editor page? This article can assist you in doing that diagnosis.
– If you use any caching systems, like Cloudflare, clear those caches.
– Check that the file permissions of all the PHP files are set correct (i.e., 644).
– Specifically check files like /wp-includes/js/tinymce/wp-tinymce.php and such.
– If the permissions are incorrect, then some servers running security code like suhosin won’t allow those files to run.Thanks, here are the error logs brought up by the console:
style.css Failed to load resource: the server responded with a status of 404 (Not Found) /var/www/vhosts/[URL]/httpdocs/wp-content/themes/gonzo/includes/classes/meta-box/css/color.css?ver=4.1.1 Failed to load resource: the server responded with a status of 404 (Not Found) load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,plupload&ver=4.7.5:9 JQMIGRATE: Migrate is installed, version 1.4.1 gonzo.js Failed to load resource: the server responded with a status of 404 (Not Found) clone.js Failed to load resource: the server responded with a status of 404 (Not Found) color.js Failed to load resource: the server responded with a status of 404 (Not Found) gonzo.js Failed to load resource: the server responded with a status of 404 (Not Found) color.js Failed to load resource: the server responded with a status of 404 (Not Found) floaticons.js:14 Uncaught SyntaxError: Unexpected token * style.css Failed to load resource: the server responded with a status of 404 (Not Found) color.css Failed to load resource: the server responded with a status of 404 (Not Found) load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,plupload&ver=4.7.5:4 POST https://[URL]/wp-admin/admin-ajax.php 504 (Gateway Time-out) send @ load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,plupload&ver=4.7.5:4 ajax @ load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,plupload&ver=4.7.5:4 n.(anonymous function) @ load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,plupload&ver=4.7.5:4 blcDoWork @ post-new.php:843
And here’s the debug mode
iption_Walker::start_el(&$output, $item, $depth, $args) should be compatible with Walker_Nav_Menu::start_el(&$output, $item, $depth = 0, $args = Array, $id = 0) in /var/www/vhosts/[URL]/httpdocs/wp-content/themes/gonzo/functions.php on line 0 Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Sidebar" sidebar. Defaulting to "sidebar-1". Manually set the id to "sidebar-1" 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 /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 4138 Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Footer Column 1" sidebar. Defaulting to "sidebar-2". Manually set the id to "sidebar-2" 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 /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 4138 Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Footer Column 2" sidebar. Defaulting to "sidebar-3". Manually set the id to "sidebar-3" 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 /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 4138 Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Footer Column 3" sidebar. Defaulting to "sidebar-4". Manually set the id to "sidebar-4" 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 /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 4138 Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Footer Column 4" sidebar. Defaulting to "sidebar-5". Manually set the id to "sidebar-5" 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 /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 4138 Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the "Header Banner" sidebar. Defaulting to "sidebar-6". Manually set the id to "sidebar-6" 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 /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 4138 Notice: The called constructor method for WP_Widget in Slipfire_Widget_Tabber is deprecated since version 4.3.0! Use __construct() instead. in /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 3893 Warning: Missing argument 2 for wpdb::prepare(), called in /var/www/vhosts/[URL]/httpdocs/wp-content/themes/gonzo/includes/widget_areas.php on line 154 and defined in /var/www/vhosts/[URL]/httpdocs/wp-includes/wp-db.php on line 1291 Notice: wpdb::prepare was called incorrectly. The query argument of wpdb::prepare() must have a placeholder. Please see Debugging in WordPress for more information. (This message was added in version 3.9.0.) in /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 4138 Notice: The called constructor method for WP_Widget in video_widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 3893 Notice: The called constructor method for WP_Widget in fans_widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 3893 Notice: The called constructor method for WP_Widget in WP_Widget_Recent_Posts_Thumbnails is deprecated since version 4.3.0! Use __construct() instead. in /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 3893 Notice: The called constructor method for WP_Widget in best_reviews_widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 3893 Notice: The called constructor method for WP_Widget in DP_Flickr_Widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 3893 Notice: add_object_page is deprecated since version 4.5.0! Use add_menu_page() instead. in /var/www/vhosts/[URL]/httpdocs/wp-includes/functions.php on line 3830 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-includes/post.php on line 5880 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-includes/post.php on line 5881 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-includes/post.php on line 5885 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-includes/post.php on line 6102 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-includes/theme.php on line 2833 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-includes/post.php on line 3993 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-includes/post.php on line 3993 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-includes/post.php on line 3494 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/post.php on line 609 Warning: Creating default object from empty value in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/post.php on line 641 Notice: Undefined property: stdClass::$ID in /var/www/vhosts/[URL]/httpdocs/wp-admin/post-new.php on line 84 Notice: Undefined property: stdClass::$post_date in /var/www/vhosts/[URL]/httpdocs/wp-admin/edit-form-advanced.php on line 133 Notice: Undefined property: stdClass::$post_status in /var/www/vhosts/[URL]/httpdocs/wp-admin/edit-form-advanced.php on line 185 Notice: Undefined property: stdClass::$post_status in /var/www/vhosts/[URL]/httpdocs/wp-admin/edit-form-advanced.php on line 219 Notice: Undefined property: stdClass::$post_type in /var/www/vhosts/[URL]/httpdocs/wp-includes/taxonomy.php on line 201 Notice: Undefined property: stdClass::$post_type in /var/www/vhosts/[URL]/httpdocs/wp-includes/taxonomy.php on line 203 Notice: Undefined property: stdClass::$post_status in/var/www/vhosts/[URL]/httpdocs/wp-admin/edit form-advanced.php on line 591 Notice: Undefined property: stdClass::$post_type in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/meta-boxes.php on line 25 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/meta-boxes.php on line 27 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/meta-boxes.php on line 27 Notice: Undefined property: stdClass::$post_status in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/meta-boxes.php on line 40 Notice: Undefined property: stdClass::$post_status in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/meta-boxes.php on line 40 Notice: Undefined property: stdClass::$post_status in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/meta-boxes.php on line 40 Notice: Undefined property: stdClass::$post_status in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/meta-boxes.php on line 41 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-includes/post.php on line 1634 Notice: Trying to get property of non-object in /var/www/vhosts/[URL]/httpdocs/wp-includes/post.php on line 1634 Notice: Undefined property: stdClass::$post_status in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/meta-boxes.php on line 80 Notice: Undefined property: stdClass::$post_status in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/meta-boxes.php on line 100 Notice: Undefined property: stdClass::$post_status in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/meta-boxes.php on line 100 Visibility: Notice: Undefined property: stdClass::$post_status in /var/www/vhosts/[URL]/httpdocs/wp-admin/includes/meta-boxes.php on line 131 Public
I still need to go through them properly but nothing jumps out to me (and my beginner knowledge)
-
This reply was modified 7 years, 10 months ago by
Bravo315.
Hi Jack,
gonzo.js Failed to load resource: the server responded with a status of 404 (Not Found) clone.js Failed to load resource: the server responded with a status of 404 (Not Found) color.js Failed to load resource: the server responded with a status of 404 (Not Found) gonzo.js Failed to load resource: the server responded with a status of 404 (Not Found) color.js Failed to load resource: the server responded with a status of 404 (Not Found)
Gonzo.js could be a JavaScript file that’s important to the theme, could be worth checking if that file is in the backup or on the server. If it is you’d need to check that the files are enqued correctly and if they’re missing completely try find them and add them in. If that doesn’t do anything do the same for all other JS files.
Good catch, it looks like the post-new.php is calling up
https://[site]/var/www/vhosts/[site]/httpdocs/wp-content/themes/gonzo/includes/classes/meta-box/css/style.css
when it should be calling up
https://[site]/httpdocs/wp-content/themes/gonzo/includes/classes/meta-box/css/style.css
Weirdly, it’s only calling up the wrong directory on those 9 requests, so will look into why.
Thanks.
-
This reply was modified 7 years, 10 months ago by
Bravo315.
-
This reply was modified 7 years, 10 months ago by
- The topic ‘WordPress not allowing me to create posts upon migration’ is closed to new replies.