Tag Info

New answers tagged

1

There is problem with the "wordpress-seo" permission so please following steps. There are two way 1) Upload from the wp-admin Step 1 -> Change the "wordpress-seo" permission or rename the "wordpress-seo" plugin to another Step 2 -> If you have change the permission then just upgrade the plugin and if you have rename the plugin dir then you need to ...


0

Yeahh! I finally found a solution! The trick was to set all files and folders their ownership and group to the apache user. Make sure you've an directory for temporary storage and you need to have the ../wp-content/upgrade/ directory as well. Than at your wp-config.php this is the only thing I'm not aware about of the compatibility of it. But you'll need ...


6

Set the constant DISALLOW_FILE_MODS to TRUE in your wp-config.php: const DISALLOW_FILE_MODS = TRUE; See the Codex for background information: Setting this constant also disables the Plugin and Theme editor (i.e. you don't need to set DISALLOW_FILE_MODS and DISALLOW_FILE_EDIT, as on its own DISALLOW_FILE_MODS will have the same effect). It will also ...


0

There are quite a few related bits you can tinker with, but the one most comprehensive setting for version controlled stack is define( 'DISALLOW_FILE_MODS', true );. It will disable anything related to changing code files, core or extensions either.


0

Hansy's solution was not working for me as I was using WP 3.5. I wanted to update to WP 3.7.8. I based my solution on Hansy's with a few changes. add_filter('pre_site_option_update_core','wpse_26750' ); add_filter('site_transient_update_core','wpse_26750' ); function wpse_26750($updates){ global $wp_version; // If current version is 3.7.8 or higher ...



Top 50 recent answers are included