<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/rss2enclosuresfull.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0" xml:base="http://drupaleasy.com">
<channel>
 <title>Drupal Easy - </title>
 <link>http://drupaleasy.com</link>
 <description>To teach and spread Drupal to all creatures great and small.</description>
 <language>en</language>
<media:keywords>drupal,development,php,cms,framework,content,nodes,howto,tutorial,screencast,video,audio,cck,views,panels,blocks,taxonomy,tips</media:keywords><media:category scheme="http://www.itunes.com/dtds/podcast-1.0.dtd">Technology/Software How-To</media:category><itunes:owner><itunes:email>info@liberatr.net</itunes:email><itunes:name>Ryan Price</itunes:name></itunes:owner><itunes:author>Ryan Price</itunes:author><itunes:explicit>no</itunes:explicit><itunes:keywords>drupal,development,php,cms,framework,content,nodes,howto,tutorial,screencast,video,audio,cck,views,panels,blocks,taxonomy,tips</itunes:keywords><itunes:subtitle>To teach and spread Drupal to all creatures great and small.</itunes:subtitle><itunes:summary>If you need a publishing system for an online newspaper, a podcast, a community, a social network, or just a webpage for your business, we think there's no better system to get you up and running than Drupal.</itunes:summary><itunes:category text="Technology"><itunes:category text="Software How-To" /></itunes:category><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/DrupalEasy" type="application/rss+xml" /><item>
 <title>Moving the comment form without hacking core</title>
 <link>http://feeds.feedburner.com/~r/DrupalEasy/~3/406990693/moving-comment-form-without-hacking-core</link>
 <description>&lt;p&gt;One of the most frustrating things about Drupal's current architecture is that comments, and the form to post them, are attached to nodes and don't easily allow you to move them around in your TPL files. There really should be an easier way to just place them anywhere you'd like. Most times this doesn't get in your way, until you want to do some fancy layouts where your content is split into multiple columns on the page.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupaleasy.com/blogs/ericmarden/2008/09/moving-comment-form-without-hacking-core"&gt;read more&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DrupalEasy/~4/406990693" height="1" width="1"/&gt;</description>
 <comments>http://drupaleasy.com/blogs/ericmarden/2008/09/moving-comment-form-without-hacking-core#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://drupaleasy.com/crss/node/14</wfw:commentRss>
 <pubDate>Tue, 30 Sep 2008 05:54:59 +0000</pubDate>
 <dc:creator>info@liberatr.net (Ryan Price)</dc:creator>
 <guid isPermaLink="false">14 at http://drupaleasy.com</guid>
<feedburner:origLink>http://drupaleasy.com/blogs/ericmarden/2008/09/moving-comment-form-without-hacking-core</feedburner:origLink></item>
<item>
 <title>Relate all nodes from one taxonomy to another with MySQL</title>
 <link>http://feeds.feedburner.com/~r/DrupalEasy/~3/406451757/relate-all-nodes-one-taxonomy-another-mysql</link>
 <description>&lt;p&gt;When using taxonomy to group nodes on your Drupal site, you find a need to apply another taxonomy term to all of those nodes (possibly from a different vocabulary) there is nothing that is going to be shorter and sweeter than some quick SQL-fu.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupaleasy.com/blogs/ericmarden/2008/09/relate-all-nodes-one-taxonomy-another-mysql"&gt;read more&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DrupalEasy/~4/406451757" height="1" width="1"/&gt;</description>
 <comments>http://drupaleasy.com/blogs/ericmarden/2008/09/relate-all-nodes-one-taxonomy-another-mysql#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://drupaleasy.com/crss/node/13</wfw:commentRss>
 <pubDate>Mon, 29 Sep 2008 17:18:45 +0000</pubDate>
 <dc:creator>info@liberatr.net (Ryan Price)</dc:creator>
 <guid isPermaLink="false">13 at http://drupaleasy.com</guid>
<feedburner:origLink>http://drupaleasy.com/blogs/ericmarden/2008/09/relate-all-nodes-one-taxonomy-another-mysql</feedburner:origLink></item>
<item>
 <title>Rebuild your node_comment_statistics table</title>
 <link>http://feeds.feedburner.com/~r/DrupalEasy/~3/405954953/rebuild-your-node-comment-statistics-table</link>
 <description>&lt;p&gt;If you're like me, most of your projects are redesigns of existing sites. And if the site is already on some kind of CMS, this means importing content from the old system into Drupal, and to make it easy you'll do it with MySQL directly.&lt;/p&gt;
&lt;p&gt;There are pros and cons about this approach, which I am learning, and one of the cons is that content created by the database may not always get plugged into all of Drupal's various tables. Sure, you got the text into node, node_revisions, can your CCK tables, but there is more than meets the eye.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupaleasy.com/blogs/ericmarden/2008/09/rebuild-your-node-comment-statistics-table"&gt;read more&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DrupalEasy/~4/405954953" height="1" width="1"/&gt;</description>
 <comments>http://drupaleasy.com/blogs/ericmarden/2008/09/rebuild-your-node-comment-statistics-table#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://drupaleasy.com/crss/node/12</wfw:commentRss>
 <pubDate>Mon, 29 Sep 2008 04:32:58 +0000</pubDate>
 <dc:creator>info@liberatr.net (Ryan Price)</dc:creator>
 <guid isPermaLink="false">12 at http://drupaleasy.com</guid>
<feedburner:origLink>http://drupaleasy.com/blogs/ericmarden/2008/09/rebuild-your-node-comment-statistics-table</feedburner:origLink></item>
<item>
 <title>Import Hundreds of Taxonomy Terms using AWK</title>
 <link>http://feeds.feedburner.com/~r/DrupalEasy/~3/394462024/import-hundreds-taxonomy-terms-using-awk</link>
 <description>&lt;p&gt;Today's challenge: your editors just handed you almost 200 taxonomy terms to add to the site, and you don't have the time or inclination to hit the taxonomy/n/add/term page for the next 2 hours or so... AWK to the rescue!&lt;/p&gt;
&lt;p&gt;Doing a simple CSV export of the term_data and term_hierarchy tables, you've got a pretty simple structure:&lt;/p&gt;
&lt;pre&gt;term_data&lt;br /&gt;tid,vid,name,description,weight&lt;br /&gt;&lt;br /&gt;term_hierarchy&lt;br /&gt;tid,parent&lt;br /&gt;&lt;/pre&gt;&lt;p&gt;What you'll ultimately generate here is a file that stores everything you need to know about importing these terms via a CSV - the term names, the weights, good IDs, and the TID of the parents.&lt;/p&gt;
&lt;pre&gt;2048,#the current value of the sequences for term_data&lt;br /&gt;term,34,Blogs,#a helper line&lt;br /&gt;x,1,Drupal,All about Drupal,-5&lt;br /&gt;x,1,Modules,Ways to extend Drupal,-4&lt;br /&gt;x,1,Themes,Making your install pretty,-3&lt;br /&gt;term,35,News,#a second helper line&lt;br /&gt;x,1,International,,0&lt;br /&gt;x,1,Local,,0&lt;br /&gt;x,1,Hyperlocal,,0&lt;br /&gt;&lt;/pre&gt;&lt;p&gt;In this file, we've got 3 types of data:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The starting value for sequences&lt;/li&gt;
&lt;li&gt;The id of the parent term for the next several rows, starting with the word "term" followed by the TID and the plain English name just to help us get organized&lt;/li&gt;
&lt;li&gt;The new terms, with an "x" where the new TIDs will be placed, and the VID, Description and Weight all filled out.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;a href="http://drupaleasy.com/blogs/ryanprice/2008/09/import-hundreds-taxonomy-terms-using-awk"&gt;read more&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DrupalEasy/~4/394462024" height="1" width="1"/&gt;</description>
 <comments>http://drupaleasy.com/blogs/ryanprice/2008/09/import-hundreds-taxonomy-terms-using-awk#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://drupaleasy.com/crss/node/11</wfw:commentRss>
 <pubDate>Tue, 16 Sep 2008 19:00:22 +0000</pubDate>
 <dc:creator>info@liberatr.net (Ryan Price)</dc:creator>
 <guid isPermaLink="false">11 at http://drupaleasy.com</guid>
<feedburner:origLink>http://drupaleasy.com/blogs/ryanprice/2008/09/import-hundreds-taxonomy-terms-using-awk</feedburner:origLink></item>
<item>
 <title>US States list for CCK select boxes</title>
 <link>http://feeds.feedburner.com/~r/DrupalEasy/~3/372200670/us-states-list-cck-select-boxes</link>
 <description>&lt;p&gt;When defining Content Types in Drupal with the Content Construction Kit you are able to add select boxes to them with CCK. It takes its&lt;br /&gt;
key/value pairs in this format: &lt;strong&gt;Key|Value&lt;/strong&gt;. One of the most common tasks for this is to create a drop down list of US States. So to save folks some time, I have compiled a list for you to paste right into your own projects. The &lt;a title="Drupal - CCK Field - US States" href="http://drupaleasy.com/files/states.txt"&gt;attached text file&lt;/a&gt; will give you US States in the expected format.&lt;/p&gt;
&lt;p&gt;Hopefully this will save others a bit of typing when you need such a list for your own Drupal projects. Enjoy!&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupaleasy.com/blogs/ericmarden/2008/08/us-states-list-cck-select-boxes"&gt;read more&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DrupalEasy/~4/372200670" height="1" width="1"/&gt;</description>
 <comments>http://drupaleasy.com/blogs/ericmarden/2008/08/us-states-list-cck-select-boxes#comments</comments>
 
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://drupaleasy.com/crss/node/9</wfw:commentRss>
 <pubDate>Fri, 22 Aug 2008 21:07:11 +0000</pubDate>
 <dc:creator>info@liberatr.net (Ryan Price)</dc:creator>
 <guid isPermaLink="false">9 at http://drupaleasy.com</guid>
<media:content url="http://feeds.feedburner.com/~r/DrupalEasy/~5/372200671/states.txt" fileSize="646" type="text/plain" /><itunes:explicit>no</itunes:explicit><itunes:subtitle> When defining Content Types in Drupal with the Content Construction Kit you are able to add select boxes to them with CCK. It takes its key/value pairs in this format: Key|Value. One of the most common tasks for this is to create a drop down list of US S</itunes:subtitle><itunes:author>Ryan Price</itunes:author><itunes:summary> When defining Content Types in Drupal with the Content Construction Kit you are able to add select boxes to them with CCK. It takes its key/value pairs in this format: Key|Value. One of the most common tasks for this is to create a drop down list of US States. So to save folks some time, I have compiled a list for you to paste right into your own projects. The attached text file will give you US States in the expected format. Hopefully this will save others a bit of typing when you need such a list for your own Drupal projects. Enjoy! read more</itunes:summary><itunes:keywords>drupal,development,php,cms,framework,content,nodes,howto,tutorial,screencast,video,audio,cck,views,panels,blocks,taxonomy,tips</itunes:keywords><feedburner:origLink>http://drupaleasy.com/blogs/ericmarden/2008/08/us-states-list-cck-select-boxes</feedburner:origLink><enclosure url="http://feeds.feedburner.com/~r/DrupalEasy/~5/372200671/states.txt" length="646" type="text/plain" /><feedburner:origEnclosureLink>http://drupaleasy.com/files/states.txt</feedburner:origEnclosureLink></item>
<item>
 <title>Drupal Theming: $path vs. base_path and path_to_theme</title>
 <link>http://feeds.feedburner.com/~r/DrupalEasy/~3/370264316/drupal-theming-path-vs-basepath-pathtotheme</link>
 <description>&lt;p&gt;When developing Drupal themes, there is one bit of code you type over and over again:&lt;/p&gt;
&lt;pre&gt;sites/all/themes/blueprint/images/whatever.jpg&lt;/pre&gt;&lt;p&gt;Where images/whatever.jpg could be a css file, or other file, but is normally an image.&lt;/p&gt;
&lt;p&gt;However, since clean URLs in Drupal appear to make fake directories, the web browser thinks your image is located in:&lt;/p&gt;
&lt;pre&gt;node/345/sites/all/themes/blueprint/images/whatever.jpg&lt;/pre&gt;&lt;p&gt;When it’s not. Luckily Drupal has tools to help you in this case.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupaleasy.com/blogs/ryanprice/2008/08/drupal-theming-path-vs-basepath-pathtotheme"&gt;read more&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DrupalEasy/~4/370264316" height="1" width="1"/&gt;</description>
 <comments>http://drupaleasy.com/blogs/ryanprice/2008/08/drupal-theming-path-vs-basepath-pathtotheme#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://drupaleasy.com/crss/node/8</wfw:commentRss>
 <pubDate>Wed, 20 Aug 2008 17:52:26 +0000</pubDate>
 <dc:creator>info@liberatr.net (Ryan Price)</dc:creator>
 <guid isPermaLink="false">8 at http://drupaleasy.com</guid>
<feedburner:origLink>http://drupaleasy.com/blogs/ryanprice/2008/08/drupal-theming-path-vs-basepath-pathtotheme</feedburner:origLink></item>
<item>
 <title>Blogs About Drupal</title>
 <link>http://feeds.feedburner.com/~r/DrupalEasy/~3/315135037/blogs-about-drupal</link>
 <description>&lt;p&gt;This is rather self-serving, but I actually got quite a bit of traffic on this site in the last few days, and that made me wonder if some older posts I've written on my personal blog were worth anything. There was really just one useful one:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupaleasy.com/blogs/ryanprice/2008/06/blogs-about-drupal"&gt;read more&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DrupalEasy/~4/315135037" height="1" width="1"/&gt;</description>
 <comments>http://drupaleasy.com/blogs/ryanprice/2008/06/blogs-about-drupal#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://drupaleasy.com/crss/node/7</wfw:commentRss>
 <pubDate>Thu, 19 Jun 2008 03:42:33 +0000</pubDate>
 <dc:creator>info@liberatr.net (Ryan Price)</dc:creator>
 <guid isPermaLink="false">7 at http://drupaleasy.com</guid>
<feedburner:origLink>http://drupaleasy.com/blogs/ryanprice/2008/06/blogs-about-drupal</feedburner:origLink></item>
<item>
 <title>Using Views 2 and Drupal 6 to Create a Related Pages Block</title>
 <link>http://feeds.feedburner.com/~r/DrupalEasy/~3/315135038/using-views-2-drupal-6-create-a-related-pages-block</link>
 <description>&lt;p&gt;Today's question comes from Dale at &lt;a title="" href="http://nfistudios.com"&gt;NFi Studios&lt;/a&gt; in Orlando, FL - my home town:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;Essentially:, what i'm trying to do is&lt;br /&gt;1. Determine the current nodes taxonomy terms&lt;br /&gt;2. Determine all other pages that share taxonomy terms&lt;br /&gt;3. Display the title (and link) to those pages in a block&lt;/p&gt;
&lt;p&gt;Using Drupal 6.2 and Views - Looked at a few modules, but nothing quite&lt;br /&gt;
exact - Reviewing some module snippets right now to see if I can&lt;br /&gt;
potentially use an argument to do it.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupaleasy.com/blogs/ryanprice/2008/06/using-views-2-drupal-6-create-a-related-pages-block"&gt;read more&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DrupalEasy/~4/315135038" height="1" width="1"/&gt;</description>
 <comments>http://drupaleasy.com/blogs/ryanprice/2008/06/using-views-2-drupal-6-create-a-related-pages-block#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://drupaleasy.com/crss/node/6</wfw:commentRss>
 <pubDate>Wed, 18 Jun 2008 02:09:10 +0000</pubDate>
 <dc:creator>info@liberatr.net (Ryan Price)</dc:creator>
 <guid isPermaLink="false">6 at http://drupaleasy.com</guid>
<feedburner:origLink>http://drupaleasy.com/blogs/ryanprice/2008/06/using-views-2-drupal-6-create-a-related-pages-block</feedburner:origLink></item>
<item>
 <title>Using AWK to Download and Unpack Drupal Modules</title>
 <link>http://feeds.feedburner.com/~r/DrupalEasy/~3/315135039/using-awk-download-unpack-drupal-modules</link>
 <description>&lt;p&gt;&lt;img alt="Security Update Required" title="Update Please!" id="wym-1213650275817" src="http://drupaleasy.com/files/update_req.png" height="46" width="213" style="float:right;padding-left:10px;"/&gt;When installing a new Drupal site (or when your list of available updates gets nice and long), you'll often have to download tons of modules, unpack them, and copy all of the resulting directories to your &lt;em&gt;sites/all/modules&lt;/em&gt; directory. Personally, I'm not a fan of all the clicking, downloading, unzipping and most of all &lt;em&gt;waiting!&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Today I finally settled on a workflow that gets the job done, and it's called the UNIX command line. If your server doesn't use some flavor of UNIX or Linux, or if your web host doesn't allow you shell access, you may want to stop reading after the next paragraph.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://drupaleasy.com/blogs/ryanprice/2008/06/using-awk-download-unpack-drupal-modules"&gt;read more&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DrupalEasy/~4/315135039" height="1" width="1"/&gt;</description>
 <comments>http://drupaleasy.com/blogs/ryanprice/2008/06/using-awk-download-unpack-drupal-modules#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://drupaleasy.com/crss/node/5</wfw:commentRss>
 <pubDate>Mon, 16 Jun 2008 20:54:15 +0000</pubDate>
 <dc:creator>info@liberatr.net (Ryan Price)</dc:creator>
 <guid isPermaLink="false">5 at http://drupaleasy.com</guid>
<feedburner:origLink>http://drupaleasy.com/blogs/ryanprice/2008/06/using-awk-download-unpack-drupal-modules</feedburner:origLink></item>
<item>
 <title>Editing HTML around Displayed View Fields: Views Theme Wizard</title>
 <link>http://feeds.feedburner.com/~r/DrupalEasy/~3/315135040/editing-html-around-displayed-view-fields-views-theme-wizard</link>
 <description>&lt;p&gt;Question #2 also comes to us via our &lt;a title="" href="http://ucf.facebook.com/topic.php?uid=19088299704&amp;amp;topic=3991"&gt;Facebook forum&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;&lt;h3&gt;Modifying existing views.&lt;br /&gt;&lt;/h3&gt;
&lt;p&gt;&lt;a title="" href="http://www.facebook.com/profile.php?id=700642840"&gt;Michael Blake&lt;/a&gt; (Orlando, FL) wrote on Jan 24, 2008 at 12:08 PM.&lt;/p&gt;
&lt;p&gt;I'm working on an existing Drupal application that has a custom Content Type. This includes some custom fields. When I change a custom field, such as add markup before and after it, This does not appear in my views. I think it's because my Views have been exported.&lt;/p&gt;
&lt;p&gt;However if I change the .php files in the themes directory directly on the server, I get what I want. My question is , if I go about it this way, can someone else come along export a view and erase my changes? Or do I need to re-export every time I make a change?&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;
&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&lt;a href="http://drupaleasy.com/blogs/ryanprice/2008/01/editing-html-around-displayed-view-fields-views-theme-wizard"&gt;read more&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/DrupalEasy/~4/315135040" height="1" width="1"/&gt;</description>
 <comments>http://drupaleasy.com/blogs/ryanprice/2008/01/editing-html-around-displayed-view-fields-views-theme-wizard#comments</comments>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://drupaleasy.com/crss/node/4</wfw:commentRss>
 <pubDate>Sat, 26 Jan 2008 23:00:58 +0000</pubDate>
 <dc:creator>info@liberatr.net (Ryan Price)</dc:creator>
 <guid isPermaLink="false">4 at http://drupaleasy.com</guid>
<feedburner:origLink>http://drupaleasy.com/blogs/ryanprice/2008/01/editing-html-around-displayed-view-fields-views-theme-wizard</feedburner:origLink></item>
<media:credit role="author">Ryan Price</media:credit><media:rating>nonadult</media:rating><media:description type="plain">To teach and spread Drupal to all creatures great and small.</media:description></channel>
</rss>
