<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.workhabit.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>drupal</title>
 <link>http://www.workhabit.com/category/activity-stream-tags/drupal</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>Adding content to a region inside a node</title>
 <link>http://www.workhabit.com/labs/adding-content-region-inside-node</link>
 <description>&lt;p&gt;We&#039;ve all seen it, those darn blocks that have to appear in-line in a node body, but we&#039;re often left scratching our heads as to how to get it in there.&lt;/p&gt;
&lt;p&gt;The problem is that regions are only surfaced to the page template, and the region we need to add is a div inside of a node.&lt;/p&gt;
&lt;p&gt;Well, with a couple of simple theme overrides, you can get there, and make it performant as well. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.workhabit.com/labs/adding-content-region-inside-node&quot;&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.workhabit.com/labs/adding-content-region-inside-node#comments</comments>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/drupal">drupal</category>
 <category domain="http://www.workhabit.com/category/tags/drupal-planet-0">drupal-planet</category>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/performance">performance</category>
 <category domain="http://www.workhabit.com/category/tags/theming">theming</category>
 <pubDate>Fri, 08 Apr 2011 20:47:03 +0000</pubDate>
 <dc:creator>aaron</dc:creator>
 <guid isPermaLink="false">5710 at http://www.workhabit.com</guid>
</item>
<item>
 <title>Cleaning up after Backup and Migrate.</title>
 <link>http://www.workhabit.com/labs/cleaning-after-backup-and-migrate</link>
 <description>&lt;p&gt;&amp;#8230;Ran into an issue where Backup and Migrate wasn&amp;#8217;t cleaning up after itself - mysql dumps were sitting in /tmp, stacking up, and causing disks to fill up.&lt;/p&gt;

&lt;p&gt;Even if it were cleaning up after itself, I&amp;#8217;m dealing with a clustered site.  It&amp;#8217;s my understanding that cleanup should occur on cron - but running cron on every webserver is kind of, well, meh.&lt;/p&gt;

&lt;p&gt;Since I&amp;#8217;m a believer that all problems can be resolved with perl, the following script can be invoked via system cron, and will clean up any backup&amp;#95;migrate&amp;#95;*.mysql files that are older than one day.&lt;/p&gt;
</description>
 <comments>http://www.workhabit.com/labs/cleaning-after-backup-and-migrate#comments</comments>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/drupal">drupal</category>
 <category domain="http://www.workhabit.com/category/tags/hax">hax</category>
 <enclosure url="http://www.workhabit.com/sites/default/files/bm_clean.pl_.txt" length="1309" type="text/plain" />
 <pubDate>Mon, 04 Apr 2011 23:49:10 +0000</pubDate>
 <dc:creator>gary</dc:creator>
 <guid isPermaLink="false">5709 at http://www.workhabit.com</guid>
</item>
<item>
 <title>Why your site from 1996 should not be ported to Drupal without a redesign</title>
 <link>http://www.workhabit.com/labs/why-your-site-1996-should-not-be-ported-drupal-without-redesign</link>
 <description>&lt;p&gt;In the past year, we&#039;ve worked with a number of fantastic clients.  One of the things we&#039;ve seen repeatedly is a desire by some clients to do work that is a &quot;port&quot; of the existing site to Drupal technologies.  This is often not the right approach. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.workhabit.com/labs/why-your-site-1996-should-not-be-ported-drupal-without-redesign&quot;&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.workhabit.com/labs/why-your-site-1996-should-not-be-ported-drupal-without-redesign#comments</comments>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/drupal">drupal</category>
 <category domain="http://www.workhabit.com/category/tags/drupal-planet">drupal planet</category>
 <category domain="http://www.workhabit.com/category/tags/redesign">redesign</category>
 <pubDate>Tue, 16 Nov 2010 11:37:57 +0000</pubDate>
 <dc:creator>jonathan</dc:creator>
 <guid isPermaLink="false">5611 at http://www.workhabit.com</guid>
</item>
<item>
 <title>Drush in RPM Form</title>
 <link>http://www.workhabit.com/labs/drush-rpm-form</link>
 <description>&lt;p&gt;Drupal without drush is like a burger without cheese.  So when, in the course of human events, it becomes necessary to ensure that a specific version of drush is installed on a number of systems in a standard location, falling back to your distribution&amp;#8217;s package management system is probably a good idea.&lt;/p&gt;

&lt;p&gt;Thus, I&amp;#8217;ve hacked together a quick script that&amp;#8217;ll grab a version of drush and turn it into a noarch binary RPM, suitable for use on RHEL/CentOS (and probably Fedora, for that matter). &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.workhabit.com/labs/drush-rpm-form&quot;&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.workhabit.com/labs/drush-rpm-form#comments</comments>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/centos">centos</category>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/drupal">drupal</category>
 <category domain="http://www.workhabit.com/category/tags/drupal-planet">drupal planet</category>
 <category domain="http://www.workhabit.com/category/tags/drupal-planet-0">drupal-planet</category>
 <category domain="http://www.workhabit.com/category/tags/drush">drush</category>
 <category domain="http://www.workhabit.com/category/tags/rhel">rhel</category>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/rpm">rpm</category>
 <enclosure url="http://www.workhabit.com/sites/default/files/rpm_build-drush.zip" length="2000" type="application/zip" />
 <pubDate>Wed, 13 Oct 2010 23:35:14 +0000</pubDate>
 <dc:creator>gary</dc:creator>
 <guid isPermaLink="false">5610 at http://www.workhabit.com</guid>
</item>
<item>
 <title>On containing risk vs getting things done</title>
 <link>http://www.workhabit.com/labs/containing-risk-vs-getting-things-done</link>
 <description>&lt;p&gt;Drupal as a framework doesn&amp;#8217;t lend itself well to detailed specifications — and many projects try very hard to do them to &amp;#8220;contain risk&amp;#8221; and get &amp;#8220;a clear and exact&amp;#8221; deliverable. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.workhabit.com/labs/containing-risk-vs-getting-things-done&quot;&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.workhabit.com/labs/containing-risk-vs-getting-things-done#comments</comments>
 <category domain="http://www.workhabit.com/category/tags/collaboration">collaboration</category>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/drupal">drupal</category>
 <category domain="http://www.workhabit.com/category/tags/process">process</category>
 <category domain="http://www.workhabit.com/category/tags/projects">projects</category>
 <category domain="http://www.workhabit.com/category/tags/specifications">specifications</category>
 <pubDate>Tue, 25 May 2010 19:32:32 +0000</pubDate>
 <dc:creator>jonathan</dc:creator>
 <guid isPermaLink="false">5384 at http://www.workhabit.com</guid>
</item>
<item>
 <title>CDN2 Updates and Fixes</title>
 <link>http://www.workhabit.com/labs/cdn2-updates-and-fixes</link>
 <description>&lt;p&gt;We&amp;#8217;ve been getting reports of intermittent issues with transcoding on our CDN2 service.&lt;/p&gt;

&lt;p&gt;After digging around for a while, we&amp;#8217;ve found an issue where messages are not getting delivered through Amazon SQS to our transcode nodes.&lt;/p&gt;

&lt;p&gt;The good news is that as of tomorrow morning, we&amp;#8217;ll be deploying CDN2 to a new scaleable infrastructure that removes the Amazon dependencies.  This move will improve performance and stabillity of video uploads and transcoding. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.workhabit.com/labs/cdn2-updates-and-fixes&quot;&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.workhabit.com/labs/cdn2-updates-and-fixes#comments</comments>
 <category domain="http://www.workhabit.com/category/tags/cdn2">cdn2</category>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/drupal">drupal</category>
 <category domain="http://www.workhabit.com/category/tags/drupal-planet">drupal planet</category>
 <category domain="http://www.workhabit.com/category/tags/updates">updates</category>
 <pubDate>Thu, 08 Oct 2009 05:01:29 +0000</pubDate>
 <dc:creator>aaron</dc:creator>
 <guid isPermaLink="false">4914 at http://www.workhabit.com</guid>
</item>
<item>
 <title>New Script: Are you dealing with a hacked drupal core?</title>
 <link>http://www.workhabit.com/labs/new-script-are-you-dealing-hacked-drupal-core</link>
 <description>&lt;p&gt;Whenever a group of us WorkHabit folks are sitting around the virtual watercooler reviewing upcoming projects, one of the first questions we need to answer is about the quality of the code we&#039;re starting with.&lt;/p&gt;
&lt;p&gt;The big question we always want to know is this: Is core hacked?  And how badly?&lt;/p&gt;
&lt;p&gt;After doing this manually several times, I decided to cut to the chase and write a script for it.&lt;/p&gt;
&lt;p&gt;The bash script to do this is at the bottom of this post.  Just save it as iscorehacked.sh, mark it executable, and have at it. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.workhabit.com/labs/new-script-are-you-dealing-hacked-drupal-core&quot;&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.workhabit.com/labs/new-script-are-you-dealing-hacked-drupal-core#comments</comments>
 <category domain="http://www.workhabit.com/category/tags/bash">bash</category>
 <category domain="http://www.workhabit.com/category/tags/core">core</category>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/drupal">drupal</category>
 <category domain="http://www.workhabit.com/category/tags/drupal-planet">drupal planet</category>
 <category domain="http://www.workhabit.com/category/tags/hacked">hacked</category>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/php">php</category>
 <category domain="http://www.workhabit.com/category/tags/shell-script">shell script</category>
 <enclosure url="http://www.workhabit.com/sites/default/files/iscorehacked.sh" length="1578" type="application/x-sh" />
 <pubDate>Tue, 21 Jul 2009 19:15:35 +0000</pubDate>
 <dc:creator>aaron</dc:creator>
 <guid isPermaLink="false">4543 at http://www.workhabit.com</guid>
</item>
<item>
 <title>AutoTagging Content with Drupal</title>
 <link>http://www.workhabit.com/labs/autotagging-content-drupal</link>
 <description>&lt;p&gt;Today marks the first beta version of our &lt;a href=&quot;http://drupal.org/project/autotagging&quot;&gt;Drupal AutoTagging&lt;/a&gt; module.&lt;/p&gt;
&lt;p&gt;This has been a long time in the works, and included several conversations between myself and Frank Febbraro, the creator of the original autotagging project and maintainer on the OpenCalais module, which this initiative is designed to facilitate.&lt;/p&gt;
&lt;p&gt;The goal of this project:&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Provide a pluggable framework for fetching taxonomy (tag) information from third party services.&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;The initial release of the project supports three different tagging services: &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.workhabit.com/labs/autotagging-content-drupal&quot;&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
</description>
 <comments>http://www.workhabit.com/labs/autotagging-content-drupal#comments</comments>
 <category domain="http://www.workhabit.com/category/tags/autotagging">autotagging</category>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/drupal">drupal</category>
 <category domain="http://www.workhabit.com/category/tags/drupal-planet">drupal planet</category>
 <category domain="http://www.workhabit.com/category/tags/opencalais">opencalais</category>
 <category domain="http://www.workhabit.com/category/tags/tagthenet">tagthe.net</category>
 <category domain="http://www.workhabit.com/category/tags/taxonomy">taxonomy</category>
 <category domain="http://www.workhabit.com/category/tags/yahoo-terms">yahoo terms</category>
 <pubDate>Mon, 06 Jul 2009 19:56:39 +0000</pubDate>
 <dc:creator>aaron</dc:creator>
 <guid isPermaLink="false">4448 at http://www.workhabit.com</guid>
</item>
<item>
 <title>User registration pages - a case study</title>
 <link>http://www.workhabit.com/labs/user-registration-pages-case-study</link>
 <description>&lt;p&gt;Sometimes an afterthought, sometimes the only good-looking page on a site: registration pages are the heart and soul of user participation. Maximizing the completion rate and minimizing abandonment of your signup form is a crucial part of getting users talking, especially if you don&#039;t allow anonymously posted content on your site (an increasingly common thing as spam continues to flourish).&lt;/p&gt;
&lt;p&gt;Web 2.0 ushered in a lot of changes to registration pages, the most notable concept being simplicity. This is the executive summary: &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.workhabit.com/labs/user-registration-pages-case-study&quot;&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.workhabit.com/labs/user-registration-pages-case-study#comments</comments>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/drupal">drupal</category>
 <category domain="http://www.workhabit.com/category/tags/one-page">one-page</category>
 <category domain="http://www.workhabit.com/category/tags/registration">registration</category>
 <category domain="http://www.workhabit.com/category/tags/simplicity">simplicity</category>
 <category domain="http://www.workhabit.com/category/tags/usability">usability</category>
 <pubDate>Sat, 16 May 2009 00:17:29 +0000</pubDate>
 <dc:creator>domenic</dc:creator>
 <guid isPermaLink="false">4143 at http://www.workhabit.com</guid>
</item>
<item>
 <title>Rupal, the new Community-Powered CMS</title>
 <link>http://www.workhabit.com/labs/rupal-new-community-powered-cms</link>
 <description>&lt;p&gt;For those eagerly awaiting the next member of the Drupal family, WorkHabit is proud to announce Rupal, the CMS designed exclusively for our valued cross-dressing community members.&lt;br /&gt;
&lt;center&gt;&lt;br /&gt;
&lt;img src=&quot;http://img.skitch.com/20090401-myb44nx5j4cm6amxew4q99bxhp.jpg&quot; /&gt;&lt;br /&gt;
&lt;/center&gt;&lt;br /&gt;
Core modules include automatic pronoun feminization, rounded corners on everything, and auto-filtering of &quot;it&#039;s a trap!&quot; comments. Over 9,000 hours have been put into lovingly crafting the first community release. &lt;span class=&#039;read-more&#039;&gt;&lt;a href=&quot;http://www.workhabit.com/labs/rupal-new-community-powered-cms&quot;&gt;&amp;nbsp;read&amp;nbsp;more&amp;nbsp;&amp;raquo;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
 <comments>http://www.workhabit.com/labs/rupal-new-community-powered-cms#comments</comments>
 <category domain="http://www.workhabit.com/category/tags/aprilfools">aprilfools</category>
 <category domain="http://www.workhabit.com/category/tags/cms">cms</category>
 <category domain="http://www.workhabit.com/category/activity-stream-tags/drupal">drupal</category>
 <category domain="http://www.workhabit.com/category/tags/rupal">rupal</category>
 <pubDate>Wed, 01 Apr 2009 19:06:29 +0000</pubDate>
 <dc:creator>domenic</dc:creator>
 <guid isPermaLink="false">3774 at http://www.workhabit.com</guid>
</item>
</channel>
</rss>

