<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: How WordPress falters as a CMS: Multiple content fields</title>
	<atom:link href="http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=how-wordpress-falters-as-a-cms</link>
	<description>Occassional posts on user experience design, faith, and family.</description>
	<lastBuildDate>Sun, 04 Jul 2010 19:22:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: ThaClown</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1619</link>
		<dc:creator>ThaClown</dc:creator>
		<pubDate>Mon, 31 May 2010 15:12:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1619</guid>
		<description>Totally agree! I am just working on an new website, it need to be multilingual &amp; have different field on the main page.
I use WPML for the multilingual part and am using WP 3.0.
And tried Magic Fields &amp; Flutter but they do not work with WPML!

The thing I am not able to do is simply create 4 fields under the main page admin where the owner can add different content to each fields.
Like:
- Box 1 left
- Box 2 right
- Box 3 bottom left
- Box 4 bottom right

The site owner is not very technical and I can not use plug-ins or custom fields, it is just not as easy to use...

If only WordPress had Template Variables like MODx CMS or MODx CMS had a blogging system like WordPress....</description>
		<content:encoded><![CDATA[<p>Totally agree! I am just working on an new website, it need to be multilingual &amp; have different field on the main page.<br />
I use WPML for the multilingual part and am using WP 3.0.<br />
And tried Magic Fields &amp; Flutter but they do not work with WPML!</p>
<p>The thing I am not able to do is simply create 4 fields under the main page admin where the owner can add different content to each fields.<br />
Like:<br />
- Box 1 left<br />
- Box 2 right<br />
- Box 3 bottom left<br />
- Box 4 bottom right</p>
<p>The site owner is not very technical and I can not use plug-ins or custom fields, it is just not as easy to use&#8230;</p>
<p>If only WordPress had Template Variables like MODx CMS or MODx CMS had a blogging system like WordPress&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toon</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1328</link>
		<dc:creator>Toon</dc:creator>
		<pubDate>Thu, 04 Mar 2010 13:02:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1328</guid>
		<description>Just for the record, Magic Fields is a fork of Flutter, the former attempting to correct some shortcomings of the latter. 
For very large sites, this is not the way to go, since the &#039;custom fields&#039; are stored in the database in a very inefficient way. In my experience, however, this is only a practical problem for internationally-oriented sites with very large amounts of content (I&#039;d say Amazon or eBay, but that&#039;s probably stretching it a bit). It&#039;s not an issue if you&#039;ve got a &#039;mere&#039; 50.000 posts and, say 10.000 visitors a day. Inefficiency is, of course, inefficiency, and it would be a huge plus if Wordpress accomodated a bit more flexibility in using custom fields.
Depending on your needs, Pods is the better, more scaleable option. Pods allows you to create a whole separate content system inside of Wordpress, separate db tables &#039;n&#039; all. And that&#039;s also one of its limitations. If your &#039;custom&#039; content needs to be heavily integrated with your posts, this is difficult to do in a user-friendly way.
For example, if you look at http://www.tail-out.com/, the banners at the top of the page and the videos in the left column are &#039;pods&#039;, whereas the extra information in the left column on http://www.tail-out.com/archives/50-demon-games.html is stored in custom fields. For me, a combination of both approaches usually works best.</description>
		<content:encoded><![CDATA[<p>Just for the record, Magic Fields is a fork of Flutter, the former attempting to correct some shortcomings of the latter.<br />
For very large sites, this is not the way to go, since the &#8216;custom fields&#8217; are stored in the database in a very inefficient way. In my experience, however, this is only a practical problem for internationally-oriented sites with very large amounts of content (I&#8217;d say Amazon or eBay, but that&#8217;s probably stretching it a bit). It&#8217;s not an issue if you&#8217;ve got a &#8216;mere&#8217; 50.000 posts and, say 10.000 visitors a day. Inefficiency is, of course, inefficiency, and it would be a huge plus if WordPress accomodated a bit more flexibility in using custom fields.<br />
Depending on your needs, Pods is the better, more scaleable option. Pods allows you to create a whole separate content system inside of WordPress, separate db tables &#8216;n&#8217; all. And that&#8217;s also one of its limitations. If your &#8216;custom&#8217; content needs to be heavily integrated with your posts, this is difficult to do in a user-friendly way.<br />
For example, if you look at <a href="http://www.tail-out.com/" rel="nofollow">http://www.tail-out.com/</a>, the banners at the top of the page and the videos in the left column are &#8216;pods&#8217;, whereas the extra information in the left column on <a href="http://www.tail-out.com/archives/50-demon-games.html" rel="nofollow">http://www.tail-out.com/archives/50-demon-games.html</a> is stored in custom fields. For me, a combination of both approaches usually works best.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Bostrom</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1244</link>
		<dc:creator>Eric Bostrom</dc:creator>
		<pubDate>Fri, 08 Jan 2010 19:18:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1244</guid>
		<description>Nope, If I&#039;m in the regular &#039;Post&#039; write panel I get the default WP layout (or whatever I&#039;ve customized). All of the magic fields entry and customization appear if I click on the &#039;Plans&#039; write panel.</description>
		<content:encoded><![CDATA[<p>Nope, If I&#8217;m in the regular &#8216;Post&#8217; write panel I get the default WP layout (or whatever I&#8217;ve customized). All of the magic fields entry and customization appear if I click on the &#8216;Plans&#8217; write panel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davin Granroth</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1243</link>
		<dc:creator>Davin Granroth</dc:creator>
		<pubDate>Fri, 08 Jan 2010 11:33:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1243</guid>
		<description>That looks great. I haven&#039;t tried Magic-Fields yet, but as you point out w/your examples, the fields are called in the template files so you can have them show for specific page types (templates). 

But, on the wp-admin add/edit post page, the Magic-Fields form always appears, regardless of the page template you choose, right? Or not?

And, yeah, isn&#039;t fax where good data goes to die a low-res death? ;-)</description>
		<content:encoded><![CDATA[<p>That looks great. I haven&#8217;t tried Magic-Fields yet, but as you point out w/your examples, the fields are called in the template files so you can have them show for specific page types (templates). </p>
<p>But, on the wp-admin add/edit post page, the Magic-Fields form always appears, regardless of the page template you choose, right? Or not?</p>
<p>And, yeah, isn&#8217;t fax where good data goes to die a low-res death? <img src='http://blog.davingranroth.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Bostrom</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1242</link>
		<dc:creator>Eric Bostrom</dc:creator>
		<pubDate>Fri, 08 Jan 2010 05:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1242</guid>
		<description>Heythanks, I appreciate it! In my opinion, the flexibility of WP is what is intense!

I&#039;m now doing some crazier stuff. After I built that posting interface with Magic fields, I spread that data out as necessary. I&#039;m using category-N.php and single-N.php (with a functions add_filter) to have special category and single post templates for just one part of the site I&#039;m working on. My next step is going to be an implementation of Role-scoper to limit the access to that special category and custom write panel for just one user, so the one user can only post to that category (much like your add-new-musician example). Once I&#039;m done defining post access I can set up an interface that will let my subcontractors auto-reg for level 0 accounts, so they can view content (like plan sheets and specification manuals) that I want to hide from other general contractors or plan rooms.

Since I work alone and I&#039;ve got no one to geek out with, behold:
(please disregard the tabular data at the bottom of these examples, that&#039;s a holdover. also: disregard template aesthetics ;)
Old plans site, uses hand built php/csv style fread/write: http://is.gd/5TuUa
Same content using Magic-Fields as mentioned: http://is.gd/5TuVC
Same content using Magic-fields, custom page template, with that category in The Loop below it: http://is.gd/5TuYo
Same content using Magic-Fields, custom category-N.php template: http://is.gd/5Tv9O

Here&#039;s a single post, using a custom single-N.php template: http://is.gd/5TveA
Here&#039;s a different post, using the default single.php template: http://is.gd/5TvR4
The reason this was important is that the custom Magic Fields don&#039;t appear within The Loop or the_content() you have to call them, so they aren&#039;t going to show up in RSS on the default single.php. This is a huge hole for my usage and probably for yours... 

What this all means is start to finish I can offload this job to a receptionist, have her post or edit the appropriate content for the plans site, and have that data automagically post to twitter and rss like normal. Saving us $$ in long distance faxing, and overhead emailing that same content to our subcontractors. Now the problem will be getting subcontractors on board, when their most impressive technology is a plain paper fax machine. :D

Cheers!</description>
		<content:encoded><![CDATA[<p>Heythanks, I appreciate it! In my opinion, the flexibility of WP is what is intense!</p>
<p>I&#8217;m now doing some crazier stuff. After I built that posting interface with Magic fields, I spread that data out as necessary. I&#8217;m using category-N.php and single-N.php (with a functions add_filter) to have special category and single post templates for just one part of the site I&#8217;m working on. My next step is going to be an implementation of Role-scoper to limit the access to that special category and custom write panel for just one user, so the one user can only post to that category (much like your add-new-musician example). Once I&#8217;m done defining post access I can set up an interface that will let my subcontractors auto-reg for level 0 accounts, so they can view content (like plan sheets and specification manuals) that I want to hide from other general contractors or plan rooms.</p>
<p>Since I work alone and I&#8217;ve got no one to geek out with, behold:<br />
(please disregard the tabular data at the bottom of these examples, that&#8217;s a holdover. also: disregard template aesthetics <img src='http://blog.davingranroth.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /><br />
Old plans site, uses hand built php/csv style fread/write: <a href="http://is.gd/5TuUa" rel="nofollow">http://is.gd/5TuUa</a><br />
Same content using Magic-Fields as mentioned: <a href="http://is.gd/5TuVC" rel="nofollow">http://is.gd/5TuVC</a><br />
Same content using Magic-fields, custom page template, with that category in The Loop below it: <a href="http://is.gd/5TuYo" rel="nofollow">http://is.gd/5TuYo</a><br />
Same content using Magic-Fields, custom category-N.php template: <a href="http://is.gd/5Tv9O" rel="nofollow">http://is.gd/5Tv9O</a></p>
<p>Here&#8217;s a single post, using a custom single-N.php template: <a href="http://is.gd/5TveA" rel="nofollow">http://is.gd/5TveA</a><br />
Here&#8217;s a different post, using the default single.php template: <a href="http://is.gd/5TvR4" rel="nofollow">http://is.gd/5TvR4</a><br />
The reason this was important is that the custom Magic Fields don&#8217;t appear within The Loop or the_content() you have to call them, so they aren&#8217;t going to show up in RSS on the default single.php. This is a huge hole for my usage and probably for yours&#8230; </p>
<p>What this all means is start to finish I can offload this job to a receptionist, have her post or edit the appropriate content for the plans site, and have that data automagically post to twitter and rss like normal. Saving us $$ in long distance faxing, and overhead emailing that same content to our subcontractors. Now the problem will be getting subcontractors on board, when their most impressive technology is a plain paper fax machine. <img src='http://blog.davingranroth.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davin Granroth</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1240</link>
		<dc:creator>Davin Granroth</dc:creator>
		<pubDate>Wed, 06 Jan 2010 23:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1240</guid>
		<description>Hey Eric, just checked out your site. Your artwork over at http://www.ericthomasbostrom.com is intense!</description>
		<content:encoded><![CDATA[<p>Hey Eric, just checked out your site. Your artwork over at <a href="http://www.ericthomasbostrom.com" rel="nofollow">http://www.ericthomasbostrom.com</a> is intense!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davin Granroth</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1239</link>
		<dc:creator>Davin Granroth</dc:creator>
		<pubDate>Wed, 06 Jan 2010 23:46:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1239</guid>
		<description>Eric, thanks for linking that image to the post interface. Yep, it seems like Magic fields could really handle a lot of these types of problems. 

I still lean towards thinking that that type of functionality should be part of WordPress itself, not a plug-in that might break with each WP upgrade.</description>
		<content:encoded><![CDATA[<p>Eric, thanks for linking that image to the post interface. Yep, it seems like Magic fields could really handle a lot of these types of problems. </p>
<p>I still lean towards thinking that that type of functionality should be part of WordPress itself, not a plug-in that might break with each WP upgrade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Bostrom</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1238</link>
		<dc:creator>Eric Bostrom</dc:creator>
		<pubDate>Wed, 06 Jan 2010 22:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1238</guid>
		<description>Hmm, the comment ate my loop! Trying again. If it fails and anyone wants it, just email me.&lt;code&gt;Projects out to bid:










, &lt;b&gt;Bids:&lt;/b&gt; 
&lt;?php echo &quot; &lt;b&gt;Estimator:&lt;/b&gt; &quot;,$Estimator,&quot;&lt;b&gt;Addenda:&lt;/b&gt; &quot;,$NumAdd,&quot;
 &lt;b&gt;Prevailing
wage:&lt;/b&gt; &quot;,$PrevWage,&quot; &lt;b&gt;Special Goals:&lt;/b&gt; &quot;,$SpecialGoals; ?&gt;



&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>Hmm, the comment ate my loop! Trying again. If it fails and anyone wants it, just email me.<code>Projects out to bid:</p>
<p>, <b>Bids:</b><br />
&lt;?php echo &quot; <b>Estimator:</b> ",$Estimator,"<b>Addenda:</b> ",$NumAdd,"<br />
 <b>Prevailing<br />
wage:</b> ",$PrevWage," <b>Special Goals:</b> ",$SpecialGoals; ?&gt;</p>
<p></code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Bostrom</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1237</link>
		<dc:creator>Eric Bostrom</dc:creator>
		<pubDate>Wed, 06 Jan 2010 22:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1237</guid>
		<description>I had this problem a few hours ago, then I installed the Magic Fields plugin, created a new custom write panel, then created some custom fields for that panel. Now I have something that would have been useful for your musicians, and useable without the screencast. New post interface: http://imgur.com/YX0V8
I spit all the fields back out at the page within The Loop.

Hovering the &#039;What&#039;s this&#039; shows the tooltip text I defined when I set up the new fields in Magic Fields. It&#039;s really slick! You can even change the type of fields, their default values, what category the post defaults to and which fields are required in order to publish.

Here&#039;s my loop/field processing, it&#039;s inelegant but I wanted to get it working before I prettied it up.:
Projects out to bid:










, &lt;b&gt;Bids:&lt;/b&gt; 
&lt;?php echo &quot; &lt;b&gt;Estimator:&lt;/b&gt; &quot;,$Estimator,&quot;&lt;b&gt;Addenda:&lt;/b&gt; &quot;,$NumAdd,&quot;
 &lt;b&gt;Prevailing
wage:&lt;/b&gt; &quot;,$PrevWage,&quot; &lt;b&gt;Special Goals:&lt;/b&gt; &quot;,$SpecialGoals; ?&gt;


</description>
		<content:encoded><![CDATA[<p>I had this problem a few hours ago, then I installed the Magic Fields plugin, created a new custom write panel, then created some custom fields for that panel. Now I have something that would have been useful for your musicians, and useable without the screencast. New post interface: <a href="http://imgur.com/YX0V8" rel="nofollow">http://imgur.com/YX0V8</a><br />
I spit all the fields back out at the page within The Loop.</p>
<p>Hovering the &#8216;What&#8217;s this&#8217; shows the tooltip text I defined when I set up the new fields in Magic Fields. It&#8217;s really slick! You can even change the type of fields, their default values, what category the post defaults to and which fields are required in order to publish.</p>
<p>Here&#8217;s my loop/field processing, it&#8217;s inelegant but I wanted to get it working before I prettied it up.:<br />
Projects out to bid:</p>
<p>, <b>Bids:</b><br />
&lt;?php echo &quot; <b>Estimator:</b> &#8220;,$Estimator,&#8221;<b>Addenda:</b> &#8220;,$NumAdd,&#8221;<br />
 <b>Prevailing<br />
wage:</b> &#8220;,$PrevWage,&#8221; <b>Special Goals:</b> &#8220;,$SpecialGoals; ?&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1219</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Tue, 22 Dec 2009 17:16:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1219</guid>
		<description>Zach, perhaps I&#039;m old fashioned, but a &quot;workaround&quot; should, well um, work :)</description>
		<content:encoded><![CDATA[<p>Zach, perhaps I&#8217;m old fashioned, but a &#8220;workaround&#8221; should, well um, work <img src='http://blog.davingranroth.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davin Granroth</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1216</link>
		<dc:creator>Davin Granroth</dc:creator>
		<pubDate>Tue, 22 Dec 2009 03:52:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1216</guid>
		<description>That&#039;s cool. I didn&#039;t know about those workarounds. It looks like &quot;More Fields&quot; is listed as broken at the moment, probably because of the recent upgrade to WP 2.9. Hopefully the plugin gets fixed pronto for all those WordPress users that are using it.</description>
		<content:encoded><![CDATA[<p>That&#8217;s cool. I didn&#8217;t know about those workarounds. It looks like &#8220;More Fields&#8221; is listed as broken at the moment, probably because of the recent upgrade to WP 2.9. Hopefully the plugin gets fixed pronto for all those WordPress users that are using it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zachary Spencer</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1213</link>
		<dc:creator>Zachary Spencer</dc:creator>
		<pubDate>Mon, 21 Dec 2009 20:24:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1213</guid>
		<description>&quot;There&#039;s a workaround for that!&quot;

This wordpress.org post talks about applying tinymce to a custom content field. http://wordpress.org/support/topic/331589

There&#039;s also a plugin for it called more fields: http://wordpress.org/extend/plugins/more-fields/</description>
		<content:encoded><![CDATA[<p>&#8220;There&#8217;s a workaround for that!&#8221;</p>
<p>This wordpress.org post talks about applying tinymce to a custom content field. <a href="http://wordpress.org/support/topic/331589" rel="nofollow">http://wordpress.org/support/topic/331589</a></p>
<p>There&#8217;s also a plugin for it called more fields: <a href="http://wordpress.org/extend/plugins/more-fields/" rel="nofollow">http://wordpress.org/extend/plugins/more-fields/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MattFlies: 100 resources for Thesis Theme users</title>
		<link>http://blog.davingranroth.com/2009/12/how-wordpress-falters-as-a-cms/comment-page-1/#comment-1201</link>
		<dc:creator>MattFlies: 100 resources for Thesis Theme users</dc:creator>
		<pubDate>Sun, 20 Dec 2009 15:30:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davingranroth.com/?p=1015#comment-1201</guid>
		<description>[...] How WordPress falters as a CMS: Multiple content fields &#124; Davin&#039;s blog [...]</description>
		<content:encoded><![CDATA[<p>[...] How WordPress falters as a CMS: Multiple content fields | Davin&#39;s blog [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
