<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000'>Our more manual process for blogs.brynmawr.edu goes something like: <div>1) identify plugin to remove</div><div>2) check in WP database which blogs have the plugin activated</div><div>3) determine if plugin was actually used on those blogs (we have had some users who will just activate all available plugins to see what they do), and if so, how it affects the blogs/if it can be extricated</div><div>4) If it seems reasonable to remove, remove plugin on test server</div><div>5) See if the blog(s) are broken</div><div>6) if not, remove in production</div><div><br></div><div>For plugin or theme removals that affect large numbers of blogs, we do the same thing we do for upgrades to spot check for problems-- review blogs on a list of high priority (college news, blogs used for classes, etc) blogs, and those that are typical examples of use of all remaining themes and plugins. If none of those are broken, we're probably okay. This method has gotten us through a lot of cleanup and a couple of upgrades successfully. </div><div><br></div><div>I thought I'd share this in case others aren't set up for automated testing. </div><div><br></div><div>FYI: Catherine Farman and I talked more about cleaning up and maintaining a large multisite install, and consolidating/revising homegrown themes and plugins, at edUi and WordCamp last year-- the slides are here if anyone is interested: <a href="http://2012.philly.wordcamp.org/2012/10/27/slides-presentations/">http://2012.philly.wordcamp.org/2012/10/27/slides-presentations/</a> (and I believe the WordCamp talk is on wordpress.tv ). </div><div><br></div><div>Best, </div><div>Juliana Perry</div><div><br><div><span name="x"></span>---<br>Juliana Perry<br>Web Services Project Manager<br>Bryn Mawr College<br>610-526-7554<span name="x"></span><br></div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 11 Apr 2013 15:26:29 +0000<br>From: "Skriloff, Nicholas" <SkriloffN@darden.virginia.edu><br>Subject: [wp-edu] Removing Plugins<br>To: "wp-edu@lists.automattic.com" <wp-edu@lists.automattic.com><br>Message-ID:<br> <CA12CBE4F4AC324FBE1668F44FF17FD61FC3A1@EXCH1.darden.virginia.edu><br>Content-Type: text/plain; charset="us-ascii"<br><br>Here at Darden Business School we have our faculty blogs: http://blogs.darden.virginia.edu/ . Overtime some plugins that were once used are no longer used. We have a staging environment that is copy of our production environment. In our staging environment we want to run a process like<br><br>1) Identify plugin to remove<br><br>2) Run a test (like a selenium test) against all blogs<br><br>3) Remove said pluging<br><br>4) Run test again<br><br>5) If nothing broke, the add it to the list of plugins that can be removed from production.<br><br>How have any of you all done this?<br><br>Sincerely,<br>Nick Skriloff , ME , MCP, SCJP<br>Information Technology Specialist<br>Darden Information Services<br>Voice 434 243 5025 Fax 434 243 2279<br>skriloffn@darden.virginia.edu<br></div></div></div></body></html>