Tag Info

New answers tagged

0

How to disable core auto updates but enable plugins and themes auto updates If you want to stop the autoupdates of the WordPress core, but to enable them for your Plugins and/or Themes, you can add these lines in the wp-config.php file: Stop the core auto updates: define( 'WP_AUTO_UPDATE_CORE', false ); Then Enable the plugins/themes: ...


2

The "autoupdate" value you see there is just a string in the "response" field from the version check API call. It doesn't determine whether or not your site actually performs an autoupdate. You'll see that field in every response returned from core version checks. Basically, it's just saying that a potential autoupdate is available for download. The ...


1

In WordPress, there are four types of automatic background updates: Core updates Plugin updates Theme updates Translation file updates If you don't like this, then add the constant to deactivate this feature in the wp-config.php, that it works on a default install. Constant to Disable All Updates define( 'AUTOMATIC_UPDATER_DISABLED', TRUE ); Constant ...


0

This might not solve your problem directly, but I would like to mention that if you want to avoid WordPress.org you can host your plugin on GitHub (or Bitbucket). There is a updater plugin for that and on Tut+ is a good Tutorial for that: Distributing Your Plugins in GitHub with Automatic Updates


0

Your 'mixed' experiences probably come from wether your two users in question are in the same group or not. And of course what “group rights” happended to be around Traditionally in php, the phpuser (aka apacheuser or webuser or cgideamon) has no right to change files, which only the ftpuser (aka “your user account“ in some codex descriptions) can, to make ...



Top 50 recent answers are included