Tag Info

Hot answers tagged

9

If you're already using the SVN method, then keep using it. Trying to auto-upgrade an SVN site will probably fail due to all the extra .svn directories and such. Auto-upgrade doesn't do anything special or different. It's just replacing the WordPress files with the new ones. SVN will do the same thing.


9

First do not use 777, change it back to 755. Second you need to add the proper group permissions most likely to the same that Apache is running under. To find that out try: ps aux | grep apache You will see the Apache user group on the left. Now change your WordPress folder to the same user group, you can do this in a parent folder or sub folder ...


9

"the boring work of backup"... Backups may be boring, but they are essential and gives you a fallback position in case things go wrong. Without backups, you're essentially playing Russian roulette with your site. It doesn't even take very long, and reverting isn't horrible or awful, it's pretty easy. WP veterans take backups, test upgrades on ...


6

Neal, The simple fix is to change the user and group ownership of the files making them the same that PHP runs under. With shared hosting (100's of accounts on the same server) a special mod is used to allow PHP to run as your user account. Most likely this is your situation. There are 2 simple fixes for this. Add the following to your wp-config.php: ...


6

The other way is to have people add their own sub-plugin. For example, the code in your core plugin that gets the skins could be something like: function get_available_skins() { $skins[] = '/includes/default-skin.css'; $skins[] = '/includes/2012-skin.css'; return apply_filters( 'get_available_skins', $skins ); } Then, users can create a ...


6

I use XAMPP myself, but WAMP isn't much different. I'll bet you have not enabled the curl module. WordPress can use other methods (streams and fsockopen) as a fallback, but these may be disabled by default as well in a stock install. Curl is preferred and easy to enable. Close WAMP Go your the \bin\php\version directory in WAMP Edit the php.ini, and ...


5

I had the same problem recently. For some reason the option db_upgraded isn’t set by the upgrade process. Fix Go to /wp-admin/options.php. Fill the field db_upgraded with a 0 (zero). Hit Save Changes. Done.


5

Don't remove the action but add your own before it. If you remove the action you will never get the message saying it was upgraded successfully. Here you can provide your own info on what to do next. function tp_dont_redirect_to_about_wordpress( $new_version ) { global $wp_version, $pagenow, $action; if ( version_compare( $wp_version, '3.4-RC1', ...


4

If you didn't disable all your plugins before updating do it manually by renaming the wp-content/plugins directory. Clear your browsers cache and all cookies and try again. If your still having the problem open the file wp-includes/version.php to make sure it is the correct file for 3.1.3. You should see this database version: /** * The WordPress ...


4

If it is an older version of WP, you need to find out what version of WP generated the database, as WP upgrades the DB most times the files are upgraded and you should incrementally upgrade to also upgrade the database. Look in the wp_options table for option 711 and see what the version is; option name will be site_transient_update_core and the value will ...


4

I could be missing something, because I'm not sure why you're talking about using the import functions, but you could download a few older versions from the release archive and upgrade incrementally. Try going to 2.5, then 2.9, then 3.1. If there's some reason you're concerned that won't work, could you provide more details on the situation?


4

Yes, I would say you should upgrade to WP 3.1 instead of importing content in WP 3.1 Like Ian said, you should do an incremental upgrade. I have seen the upgrade working from 2.2.1 to 3.1 directly (Check this tweet) But lets say you should download and over write 2.3 files over your installation. BRowse in your dashboard, it will ask you to upgrade ...


4

If you site is live then you shouldn't directly update that, although update in the recent version of wordpress is very easy and seemless but that wasn't the case in 2.1 though. Also here is the list of steps that I will recommend you to take: Make the list of all plugins. Make sure none of the plugin's are responsible for site's main functionality. (As ...


4

When a major release is made, fixes are made to it, but it's rare that fixes to older versions are made. It has happened before, but it should never be relied upon, and there are a lot of bugfixes that are never backported. Sometimes a version will be tagged before a major release that isn't publicly announced, but these shouldn't be used if you have the ...


4

It fails because there is already a theme with that name on the server. So the obvious solution is to remove the theme before you upload the new version. If you're wanting to use an update mechanism like the theme repo, but on a custom theme, there are udpater classes you can add, such as this one: https://github.com/UCF/Theme-Updater That particular one ...


4

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.


4

Many plugins use /wp-content/custom-plugin-folder/ to store customized plugin data (WPTouch comes to mind). Just use the constants WP_CONTENT_URL and WP_CONTENT_DIR Docs to check for the existence of your folder and retrieve any available skins. The following article, although not directly related to this Question, explains the importance for ...


4

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


4

The virus part is going to be off-topic, but yes a fresh install is the way to go. What I would do to upgrade the site is: Backup everything-- PHP and database Install the old site on a development server. Before running the site, replace all of the core files with new 2.8 ones from the archive. This will hopefully fix the suspected virus problem. Then ...


3

You can remove you plugin from the updateble list with: add_action( 'plugins_loaded', function(){ add_filter( 'site_transient_update_plugins', function ( $value ) { if( isset( $value->response['google-analytics/google-analytics.php'] ) ) unset( $value->response['google-analytics/google-analytics.php'] ); return ...


3

Delete everything but wp-content and wp-config.php, copy the fresh installation into the directory. On upgrading WordPress will use the database to see what should be done, not the files. Not all files are deleted automatically, because some of them might still be used by outdated plugins or external scripts (the old feed files are good examples for this ...


3

The first thing to try: Manually download a fresh copy of Wordpress Log into the FTP account and upload everything EXCEPT the wp-content folder It is important that you do NOT copy over the wp-content folder or the wp-config.php files. These are custom to each site. This will allow you to make sure the upgrade is complete. If that doesn't work, you ...


3

That error is probably due the use of cURL in the Wordpress multisite updating proccess. By default cURL will try to verify the SSL certificate with an accepted CA in a bundled set of CA certificates. You have at least four options: Make sure you are using the last version of cURL in your PHP installation to ensure the set of used CA is updated. Manually ...


3

Review this WordPress codex guide: http://codex.wordpress.org/Upgrading_WordPress_Extended#Detailed_Upgrade_Instructions_for_1.5.x.2C_and_versions_2.0_-_2.6.5.2C_to_3.1.2


3

I'm not aware of any solutions for iterating through and automatically updating your list of plug-ins, but my guess is that any system that can automatically update WordPress itself can be modified to update everything in fairly short order. That said, I know of two good ways to update WordPress automatically: WP Remote This is an online service that ...


3

Any database changes WP itself needs are performed automatically. On first load after core update you will get (if required) special page that will say that database update is required and perform that update. No actions required from you really. Changes and updates to database by plugins can vary and not many plugins actually need or perform them. If you ...


3

From the quick look at code: This message is triggered by maintenance_nag() function. The only condition to trigger is if $upgrading variable is defined. $upgrading variable is defined by including .maintenance file. So I reason that file is present, there is no other path to this message that I see in code. File starting with dot are regarded as ...


3

Hi @silent: This was recently discussed at length on the wp-hackers list. Here's the thread: Will Activation Hook Be Executed During Plugin Upgradation? Quoting Otto from the list: The simplest method that would work everywhere would be simply to store the version number of the plugin somewhere (like in your options entry in the database), ...


3

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: ...


3

There is no point disabling updates. Its a security risks. If a theme doesn't provide enough flexibility to customize through its theme option one should use a child theme. That way he can update the original theme and and take advantage of new features. If you using a older version wordpress you are wide open to attack. Trust me they will get in sooner or ...



Only top voted, non community-wiki answers of a minimum length are eligible