<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Setting up Custom Content Types in WordPress 3.0</title>
	<atom:link href="http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/feed/" rel="self" type="application/rss+xml" />
	<link>http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/</link>
	<description>Alan Levine&#039;s space for barking about and playing with technology</description>
	<lastBuildDate>Sat, 26 May 2012 17:11:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Will</title>
		<link>http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/comment-page-1/#comment-81787</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Wed, 10 Nov 2010 12:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/?p=5095#comment-81787</guid>
		<description>Thanks, this is good stuff to get my head into! This really makes Wordpress more of a CMS which is great.</description>
		<content:encoded><![CDATA[<p>Thanks, this is good stuff to get my head into! This really makes WordPress more of a CMS which is great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pinning WordPress 3 Custom Content to the Map (b) - CogDogBlog</title>
		<link>http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/comment-page-1/#comment-81227</link>
		<dc:creator>Pinning WordPress 3 Custom Content to the Map (b) - CogDogBlog</dc:creator>
		<pubDate>Tue, 26 Oct 2010 12:50:30 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/?p=5095#comment-81227</guid>
		<description>[...] up to this, I began by overviewing the plans for a new web project, we set up the places to create the new content types, and introduced the benefits using child themes. Then we dove headfirst into the code to create the [...]</description>
		<content:encoded><![CDATA[<p>[...] up to this, I began by overviewing the plans for a new web project, we set up the places to create the new content types, and introduced the benefits using child themes. Then we dove headfirst into the code to create the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wordpress 3.0 Features for Designers &#124; StylizedWeb.com</title>
		<link>http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/comment-page-1/#comment-81223</link>
		<dc:creator>Wordpress 3.0 Features for Designers &#124; StylizedWeb.com</dc:creator>
		<pubDate>Tue, 26 Oct 2010 09:02:20 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/?p=5095#comment-81223</guid>
		<description>[...] If you are the type that likes to get your hands dirty I recommend you read this great article about setting up custom content types and fields. [...]</description>
		<content:encoded><![CDATA[<p>[...] If you are the type that likes to get your hands dirty I recommend you read this great article about setting up custom content types and fields. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Levine aka CogDog</title>
		<link>http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/comment-page-1/#comment-80170</link>
		<dc:creator>Alan Levine aka CogDog</dc:creator>
		<pubDate>Fri, 27 Aug 2010 17:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/?p=5095#comment-80170</guid>
		<description>It&#039;s easier than that-- just modify the template that displays the post, usually single.php, and remove the parts the display the comments. This way comments come in, but are never displayed.</description>
		<content:encoded><![CDATA[<p>It&#8217;s easier than that&#8211; just modify the template that displays the post, usually single.php, and remove the parts the display the comments. This way comments come in, but are never displayed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cathy Finn-Derecki</title>
		<link>http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/comment-page-1/#comment-80169</link>
		<dc:creator>Cathy Finn-Derecki</dc:creator>
		<pubDate>Fri, 27 Aug 2010 17:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/?p=5095#comment-80169</guid>
		<description>This has been wonderful, and I have to thank you (and Jim Groom, and Martha Burtis). I have one question: I&#039;d like to customize the nature of the comments for this custom post type. We&#039;ve developed a really simply Classfied ad custom post type. I&#039;d like to allow comments (in this case, inquiries about the product), but have the option to have them sent privately to the author, not displayed on the Web site. I&#039;m thinking that I can just suppress the display with css, but that seems clunky. Any ideas?</description>
		<content:encoded><![CDATA[<p>This has been wonderful, and I have to thank you (and Jim Groom, and Martha Burtis). I have one question: I&#8217;d like to customize the nature of the comments for this custom post type. We&#8217;ve developed a really simply Classfied ad custom post type. I&#8217;d like to allow comments (in this case, inquiries about the product), but have the option to have them sent privately to the author, not displayed on the Web site. I&#8217;m thinking that I can just suppress the display with css, but that seems clunky. Any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roundup WordPress 3.0 Custom Content Type - CogDogBlog</title>
		<link>http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/comment-page-1/#comment-80145</link>
		<dc:creator>Roundup WordPress 3.0 Custom Content Type - CogDogBlog</dc:creator>
		<pubDate>Thu, 26 Aug 2010 17:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/?p=5095#comment-80145</guid>
		<description>[...] Creating the content types. The easiest part, and the beauty of functions.php [...]</description>
		<content:encoded><![CDATA[<p>[...] Creating the content types. The easiest part, and the beauty of functions.php [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Levine aka CogDog</title>
		<link>http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/comment-page-1/#comment-79705</link>
		<dc:creator>Alan Levine aka CogDog</dc:creator>
		<pubDate>Wed, 04 Aug 2010 22:13:06 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/?p=5095#comment-79705</guid>
		<description>Hmm, those functions do not come into play at this point; they are used in the next section
http://cogdogblog.com/2010/06/06/put-on-your-hazmat-suits/

It is possible I got some of the demo files crossed, as I had to go back and pull out some parts that were introduced sequentially...</description>
		<content:encoded><![CDATA[<p>Hmm, those functions do not come into play at this point; they are used in the next section<br />
<a href="http://cogdogblog.com/2010/06/06/put-on-your-hazmat-suits/" rel="nofollow">http://cogdogblog.com/2010/06/06/put-on-your-hazmat-suits/</a></p>
<p>It is possible I got some of the demo files crossed, as I had to go back and pull out some parts that were introduced sequentially&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/comment-page-1/#comment-79704</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Wed, 04 Aug 2010 21:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/?p=5095#comment-79704</guid>
		<description>Alan,

Excellent stuff here. I think you left out two functions from the functions.php.

&lt;code&gt;function midea_proj_options() {
	// add meta data fields for a MIDEA organization content type
	global $post;

	// Use nonce for verification
	echo &#039;&lt;input type=&quot;hidden&quot; name=&quot;midea_noncename&quot; id=&quot;midea_noncename&quot; value=&quot;&#039; .
    wp_create_nonce( &#039;MyNonceCode&#039; ) . &#039;&quot; /&gt;&#039;;

	$my_fields = midea_proj_fields(); // fields for this content type

	foreach ($my_fields as $key =&gt; $value) {
		// load values into our array
		$my_fields[$key] = get_post_meta($post-&gt;ID, &#039;midea-proj-&#039; . $key, true);
	}	

	echo &#039;&lt;p&gt;&lt;strong&gt;Organization&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;label&gt;name:&lt;/label&gt;&lt;br /&gt; &lt;input name=&quot;midea-proj-org&quot; size=&quot;60&quot; value=&quot;&#039; . $my_fields[&#039;org&#039;] . &#039;&quot; /&gt;&lt;/p&gt;&#039; . &quot;\n&quot;;
	echo &#039;&lt;p&gt;&lt;label&gt;web site&lt;/label&gt;:&lt;br /&gt; &lt;input name=&quot;midea-proj-url&quot; size=&quot;60&quot; value=&quot;&#039; . $my_fields[&#039;url&#039;] . &#039;&quot; /&gt;&lt;/p&gt;&#039; . &quot;\n&quot;;
	echo &#039;&lt;p&gt;&lt;label&gt;rating&lt;/label&gt;:&lt;br /&gt; &lt;input name=&quot;midea-proj-rating&quot; size=&quot;60&quot;  value=&quot;&#039; . $my_fields[&#039;rating&#039;] . &#039;&quot; /&gt;&lt;/p&gt;&#039; . &quot;\n&quot;;
}

function midea_event_options() {
	// add meta data fields for a MIDEA organization content type
	global $post;

	// Use nonce for verification
	echo &#039;&lt;input type=&quot;hidden&quot; name=&quot;midea_noncename&quot; id=&quot;midea_noncename&quot; value=&quot;&#039; .
    wp_create_nonce( &#039;MyNonceCode&#039; ) . &#039;&quot; /&gt;&#039;;

	$my_fields = midea_event_fields(); // fields for this content type

	foreach ($my_fields as $key =&gt; $value) {
		// load values into our array
		$my_fields[$key] = get_post_meta($post-&gt;ID, &#039;midea-event-&#039; . $key, true);
	}	

	echo &#039;&lt;p&gt;&lt;p&gt;&lt;label&gt;start:&lt;/label&gt;&lt;br /&gt; &lt;input name=&quot;midea-event-start&quot; size=&quot;60&quot; value=&quot;&#039; . $my_fields[&#039;start&#039;] . &#039;&quot; /&gt;&lt;/p&gt;&#039; . &quot;\n&quot;;
	echo &#039;&lt;p&gt;&lt;p&gt;&lt;label&gt;end:&lt;/label&gt;&lt;br /&gt; &lt;input name=&quot;midea-event-end&quot; size=&quot;60&quot; value=&quot;&#039; . $my_fields[&#039;end&#039;] . &#039;&quot; /&gt;&lt;/p&gt;&#039; . &quot;\n&quot;;
	echo &#039;&lt;p&gt;&lt;label&gt;web site&lt;/label&gt;:&lt;br /&gt; &lt;input name=&quot;midea-event-url&quot; size=&quot;60&quot; value=&quot;&#039; . $my_fields[&#039;url&#039;] . &#039;&quot; /&gt;&lt;/p&gt;&#039; . &quot;\n&quot;;
	echo &#039;&lt;p&gt;&lt;strong&gt;Location&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;label&gt;address&lt;/label&gt;:&lt;br /&gt;&lt;textarea name=&quot;midea-event-location&quot; rows=&quot;2&quot; cols=&quot;55&quot;&gt;&#039; . $my_fields[&#039;address&#039;] . &#039;&lt;/textarea&gt;&lt;/p&gt;&#039; . &quot;\n&quot;;&lt;/code&gt;

I was getting an error about expecting a valid callback function or something until I added these to the functions.php file. Now to figure out how to allow for another rich text editing box.</description>
		<content:encoded><![CDATA[<p>Alan,</p>
<p>Excellent stuff here. I think you left out two functions from the functions.php.</p>
<p><code>function midea_proj_options() {<br />
	// add meta data fields for a MIDEA organization content type<br />
	global $post;</p>
<p>	// Use nonce for verification<br />
	echo '<br />
<input type="hidden" name="midea_noncename" id="midea_noncename" value="' .<br />
    wp_create_nonce( 'MyNonceCode' ) . '" />';</p>
<p>	$my_fields = midea_proj_fields(); // fields for this content type</p>
<p>	foreach ($my_fields as $key => $value) {<br />
		// load values into our array<br />
		$my_fields[$key] = get_post_meta($post->ID, 'midea-proj-' . $key, true);<br />
	}	</p>
<p>	echo '
<p><strong>Organization</strong></p>
<p><label>name:</label><br /> <br />
<input name="midea-proj-org" size="60" value="' . $my_fields['org'] . '" /></p>
<p>' . "\n";<br />
	echo '
<p><label>web site</label>:<br /> <br />
<input name="midea-proj-url" size="60" value="' . $my_fields['url'] . '" /></p>
<p>' . "\n";<br />
	echo '
<p><label>rating</label>:<br /> <br />
<input name="midea-proj-rating" size="60"  value="' . $my_fields['rating'] . '" /></p>
<p>' . "\n";<br />
}</p>
<p>function midea_event_options() {<br />
	// add meta data fields for a MIDEA organization content type<br />
	global $post;</p>
<p>	// Use nonce for verification<br />
	echo '<br />
<input type="hidden" name="midea_noncename" id="midea_noncename" value="' .<br />
    wp_create_nonce( 'MyNonceCode' ) . '" />';</p>
<p>	$my_fields = midea_event_fields(); // fields for this content type</p>
<p>	foreach ($my_fields as $key => $value) {<br />
		// load values into our array<br />
		$my_fields[$key] = get_post_meta($post->ID, 'midea-event-' . $key, true);<br />
	}	</p>
<p>	echo '
</p>
<p><label>start:</label><br /> <br />
<input name="midea-event-start" size="60" value="' . $my_fields['start'] . '" /></p>
<p>' . "\n";<br />
	echo '
</p>
<p><label>end:</label><br /> <br />
<input name="midea-event-end" size="60" value="' . $my_fields['end'] . '" /></p>
<p>' . "\n";<br />
	echo '
<p><label>web site</label>:<br /> <br />
<input name="midea-event-url" size="60" value="' . $my_fields['url'] . '" /></p>
<p>' . "\n";<br />
	echo '
<p><strong>Location</strong></p>
<p><label>address</label>:<br /><textarea name="midea-event-location" rows="2" cols="55">' . $my_fields['address'] . '</textarea></p>
<p>' . "\n";</code></p>
<p>I was getting an error about expecting a valid callback function or something until I added these to the functions.php file. Now to figure out how to allow for another rich text editing box.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dressing up and Displaying WordPress 3 Custom Post Content (a) - CogDogBlog</title>
		<link>http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/comment-page-1/#comment-79354</link>
		<dc:creator>Dressing up and Displaying WordPress 3 Custom Post Content (a) - CogDogBlog</dc:creator>
		<pubDate>Thu, 22 Jul 2010 05:59:42 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/?p=5095#comment-79354</guid>
		<description>[...] this series, I started with an overview of the plans for the MIDEA project, we set up the places to create the new content types, and introduced the benefits using child themes. Then we took it up a notch to dive into the code [...]</description>
		<content:encoded><![CDATA[<p>[...] this series, I started with an overview of the plans for the MIDEA project, we set up the places to create the new content types, and introduced the benefits using child themes. Then we took it up a notch to dive into the code [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Put on Your HazMat Suits- Setting Up Metadata For WordPress 3 Custom Content Types - CogDogBlog</title>
		<link>http://cogdogblog.com/2010/05/28/setting-up-custom-contenttypes/comment-page-1/#comment-79288</link>
		<dc:creator>Put on Your HazMat Suits- Setting Up Metadata For WordPress 3 Custom Content Types - CogDogBlog</dc:creator>
		<pubDate>Mon, 19 Jul 2010 04:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/?p=5095#comment-79288</guid>
		<description>[...] custom content types, same thing), I overviewed the plans for the MIDEA web site, we set up the places to create the new content types, and diverged into some set up magic using child [...]</description>
		<content:encoded><![CDATA[<p>[...] custom content types, same thing), I overviewed the plans for the MIDEA web site, we set up the places to create the new content types, and diverged into some set up magic using child [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

