New answers tagged upgrade
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 ...
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 ...
Short Term Solution As per the answer at: http://stackoverflow.com/a/9984309/1983389 you can suppress the warning messages via changes to your php.ini or .htaccess file. In your php.ini change error_reporting = E_ALL to error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT If you don't have access to the php.ini, you can ...
You're WordPress install is out of date. Upgrading to the latest version ( 4.0.1 at time of writing ) should fix those issues, while fixing hundreds of other bugs and security issues. As a side note, you should always keep both your PHP and WordPress installs at the latest versions. Select PHP 5.4, and move to 5.5 and 5.6 as they become available. They fix ...
The right solution is checking the server TIME. If it is wrong SSL doesn't work fine.
What version of WordPress? It's late and I'm tired but basically, the code is out of date. The site must be ancient. 5.2 was released in 2006 and 5.3 in 2009. As the only variable that's changed is the PHP version, I'm confident it's that. Time for a rewrite perhaps.
If you are using vsftpd as your FTP server and have enabled passive connections, you need to add pasv_promiscuous=YES to /etc/vsftpd/vsftpd.conf.
When WordPress shows themes/core/plugins are updated, it means they were successfully upgraded. Which means WP was able to download the zip, extract it then able to put/overwrite files into the file system. WordPress does not save plugin/theme versions as a database entry they are directly read from plugin files and theme css. Theme/plugin/core bundle are ...
From the error you posted, I suspect that there was some kind of file corruption. The original file /wp-includes/post.php shouldn't end at line 235. The file should have 5841 lines (in WP version 4.0 and 4.0.1). If it was a file corruption and the error doesn't appear anymore, the update probably "healed" the damage by overwriting the file. Nevertheless I ...
Top 50 recent answers are included