Back up all your files and database And then install wp3.5 and activate each plugin one by one and see whether they are compaitable or not OR you can install a wp3.5 in any other subdomain(domain.yoursite.com) and then activate all those plugins and see if they are compaitable or not
In a nutshell that should be considerably straightforward, WP just couldn’t update itself in versions that far back. Codex has detailed instructions for upgrading from older versions, see Upgrading WordPress Extended. However overall it’s usual for manual update – backup, replace core files, go through upgrade dialogs.
A hint to the functions that I need to use. I’m not sure why you’ll want to mimic WP’s default behavior, but most of the update logic lies on wp-admin/update-core.php Check for do_core_upgrade().
I had this problem and the answer was found (a) in enabling ftp to write and (b) at least temporarily setting the directories to 777 although I think the latter permissions can be improved. I run vsftp with chroot’d users. After finding no mention in apache logs, setting the permissions to 777, changing ftp group … Read more
Your problem seems to be related with a misconfiguration of the temporary directory in PHP which is used for uploads and need to be writable when the sever downloads a WordPress, plugin or theme package. If you can not configure it at PHP level, you can define it also in wp-config.php file: define(‘WP_TEMP_DIR’, ABSPATH . … Read more
You’re confusing the self-hosted WordPress software (that Bluehost is hosting for you) and the WordPress.com service. They’re not the same thing. You can read about the differences here: https://en.support.wordpress.com/com-vs-org/
Disable your plugins via FTP, by renaming the plugins folder. I found MANY plugins cause a “white page” issue. Need to wait for upgraded plugins or WP fix.
Most of these errors are caused by damaged or corrupt theme files. Upload theme files/directory again and you will be fine. Strange things happen sometimes, that’s why it’s always recommended to keep a backup of your WordPress files and database before updating.
In file wp-admin/includes/class-wp-filesystem-ftpext.php, line 333: Replace $file_list = @ftp_nlist( $this->link, ‘-a ‘ . $path ); With $file_list = @ftp_nlist( $this->link, $path );
You are facing the issue due to the different database versions. Please, follow this steps to fix the issue: Head to /wp-include/ folder. Open the version.php file. Find the value for $wp_db_version. Open your database. Find wp_options. Use the following line to identify the value of db_version: SELECT option_value FROM yourdatabase.wp_options WHERE option_name=”db_version”; The values … Read more