ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Automatically Upgrade WordPress Plugins

Updated on December 2, 2012

Update Your WordPress Plugins Automatically

Today there is hardly any WordPress driven website or Blog that does not use plugins to extend WordPress core functionality. Most WordPress driven websites or Blogs use at least a couple of plugins, which can extend to a modest fifteen or twenty plugins ( or more ) on WordPress driven E-Commerce websites or Blogs. The bottom line is that having plugins on a WordPress driven website or Blog is inevitable.

Is There A Real Reason To Bother?

Thanks to the open nature of WordPress, plugins can be developed quickly to meet any need or desire to extend the functionality of the WordPress core. However, when plugins are installed on a WordPress CMS, site or Blog behavior can begin to get a wee bit messy.

Sometimes plugins will conflict with one another, or someone discovers a bug in s specific plugin and informs the plugin creator who ( hopefully ) releases an update. Sometimes the demand for a specific plugin is so great, that the plugin gets released a little early ( i.e. prior being sufficiently tested ) and can have a few strange bugs that must be squashed. All of this warrants that the plugin be updated.

Security is another reason. When a new Plugin comes out, unscrupulous people try and take advantage of any vulnerability within the Plugin codespec, to hack into and take over your Website or Blog and then do all sorts of nasty stuff there.

Hence, even if a single plugin in used with WordPress, keeping that plugin up-to-date is important to ensure the security ( and functionality ) of the WordPress core.

This used to be a quite manual job:

  1. You would have to log into the WordPress Admin section
  2. Manually check if any plugin in use needed updations
  3. Download the updated plugin from its source
  4. Disable / Uninstall the current plugin
  5. Install the updated plugin
  6. Activate the newly installed plugin
  7. And the job was done

A fairly, painstaking, long drawn, systematic process.

Ever since WordPress version 2.7, this entire process has been automated for you, reducing the effort required to keep your plugins up-to-date.   All that is necessary to help you keep all your plugins up-to-date is built into the WordPress core. 

BTW, this is an excellent reason to update your WordPress core framework but I’m keeping that for another Hub.  The latest version of WordPress ( at the time of writing this Hub ) is WordPress 3.0.1.

How Does This Work?

Thanks to the Automatic Upgrade feature built into the latest versions of WordPress, when you login to your WordPress Admin dashboard, adjacent to the menu item Plugins you could see a number.   The number indicates how many plugins have to be upgraded.   Click the menu item Plugins and a list of all the Plugins used with the WordPress core will be displayed.

Below each plugin that requires updation there will be a message displayed that indicates that the Plugin needs to be updated and a link that says click on it for automatic updation of the Plugin. Take a look at diagram 1.

Diagram 1.  A plugin ready for updation
Diagram 1. A plugin ready for updation

The message displayed below a specific plugin that must be upgraded is:
There is a new version of { plugin name } available, View Version X.X Details or Upgrade Automatically.

View Version X.X Details  - is a link
Upgrade Automatically  - is a link

Click the Upgrade Automatically link.

You will be asked for your FTP information as shown in diagram2.

Diagram 2. Fill in your FTP information
Diagram 2. Fill in your FTP information

Enter your Hostname (usually the domain URL) then input your FTP login ID and Password, select the FTP radio button , then click the button Proceed.

You will see a number of messages displayed to one by one.  Wait until you see plugin reactivated successfully before you leave this page, otherwise the process may not complete.  Take a look at diagram 3.

Diagram 3.  Plugin being updated - Messages
Diagram 3. Plugin being updated - Messages

If there are any other plugins, in the list of plugins that are displaying the message that there is a New Version available simply repeat this process and upgrade them as well.

NOTE: You will not be asked for your FTP information repeatedly, only once at the start of the updation process.

If you encounter any plugin which for any reason will not get updated automatically then you have to update it the old fashion way as described in steps 1 – 7 in this content.

Keep Getting A Write Error When Attempting To Update?

This is normally a directory permission issue, here is a fix. Login to your website using an FTP client. Browse to you WordPress - Plugins - folder. This is located inside the wp-content folder and set the WordPress - Plugins - folder permissions to 755. This is normally done using the GUI of your FTP client.

Select the Plugins folder, right click, go to Properties from the sticky menu that appears and set the folder’s permission to 755. Then exit and re-try the Automatic updation, it should run perfectly now.

In the worst case, set the Plugins folder permissions to 777, do the automatic upgrade and when completed fully reset the Plugin folder’s permission to 755. Leaving any folder’s permission as 777 is dangerous in any Content Management System.

Ivan Bayross
WordPress Tutorials

working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)