Upgrading from 3.5.2 to 3.9.1
Make a copy of the site in localhost, this will be better approch. To upgrade site see Upgarding WordPress – Extended Instructions
Make a copy of the site in localhost, this will be better approch. To upgrade site see Upgarding WordPress – Extended Instructions
Edit line 149 in file.php as described in this thread: https://wordpress.org/support/topic/unable-to-update-plugins-after-upgrade-to-42 fixed it for me (on a linux host). edit: just read you are on windows: someone also posted a fix that applies to windows hosts there (apparently more complicated because backslashes are used in filepaths). so your line 149 in file.php should read: if … Read more
In my case (running on Centos 8), this error was caused by SElinux preventing apache (the login running the web server) from using the connect(2) system call. Try running in permissive mode — if that works, change your SELinux configuration as appropriate.
In my case the problem was caused by bad import of MySQL tables in phpMyAdmin. (I exported databases instead of only one database’s content. While importing MySQL errored with “Cannot create DB” but created the tables.) Testing INSERT INTO wp_options ( option_name, option_value, autoload ) VALUES (‘core_updater.lock’, 1592768373, ‘no’) (thanks @Rup) said I have a … Read more
You can create a content_filter that will update on the fly meaning that you don’t have to update all previous pictures and it will be the default so you don’t have to worry about your authors. something like this: function autoadd_rel_prettyPhoto($content) { global $post; $pattern = “/(<a(?![^>]*?rel=[‘\”]prettyPhoto.*)[^>]*?href=[‘\”][^’\”]+?\.(?:bmp|gif|jpg|jpeg|png)[‘\”][^\>]*)>/i”; $replacement=”$1 rel=”prettyPhoto[“.$post->ID.’]”>’; $content = preg_replace($pattern, $replacement, $content); return … Read more
Instead of wp_create_user, use wp_insert_user. So you will be able to set extra variables like nickname, display_name separately than the default value. For your case, you can code like this: $args = array ( ‘user_login’ => $user_name, ‘user_pass’ => $random_password, //send as plain text password string ‘user_email’ => $user_email, ‘nickname’ => $user_nickName, ‘display_name’ => $user_nickName … Read more
Yes, theme update will overwrite its folder completely. If you are using third party theme with possibility of updates the normal practice is to put your customizations into a Child Theme for it.
It is not recommended in any way to maintain a website on the 4.9.9 WordPress release to support legacy code that is poorly written. Although some of the security patches may be backported, scriptbots will target your website seeking out known exploits to access user data. According to WordPress: “The only current officially supported version … Read more
Yes, you should apply this update. To elaborate: WordPress releases major core updates (ie. 4.4.x to 4.5.x) regularly, about 2-3 times each year. In between these they will also release minor updates (ie. 4.4.1 to 4.4.2). The major updates typically introduce new functionality, enhance current functionality, and address non-critical bugs. The minor updates typically address … Read more
Both wp-includes and wp-admin folders contain core files of WordPress. You should never modify any of them, because it is crucial for WP to be able to change these folders during updates. Almost the same is true for all WP files placed in root folder – wp-config.php is the only file that WP won’t overwrite … Read more