I had a similar situation with my WordPress install and Softaculous, what I found was that the version it was telling me to install (or upgrade to) was actually a minor version BEHIND the version of WP that was considered to be current at the time. In my situation I simply ignored it and had … Read more
Since: upgrade endpoint in question doesn’t seem to be behind login wall no user action is required other than visiting it I would imagine requesting the suggested URL with some CLI tool for HTTP requests (curl and wget are commonly available) should accomplish upgrade.
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
Your question is way too broad to answer thoroughly. By far the most common type of issue is a theme/plugin that is incompatible with the new WP version. So you want to check that first. The upgrade from 4.5 to 4.6, for instance, brought more thorough error catching, prompting plugins to stumble over errors that … Read more
You can use site_transient_update_plugins hook to disable plugin updates. function filter_plugin_updates( $value ) { unset( $value->response[‘plugin_folder/plugin_name.php’] ); return $value; } add_filter( ‘site_transient_update_plugins’, ‘filter_plugin_updates’ );
This error indicates that your SSL certificate has either expired or is corrupted. I came across this error recently on a local WordPress installation and the solution is as follows: Download the latest cert.pem file from https://curl.haxx.se/docs/caextract.html Save this file (called cacert.pem) in your php installation directory Open php.ini in an editor and search for … Read more
WordPress is unaware of what kind of database server you’re using, as long as it accepts MySQL flavour SQL, can be communicated with via the mysqli PHP extension, and supports the feature set of the minimum requirements, WordPress is happy. As a result, none of the concerns you need to worry about are related to … Read more
Hi @ripper234: Either 1.) edit the plugin header comment in the main plugin file and change the Version: value to something like 999, or 2.) move the plugin to the “Must Use” plugin directory: /wp-content/mu-plugins. Here’s an example from /wp-content/plugins/akismet/akismet.php of the plugin header comment for Akismet: /* Plugin Name: Akismet Plugin URI: http://akismet.com/ Description: … Read more
This is definitely not error message produced by WordPress, so it comes from server software. Please check server logs (if you have access and skills) and ask your hosting support to look into it. It is hard to make a good guess from this little information.
From the codex: Note: When using ‘some string’ to show as a submenu of a menu page created by a plugin, this item will become the first submenu item, and replace the location of the top level link. If this isn’t desired, the plugin that creates the menu page needs to set the add_action priority … Read more