Wordpress

Why WordPress should be served Cached

The biggest strength of Wordpress is its dynamic nature. A browser view of a Wordpress website is like a “skin” which interfaces with dynamic components under the hood. But once a Wordpress website starts growing, this also becomes the biggest weakness of Wordpress. The “skin” becomes overloaded with more and more dynamic components. and a simple pageview becomes acrimonious for the server, as it struggles to deliver a “freshly prepared skin” to the browser for each and every page view. On the user end, the lag becomes noticeable. When it comes to self-hosting Wordpress, Caching is an inevitability.

Wordpress

Subversion for a Casual WordPress User…Promises and Challenges

Subversion offers many promises for casual Wordpress users, such as the ability to update Wordpress using a single shell command. But many underlying challenges also remain. This post examines what makes the lure of Subversion so strong for Wordpress users while thoroughly discussing the challenges the author faced in an experimental deployment of Subversion. Subversion clients are also discussed. The article concludes with a “wish-list” for the ideal theoretical Subversion client.

How to · Reviews · Trends · Wordpress

Why Subversion is not a complete way to update WordPress

While Wordpress offers the functionality of upgrading core files, themes and plugins via the Dashboard, this feature cannot be used with some webhosts who are keen on security. Upgrading via FTP is time-consuming and error prone. FTP is also not very secure. To quote one webhost, “Its 2012, and you shouldn’t be using FTP for anything.” Subversion offers the promise of one-click one-command, lightning-fast, server side upgrades. Is Subversion the way to go or has Subversion yet to grow up for the casual Wordpress user?