Up next
Author
Tags

I just found a quick tip on the Installatron forums.

By default Installatron disables all WordPress plugins when doing an upgrade. This is due to the WordPress best practices for upgrading the version of their system. When you have a lot of WordPress installs to go through this is a big pain because it usually breaks the site.

According to this post, you disable the disabling of the plugins by creating a file named .dont_disable_plugins in the directory that wordpress is installed to.

Via command line it is as simple as this:

touch /path/to/wordpress/.dont_disable_plugins

Execute that command on the command line (or upload an empty file via FTP/SCP) and the plugins will remain enabled. There is also an option in the installatron settings to enable this file creation upon install.

Note that if you have a plugin that is not compatible with a new version of WordPress, it may break your install!

3 comments
  1. Pingback: Dave Drager
  2. Pingback: Julianna Yau

Comments are closed.

You May Also Like

Firesheep Should Be A Call To Arms For System, Network & Web Admins

Firesheep by Eric Butler has just been released to the world. This Firefox plugin does a few things that have already been fairly easy to do for a while, but rolled up in one easy to use package: Sniffs data on unencrypted Wireless Networks Looks for unencrypted login cookies sent to known popular insecure sites Allows you to login to that account with ‘One Click’ So what sites are impacted by default? Amazon.com, Basecamp, bit.ly, Cisco, CNET, Dropbox, Enom, Evernote, Facebook, Flickr, Github, Google, HackerNews, Harvest, Windows Live, NY Times, Pivotal Tracker, Slicehost, tumblr, Twitter, WordPress, Yahoo, and Yelp are among the few. A plugin system allows anyone to add their own sites (and cookie styles) to the plugin. Yikes! It goes without saying that this is a major security problem for anyone who uses unencrypted wireless networks. Includes on this list are many universities and companies such as Starbucks.

Dead linux users?

Not dead as in dead, but dead as in the user has logged out of the system and for some reason their shell is still open. This might happen if your system crashes before you can log out, there are network problems and you are disconnected, or a number of other reasons. This article explains how to log these “dead” shell users out.

Adding a Module Position in a Joomla 1.5 Template

Adding a module position in a Joomla 1.5 template is not as…

Accessing Microsoft ODBC data sources in Linux

Developing web apps cross platform can be a pain sometimes, as the…