Tag Info

Hot answers tagged

11

Instead of using the code from the question in functions.php, replace it with this: /** * Prevent certain plugins from receiving automatic updates, and auto-update the rest. * * This function could easily be altered to do the opposite, by auto-updating specific * plugins and excluding the rest. * * Also, by using the 'auto_update_theme' or ...


6

You are correct, Wordpress checks for updates to core and plugins every 12 hours, but a better way to word it would be: it checks updates if last update was more than 12 hours ago. The 12 hour setting is hard codded in wp-includes/update.php The last updated dates are stored in wp_options table and the options are: _site_transient_update_core ...


5

The relevant functions wp_update_plugins() and wp_maybe_auto_update() are hooked to the wp-cron events of same name, running on twice daily schedule. Logically the initial schedule will start to tick from the time of first run. Due to wp-cron implementation (not being real cron and trigered by site visits rather than server clock) it will also "drift" ...


4

Disable Plugin updates all together It should be as easy as that: <?php defined( 'ABSPATH' ) or exit; /* Plugin Name: (#120589) Disable Plugin Updates */ remove_action( 'load-update-core.php', 'wp_update_plugins' ); Deny (or reroute) Updates for Themes/Plugins Single core and theme updates can be deactivated by this script my Mark Jaquith: For ...


4

From my perspective there are about two issues with your plan - Git and "conventional" structure. So basically everything. :) Git (and version control in general) is poor tool for whole site stacks. Been there, done that, it hurt a lot. What you call "unconventional" structure with content separated from core has been for a while very conventional and ...


3

WP checks for updates by sending data about all plugins and themes to the repository. To prevent false update messages for your own code you need to selectively scrub it out of those requests. The example for theme by Mark Jaquith: function cws_hidden_theme_12345( $r, $url ) { if ( 0 !== strpos( $url, 'http://api.wordpress.org/themes/update-check' ) ) ...


3

The setting you are looking for is found in "Settings"=>"General"=>"E-Mail Adress". All the Emails WordPress or Plugins send out are sent to the admin_mail, which is returned by get_option( 'admin_mail' ), and this Emailadress is not always connected to a user. If you first install WordPress, the first user created gets the role administrator, and the same ...


2

make a copy of the site in localhost,this will be better approch.To upgrade site see below link. https://codex.wordpress.org/Upgrading_WordPress_-_Extended_Instructions


2

From development point of view the most practical way to detect and locate changes is version control - comparing against SVN/Git checkout of core or use such checkout directly. However there are also plugins around that verify files against set of hashes. I think Sucuri Security recently got such feature. The practical limitation of them is for which ...


2

Yes you can do that… define( 'DISALLOW_FILE_MODS', true ); Put this snippet in your wp-config.php file and you will able to disable core and plugin updates.


1

This type of development falls into the "not so easy and requires a custom workflow that might take a long time to be happy with". I find Subtrees, submodules or nested repos, a huge pain in the ass. Some thoughts (track everything). Enable auto updates with git/svn using: add_filter( 'auto_upgrade_ignore_checkout_status', '__return_true' ); Safe ...


1

From quick look at the code upgrade motions are performed by wp_upgrade() function. I imagine calling it in some way would get it done, but postponing it until normal upgrade process is fixed is probably more efficient. In recent versions WP rarely does major changes to DB and it's reasonable expectation for it to not need database upgrade urgently after ...


1

There is a bug in some versions of PHP itself, unzip hangs. PHP 5.2.17 hangs, PHP 5.3.24 works as expected. PHP Change Log http://www.php.net/ChangeLog-5.php#5.3.4 says PHP Version 5.3.4 released 09-Dec-2010 - "Fixed crash in zip extract method (possible CWE-170)". (Note: 5.3.24 released 11-April-2013, and is no longer the latest version.) ...


1

Well it looks like it's running ok from front end. I did get a notice saying that your Wordpress Database needed upgrading though. I'd suggest you visit: http://www.azraar.com/wp-admin and click that (after backing up your DB as previously suggested) as it might fix your problem. Good luck


1

Probably the update wasn't complete and some files are missing. If you have FTP access, follow these steps. Download you wp-config.php and save it somewhere. In the wp folder on server delete everything but the wp-content folder Have a DB backup, if you can Download from wordpress.org the zip of wordpress and extract it At this moment remove the ...


1

Best Practice #1 One of the best practices is to let the PHP process to run under a different user (in your case: jdoe, jsmith, etc) than the web server user (in your case: httpd) and let only these users have the write permission. Of course, your web server may still need read permission for all these files. For this solution to work, you may need to go ...


1

In your finctions.php add_filter( 'auto_core_update_send_email', '__return_false' );


1

If my guess is right that you think you add your site URL inside the plugin's head and it will magically update everyones plugin, then I have to tell you that wont work. You have choices: Either you host your plugin on wordpress.org and updates work pretty much without you doing anything then pushing your plugin to svn with the right stable tag in the ...


1

Since version 3.7 it is, see https://codex.wordpress.org/Configuring_Automatic_Background_Updates.


1

You might like to check out this plugin which allows you to change where the email goes: background-update-notification-email-address


1

You can use auto_core_update_email filter to change the default admin email. add_filter( 'auto_core_update_email', function($email){ $email['to'] = 'updateWP@example.com'; // Override email address return $email; });



Only top voted, non community-wiki answers of a minimum length are eligible