I’ve actually just fixed it myself. The problem was as follows: I had changed the username of the admin account to ‘new-admin’. What I had missed when making this change was to update the ‘wp_sitemeta’ table in the database. meta_id 8 (site_admins) still had the old admin name set. Once I updated this, the plugins … Read more
From quick search of source for this error message, it is likely to be triggered by failed move_uploaded_file() function call, which is native PHP and not WordPress. Documentation says that it has some restrictions, related to safe_mode and open_basedir so that might be your issue. Since WP suppresses error output from this function with @ … Read more
Your problem seems to be related with a misconfiguration of the temporary directory in PHP which is used for uploads and need to be writable when the sever downloads a WordPress, plugin or theme package. If you can not configure it at PHP level, you can define it also in wp-config.php file: define(‘WP_TEMP_DIR’, ABSPATH . … Read more
Adding these two lines to the wp-config.php file solved the problem: define(‘FS_CHMOD_FILE’, 0644); define(‘FS_CHMOD_DIR’, 0755);
I finally found the solution. function checkUserPermissionsInThisScreen(){ if (is_admin()){ $currentUserRoles = wp_get_current_user()->roles; if (in_array(‘shop_manager’, $currentUserRoles)){ $a = get_current_screen(); if ($a->id != ‘edit-shop_order’ && $a->post_type != ‘shop_order’){ wp_die(‘you do not have needed permissions to see this page’); } } } } add_action(‘current_screen’, ‘checkUserPermissionsInThisScreen’);
The web installer writes configuration data into that file. It needs write access for that. I don’t think this was your backdoor. There was probably a plugin or an old theme with timthumb that had a vulnerability.
Checkout User Roles and Capabilities Plugin
I Resolve this.. looks like the force upgrade change the option_value of wp_user_role under wp_option. so i replace it with the fresh value.. thank you
I have had the same issue and it is do to how apache and wordpress communicate. It has to have both owner and group permission to install from backend. The only really way to get around this is to see if your host has a server setup that way or you get your own server … Read more
You will need to restore the database prefix after using it , with something like this global $wpdb; $previousPrefix=$wpdb->prefix; $wpdb->prefix=”mainsiteprefix_”; //Database access goes here $wpdb->prefix=$previousPrefix; or you can create a new wpdb object like this: $wpdb2 = new wpdb( DB_USER, DB_PASSWORD, DB_NAME, DB_HOST );