<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>scot hacker's scripts and utils &#187; WordPress</title>
	<atom:link href="http://birdhouse.org/software/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://birdhouse.org/software</link>
	<description>Scot Hacker's Misc Scripts and Utils</description>
	<lastBuildDate>Fri, 06 Aug 2010 16:00:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>WordPress Mass Management Tools</title>
		<link>http://birdhouse.org/software/2010/08/wordpress-mass-management/</link>
		<comments>http://birdhouse.org/software/2010/08/wordpress-mass-management/#comments</comments>
		<pubDate>Wed, 04 Aug 2010 16:32:38 +0000</pubDate>
		<dc:creator>shacker</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://birdhouse.org/software/?p=133</guid>
		<description><![CDATA[WordPress Mass Management Tools is a small collection of tools for managing multiple WordPress installations on a Unix/Linux/Mac server (or perhaps a Windows server with Cygwin (untested)). Yes, users can often self-install via Fantastico or similar programs, but what guarantee do you have that they&#8217;ll upgrade as soon as new releases become available? Letting users [...]]]></description>
			<content:encoded><![CDATA[<p>WordPress Mass Management Tools is a small collection of tools for managing multiple WordPress installations on a Unix/Linux/Mac server (or perhaps a Windows server with Cygwin (untested)). </p>
<p>Yes, users can often self-install via Fantastico or similar programs, but what guarantee do you have that they&#8217;ll upgrade as soon as new releases become available? Letting users run old versions of web software is a great way to get hacked. This kit lets you take control of users&#8217; installations by checking them out via svn and upgrading them <em>en masse</em>.</p>
<p>At <a href="http://hosting.birdhouse.org">Birdhouse Hosting</a> we use WordPress Mass Management Tools to create all new installations. When WP updates are released, we&#8217;re able to upgrade more than 100 WP installations belonging to 80+ users in a few minutes flat. </p>
<p>The kit is designed to be run by root &#8211; these are not tools for WordPress end users. The kit assumes basic knowledge of the bash shell.</p>
<p>This kit <strong>replaces</strong> the old wp-create and wp-mass-upgrade scripts which were distributed separately and are no longer supported. Includes:</p>
<p><strong>wp-create.sh</strong>: Super fast way to install WordPress for clients, via subversion. Performs the following tasks:</p>
<ul>
<li>Gather installation info</li>
<li>Create install dir and check out a copy of WordPress</li>
<li>Create database, db user, set db privs via external .sql file</li>
<li>Create WP config file</li>
<li>Create upload dir and set filesystem permissions</li>
<li>Generate array line for wp-sites.sh</li>
</ul>
<p>Final setup is done via browser.</p>
<p><strong>wp-mass-upgrade.sh</strong>: Iterates through all sites listed in wp-sites.sh, backs up the site&#8217;s database, upgrades to a specified version of WordPress, and sends the site owner email announcing the upgrade.</p>
<p><strong>wp-mass-plugins.sh</strong>: Generates a list of all active plugins  used by all sites on the server. The list can be compared to lists of known-incompatible plugins to help you make decisions about whether to skip any sites on the list.</p>
<p><strong><a href='http://birdhouse.org/software/wp-content/uploads/2010/08/wp-mass-tools.zip'>Download wp-mass-tools 1.1</a></strong></p>
<p>See the included readme.txt for documentation.</p>
]]></content:encoded>
			<wfw:commentRss>http://birdhouse.org/software/2010/08/wordpress-mass-management/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Cleancats</title>
		<link>http://birdhouse.org/software/2008/04/cleancats/</link>
		<comments>http://birdhouse.org/software/2008/04/cleancats/#comments</comments>
		<pubDate>Wed, 23 Apr 2008 08:12:56 +0000</pubDate>
		<dc:creator>shacker</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://birdhouse.org/software/?p=34</guid>
		<description><![CDATA[This is a very crude mass category deletion script for WordPress. I recently inherited a WordPress site with more than 6000 categories. After deleting a ton of old posts, we were left with more than 4000 unused categories, and I needed a way to remove them quickly. Couldn&#8217;t find a plugin up to the task, [...]]]></description>
			<content:encoded><![CDATA[<p>This is a very crude mass category deletion script for WordPress. I recently inherited a WordPress site with more than 6000 categories. After deleting a ton of old posts, we were left with more than 4000 unused categories, and I needed a way to remove them quickly. Couldn&#8217;t find a plugin up to the task, so wrote this. Very crude, but effective. Not a plugin, but a small WP companion script. See instructions in the comment at top of script.</p>
<p><strong><a href='http://birdhouse.org/software/wp-content/uploads/2008/04/cleancatsphp.txt'>Download Cleancats</a></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://birdhouse.org/software/2008/04/cleancats/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WP-Create</title>
		<link>http://birdhouse.org/software/2008/04/wp-create/</link>
		<comments>http://birdhouse.org/software/2008/04/wp-create/#comments</comments>
		<pubDate>Sun, 13 Apr 2008 21:26:19 +0000</pubDate>
		<dc:creator>shacker</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://birdhouse.org/software/?p=28</guid>
		<description><![CDATA[WP-Create has been folded into the WordPress Mass Management Tools kit.]]></description>
			<content:encoded><![CDATA[<p>WP-Create has been folded into the <a href="http://birdhouse.org/software/2010/08/wordpress-mass-management/">WordPress Mass Management Tools</a> kit.</p>
]]></content:encoded>
			<wfw:commentRss>http://birdhouse.org/software/2008/04/wp-create/feed/</wfw:commentRss>
		<slash:comments>25</slash:comments>
		</item>
		<item>
		<title>WP Workflow Docs</title>
		<link>http://birdhouse.org/software/2008/01/wp-workflow-docs/</link>
		<comments>http://birdhouse.org/software/2008/01/wp-workflow-docs/#comments</comments>
		<pubDate>Wed, 23 Jan 2008 05:30:33 +0000</pubDate>
		<dc:creator>shacker</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://birdhouse.org/software/?p=25</guid>
		<description><![CDATA[A dirt-simple WordPress plugin that lets you provide workflow docs to your authors and editors from within the WP admin interface. Instructions: Unpack this folder to your plugins directory and activate it. Click on the Dashboard and you&#8217;ll see a new tab called &#8220;NGNO Docs.&#8221; Within that, you&#8217;ll find documentation I wrote for my authors [...]]]></description>
			<content:encoded><![CDATA[<p>A dirt-simple WordPress plugin that lets you provide workflow docs to your authors and editors from within the WP admin interface.</p>
<p><span id="more-25"></span></p>
<p><strong>Instructions:</strong> Unpack this folder to your plugins directory and activate it. Click on the Dashboard and you&#8217;ll see a new tab called &#8220;NGNO Docs.&#8221; Within that, you&#8217;ll find documentation I wrote for <em>my</em> authors  for  <em>one particular site</em>. In order for this to be useful, you&#8217;ll need to replace  the HTML it contains with your  own by editing the file <code>docs.html</code>.</p>
<p>You&#8217;ll want to remove the image files I&#8217;ve included and, if desired, add your own. Note: I found it tricky to get image paths working &#8211; you&#8217;ll need to embed images like this:</p>
<p><code>img src="../wp-content/plugins/wp-workflow-docs/more-result.gif"</code></p>
<p>You can change the plugin name and tab name by editing the plugin file itself &#8211; it&#8217;s a tiny plugin and it will be pretty obvious where to do this in the file. Then de-activate and re-activate it to see the new tab name.</p>
<p><strong><a href="http://birdhouse.org/software/wp-content/uploads/2008/04/wp-workflow-docs.zip">Download wp-workflow-docs</a></strong></p>
<p>Contributions / improvements welcome!</p>
]]></content:encoded>
			<wfw:commentRss>http://birdhouse.org/software/2008/01/wp-workflow-docs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FuturePost</title>
		<link>http://birdhouse.org/software/2007/12/futurepost/</link>
		<comments>http://birdhouse.org/software/2007/12/futurepost/#comments</comments>
		<pubDate>Tue, 18 Dec 2007 05:27:40 +0000</pubDate>
		<dc:creator>shacker</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://birdhouse.org/software/?p=24</guid>
		<description><![CDATA[A WordPress plugin aimed primarily at events sites, where you want to be able to timestamp posts in the future but have them appear immediately (by default, WordPress will not display a future timestamped post until its go-live date rolls around). This plugin sets the post_status field to &#8220;publish&#8221; rather than &#8220;future&#8221; when publishing a [...]]]></description>
			<content:encoded><![CDATA[<p>A WordPress plugin aimed primarily at events sites, where you want to be able to timestamp posts in the future but have them appear immediately (by default, WordPress will not display a future timestamped post until its go-live date rolls around). This plugin sets the post_status field to &#8220;publish&#8221; rather than &#8220;future&#8221; when publishing a post, even if its timestamp is in the future. Written by Ryan Boren &#8211; I&#8217;m just hosting it.</p>
<h4><span id="more-24"></span></h4>
<p><strong>Instructions:</strong> Place future-post.php in your plugins directory and activate it. Write a post with a future timestamp and hit publish. Notice that it goes live on your site immediately.</p>
<p><strong>Note:</strong> This seemingly simple plugin was graciously written by the magical <a title="boren.nu" href="http://boren.nu/">Ryan Boren</a> when I was facing a deadline. He doesn&#8217;t have time to maintain/host it, so I agreed to.</p>
<p><strong><a href="http://wordpress.org/extend/plugins/the-future-is-now/">Download version 1.0</a></strong></p>
<p>Contributions / improvements welcome!</p>
]]></content:encoded>
			<wfw:commentRss>http://birdhouse.org/software/2007/12/futurepost/feed/</wfw:commentRss>
		<slash:comments>78</slash:comments>
		</item>
		<item>
		<title>WP Mass Upgrade</title>
		<link>http://birdhouse.org/software/2007/07/wp-mass-upgrade/</link>
		<comments>http://birdhouse.org/software/2007/07/wp-mass-upgrade/#comments</comments>
		<pubDate>Thu, 12 Jul 2007 05:23:53 +0000</pubDate>
		<dc:creator>shacker</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://birdhouse.org/software/?p=22</guid>
		<description><![CDATA[Designed for hosts with lots of individual WordPress blogs to manage. If all blogs are managed via subversion, this script can iterate through all of them and upgrade each to the latest version in seconds. WP-Mass-Upgrade has been folded into the WordPress Mass Management Tools kit.]]></description>
			<content:encoded><![CDATA[<p>Designed for hosts with lots of individual WordPress blogs to manage. If all blogs are <a title="Installing/Updating WordPress with Subversion « WordPress Codex" href="http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion">managed via subversion</a>, this script can iterate through all of them and upgrade each to the latest version in seconds.</p>
<p>WP-Mass-Upgrade has been folded into the <a href="http://birdhouse.org/software/2010/08/wordpress-mass-management/">WordPress Mass Management Tools</a> kit.</p>
]]></content:encoded>
			<wfw:commentRss>http://birdhouse.org/software/2007/07/wp-mass-upgrade/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>WP-Digest</title>
		<link>http://birdhouse.org/software/2006/12/wp-digest/</link>
		<comments>http://birdhouse.org/software/2006/12/wp-digest/#comments</comments>
		<pubDate>Sun, 10 Dec 2006 16:04:27 +0000</pubDate>
		<dc:creator>shacker</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://birdhouse.org/software/?p=8</guid>
		<description><![CDATA[Sends periodic email notifications of new WordPress blog entries (in either plain text or HTML mode) to a separate subscribers mailing list. Maintains cache file recording ID of last-sent post. On subsequent runs, sends all posts created since the previous run. Currently driving weekly email updates from birdhouse.org and other sites. About Sends periodic email [...]]]></description>
			<content:encoded><![CDATA[<p>Sends periodic email notifications of new WordPress blog entries (in either plain text or HTML mode) to a separate subscribers mailing list. Maintains cache file recording ID of last-sent post. On subsequent runs, sends all posts created since the previous run.</p>
<p>Currently driving weekly <a href="http://birdhouse.org/blog">email updates</a> from birdhouse.org and other sites.</p>
<h3><span id="more-8"></span>About</h3>
<p>Sends periodic email notifications of new WordPress blog entries, either in plain text or as formatted HTML, to a separate subscribers mailing list. Records ID of last-sent post. On subsequent runs, sends all posts created since the previous run. Mail is sent to a single email address, which is most likely a separate subscribers mailing list.</p>
<p>The first time WP-Digest is run, it operates on the last n entries made in your blog. After the first run, it will save the ID of your last blog entry in a cache file. On subsequent runs, it will operate on however many entries have been made since the previous run. You can manually control the value of n by changing $MinPosts in conf.php.</p>
<h3>Requirements</h3>
<p>This script is desgined to be run on Unix/Linux/OS X servers. It may work on Windows servers as well, but has not been tested in that environment. Of course you&#8217;ll need to use some alternative to cron if working under Windows.</p>
<p>This script requires access to the lynx web browser installed on your server. To determine whether you have it, type:</p>
<p><code>which lynx</code></p>
<p>If the system returns &#8220;Command not found&#8221; then you don&#8217;t have it, and should ask your sysadmin to install it. This script is designed to be run at regular intervals via crontab.</p>
<p>See included readme.txt for setup instructions.</p>
<h3>History</h3>
<p>2.0: Now sends your choice of plain text or HTML-formatted (multipart) email.</p>
<p>1.2: Completely new architecture, now based on lynx for improved formatting options and an end to problems with incorrectly formatted characters and error messages in output generated by 3rd party plugins when run via cron.</p>
<p>1.1: Bug fixes</p>
<p>1.0: Started as a port of mtblogmail, but quickly turned into a complete rewrite in order to take advantage of the WordPress APIs.</p>
<h3>Download</h3>
<p><strong><a href="http://birdhouse.org/software/wp-content/uploads/2008/04/wp-digest.tgz">Download wp-digest</a></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://birdhouse.org/software/2006/12/wp-digest/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WPBlogMail</title>
		<link>http://birdhouse.org/software/2004/01/wpblogmail/</link>
		<comments>http://birdhouse.org/software/2004/01/wpblogmail/#comments</comments>
		<pubDate>Sun, 11 Jan 2004 08:12:00 +0000</pubDate>
		<dc:creator>shacker</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://birdhouse.org/software/?p=10</guid>
		<description><![CDATA[WPBlogMail is now deprecated. Please use WP-Digest instead.]]></description>
			<content:encoded><![CDATA[<p>WPBlogMail is now deprecated. Please use <a href="http://birdhouse.org/software/2006/12/wp-digest/">WP-Digest</a> instead.</p>
]]></content:encoded>
			<wfw:commentRss>http://birdhouse.org/software/2004/01/wpblogmail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
