Well, of course, you have a complete and full backup to start – DB and files. Has to be said if this is going to be a complete answer. It is hard to tell quickly what the problem could be when a WP upgrade produces a failure like you describe. Most likely it is the … Read more
I don’t think anyone can give you a guarantee that you will have no problems, however typically WordPress handles the upgrade process very well. You are only a couple of versions behind so I wouldn’t anticipate any major problems. You should consider: Back up all the files and database before proceeding. If you don’t know … Read more
this is the line causing the problem for you. define( ‘WP_CONTENT_URL’, get_option(‘siteurl’) . ‘/wp-content’); this could be get_option(‘siteurl’) is not a string. please check what you having at wp-option table and siteurl row. If possible check what you are getting when you run get_option(‘siteurl’); this line
Your code works for me in version 4.7.2 with 2016 theme, but a slightly simpler version is to remove the action entirely rather than filter the output: remove_action( ‘wp_head’, ‘wp_generator’ );
It’s not right in front of you, but you can obtain this information from the back end. Go to Tools -> Site Health -> Click on Info tab. Clicking on the first drop-down (‘WordPress’) will get you the current version and the latest.
Probably. Just do the following before updating: Do a direct SQL backup of the database Export your site content Disable all Plugins Switch to the default Theme Then update to the latest version. If anything goes wrong, just restore from your backups, and try an iterative update.
You can do this with the function get_bloginfo(). There is a special paramater called version that retrieves the wordpress version from the $wp_version variable set in wp-includes/version.php. So you could do something like this function register_jquery_wp_version() { global $wp_version; if ( $wp_version >= 3.8 ) { // register and enqueue jquery A }elseif( $wp_version >= … Read more
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 … Read more
I would be very afraid to develop on 3.8.1 and try to run the same code on 3.5.1. Things have changed. 3.5.1 is ancient by web app standards. I can’t say that I have ever tried to “backport” like that, but it does worry me. Much of your code would work. WordPress itself is pathologically … Read more
TimThumb has never been bundled with WordPress, it is/was entirely a third-party theme/plugin issue.