Hide Welcome Panel for WordPress Multisite

With a major release update of WordPress, everytime all new functions will be displayed after updating. Basically a good idea, which displays all new features on one page. However, this is not always intentional. In the corporate environment, large groups of users aren't interested in it, so that this screen only provides additional work for the support team.
WordPress has implemented an option for every user. Therefore, a small function that suppresses the info screen and adjust the user settings, so this screen won't appear.

Continue reading …

Batch Plugin-Update in WordPress 2.9

In the past we have already informed you a little bit about the new features of the upcoming 2.9 version of WordPress - the development does not stop and the next version has many minor changes. Improvements in security, administration.

WordPress 2.9 will have the possibility to update all your Plugins, which have an update available, in one step.
That makes maintenance work with customer's and on your own blog more simple and faster. As a little insight, here is a screenshot of the current beta.

plugin-update-29

Caution When Updating To WordPress 2.8

Thanks to Heiko of WordPress Deutschland and Code Styling Project who brought up the problem on WordPress Deutschland:

Users reporting me, that they are missing files, after they automatically updated to WordPress version 2.8 and there were a problem while updating. I checked out the WordPress Trac and found a brand new record, which confirms this: Trac ticket # 10140

What happened and what are the conditions?

On one hand, the upgrade process has to be so far that the files were downloaded and unpacked. If anything goes wrong after these steps (wrong write permissions, etc.), the upgrade process makes a rollback and usually clears the downloaded files without any problems.

So much for theory. The practice shows, however, in exactly this case, because of a bug, previous existing installation files accidentally get deleted too, so the blog will no longer work!

What to do if already happened?

The best thing to do is to upload the old version completely via FTP. If the files are no longer available, you may download the old version from the archives of WordPress.org.
You should also verify if the wp-config.php needs to be adjusted, because this may also be deleted.

What lesson did we learn?

It’s not just a phrase, when we repeatedly emphasize, before you upgrade:

1. Create a current backup of the database
2. Create a current backup of all files on your web server.

As convenient as an automatic update can be, there is always a risk. If the web server is configured properly and is maintained well, there shouldn’t a problem arise. But the most users do not know or want to know if that’s the case. Therefore, the safest way is still to upload the new version via FTP.
Anyone who knows how everything has to be configured, I mean the pros among you, will surely continue to use the automatic upgrade.

What’s next?

This problem will be fixed, according to WordPress Trac entry, with version 2.8.1, and automatic upgrade will work again without any problems. But we think it is very important that the WordPress-Team let the users know about the problem and not just fix it in version 2.8.1 and be quiet about it. It will avoid a lot frustration!

But please don’t forget about your backups again, when you use 2.8.1 or future versions. It’s better “I have” than “if I would have”.

We still hope that you all continue to enjoy WordPress as we do, and we will continue to do our best to contribute you as quickly as possible with new information.

Update Informations Only for Admins

If you only want to let users, who are privileged to receive information about updates and plugins, you should copy the following code to your functions.php of your theme. These users have to have the right "edit plugin" (edit_plugins) to receive updates.

Alternative: use the plugin Secure WordPress, the plugin has inside the function to active this possibility.

/**
 * remove core-Update-Information
 * @rights: http://codex.wordpress.org/Roles_and_Capabilities
 */
if ( !current_user_can( 'edit_plugins' ) ) {
	// core update
	add_action( 'init', create_function( '$a', "remove_action( 'init', 'wp_version_check' );" ) );
	add_filter( 'pre_option_update_core', create_function( '$a', "return null;" ) );
	// plugin update
	add_action( 'admin_menu', create_function( '$a', "remove_action( 'load-plugins.php', 'wp_update_plugins' );" ) );
	add_action( 'admin_init', create_function( '$a', "remove_action( 'admin_init', 'wp_update_plugins' );" ), 2 );
	add_action( 'init', create_function( '$a', "remove_action( 'init', 'wp_update_plugins' );" ), 2 );
	add_filter( 'pre_option_update_plugins', create_function( '$a', "return null;" ) );
}

WordPress FTP Data With Constant

Since version 2.5 it's possible to update your Plugins automatically. It's necessary to input your FTP information before you update your Plugin.

It is very popular and an easy process, but I like to upload the newest version via my FTP client. How sure is the use of your FTP login information in your WordPress Admin? If you like to use another way, you can just put a definition of constants in your wp-config.php. Continue reading …