<?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: Archive toolbar for campaigns</title>
	<atom:link href="http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/</link>
	<description>MailChimp, email marketing, and monkeys!</description>
	<lastBuildDate>Fri, 12 Mar 2010 12:25:00 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: kevin cawley</title>
		<link>http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/comment-page-1/#comment-7184</link>
		<dc:creator>kevin cawley</dc:creator>
		<pubDate>Wed, 03 Mar 2010 01:58:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=2812#comment-7184</guid>
		<description>thanks for this feature.  thanks for the rsvp to me on the question of how to set it up.
I am hoping the translate feature on the toolbar means that I no longer need that huge long string of languages that hangs on at the end of the campaign when i use the merge tag feature for tranlating.</description>
		<content:encoded><![CDATA[<p>thanks for this feature.  thanks for the rsvp to me on the question of how to set it up.<br />
I am hoping the translate feature on the toolbar means that I no longer need that huge long string of languages that hangs on at the end of the campaign when i use the merge tag feature for tranlating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristof</title>
		<link>http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/comment-page-1/#comment-6755</link>
		<dc:creator>Kristof</dc:creator>
		<pubDate>Thu, 28 Jan 2010 13:52:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=2812#comment-6755</guid>
		<description>please translate the tool bar in other languages

only in english</description>
		<content:encoded><![CDATA[<p>please translate the tool bar in other languages</p>
<p>only in english</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alain</title>
		<link>http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/comment-page-1/#comment-5291</link>
		<dc:creator>alain</dc:creator>
		<pubDate>Tue, 29 Sep 2009 08:37:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=2812#comment-5291</guid>
		<description>Is it possible to translate the text in the tool bar (share, translate, view past issues...)? It is only in english.

Thanks</description>
		<content:encoded><![CDATA[<p>Is it possible to translate the text in the tool bar (share, translate, view past issues&#8230;)? It is only in english.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/comment-page-1/#comment-4321</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Mon, 13 Jul 2009 22:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=2812#comment-4321</guid>
		<description>Thanks guys!  MailChimp keeps getting better and better.  We will be archiving all of our campaigns on our new website once it launches so the new archive toolbar is both timely and helpful.</description>
		<content:encoded><![CDATA[<p>Thanks guys!  MailChimp keeps getting better and better.  We will be archiving all of our campaigns on our new website once it launches so the new archive toolbar is both timely and helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/comment-page-1/#comment-3692</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 23 Apr 2009 17:32:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=2812#comment-3692</guid>
		<description>Thanks!  Sounds good enough for me.  :)  Keep up the good work.</description>
		<content:encoded><![CDATA[<p>Thanks!  Sounds good enough for me.  <img src='http://www.mailchimp.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   Keep up the good work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aarron Walter</title>
		<link>http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/comment-page-1/#comment-3691</link>
		<dc:creator>Aarron Walter</dc:creator>
		<pubDate>Thu, 23 Apr 2009 12:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=2812#comment-3691</guid>
		<description>I can&#039;t give you a timeline on when to expect a more sophisticated tool set for handling archive content display, but yes, it would have conditionals that would allow you to specify what gets shown/hidden in an archive page.</description>
		<content:encoded><![CDATA[<p>I can&#8217;t give you a timeline on when to expect a more sophisticated tool set for handling archive content display, but yes, it would have conditionals that would allow you to specify what gets shown/hidden in an archive page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/comment-page-1/#comment-3686</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Wed, 22 Apr 2009 21:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=2812#comment-3686</guid>
		<description>Hi Arron -- Thanks again for your recommendation re: form default fields.  Trent and I are working together on this.  The campaign archive (and social-shared versions) are going to be more important to us soon, so I was wondering if there was an eta or rough timeline on when we might expect The Fancy Solution.  Can you give us an idea of how it would work?

Would it help with conditional cases as well? For instance, would we be able to set a condition to display the &quot;Click for web version / Click to unsubscribe&quot; sections only in the actual emails, but remove it for archived versions and shared (eg facebook, twitter) versions?

Thanks again!</description>
		<content:encoded><![CDATA[<p>Hi Arron &#8212; Thanks again for your recommendation re: form default fields.  Trent and I are working together on this.  The campaign archive (and social-shared versions) are going to be more important to us soon, so I was wondering if there was an eta or rough timeline on when we might expect The Fancy Solution.  Can you give us an idea of how it would work?</p>
<p>Would it help with conditional cases as well? For instance, would we be able to set a condition to display the &#8220;Click for web version / Click to unsubscribe&#8221; sections only in the actual emails, but remove it for archived versions and shared (eg facebook, twitter) versions?</p>
<p>Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aarron Walter</title>
		<link>http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/comment-page-1/#comment-3481</link>
		<dc:creator>Aarron Walter</dc:creator>
		<pubDate>Wed, 01 Apr 2009 18:14:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=2812#comment-3481</guid>
		<description>As it turns out, using fancy merge tag conditionals won&#039;t render as expected in a campaign archive. Sorry for misleading you, but I do have a solution to share.

In the form builder (lists &gt; create forms), you can set a predefined value for your fields (Ex: for your first name field, you might set the predefined value to  &quot;customer&quot;). Then your campaign archive will show this default value when it encounters the merge tag. 

This screenshot explains it a bit better: http://eepurl.com/NRi

We also have a fancier solution in the works that will give you more control over what is shown in your campaign archive.</description>
		<content:encoded><![CDATA[<p>As it turns out, using fancy merge tag conditionals won&#8217;t render as expected in a campaign archive. Sorry for misleading you, but I do have a solution to share.</p>
<p>In the form builder (lists &gt; create forms), you can set a predefined value for your fields (Ex: for your first name field, you might set the predefined value to  &#8220;customer&#8221;). Then your campaign archive will show this default value when it encounters the merge tag. </p>
<p>This screenshot explains it a bit better: <a href="http://eepurl.com/NRi" rel="nofollow">http://eepurl.com/NRi</a></p>
<p>We also have a fancier solution in the works that will give you more control over what is shown in your campaign archive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/comment-page-1/#comment-3425</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Sat, 28 Mar 2009 19:28:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=2812#comment-3425</guid>
		<description>It&#039;s going live when v4.1 goes live. The upgrade process starts Sunday, and then it&#039;ll take a few days to go through and upgrade all our users. Sometimes between Sunday and Thursday, you&#039;ll see it under List --&gt; Settings</description>
		<content:encoded><![CDATA[<p>It&#8217;s going live when v4.1 goes live. The upgrade process starts Sunday, and then it&#8217;ll take a few days to go through and upgrade all our users. Sometimes between Sunday and Thursday, you&#8217;ll see it under List &#8211;&gt; Settings</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Karr</title>
		<link>http://www.mailchimp.com/blog/archive-toolbar-for-campaigns/comment-page-1/#comment-3421</link>
		<dc:creator>Douglas Karr</dc:creator>
		<pubDate>Sat, 28 Mar 2009 16:30:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=2812#comment-3421</guid>
		<description>I can&#039;t find this setting anywhere.</description>
		<content:encoded><![CDATA[<p>I can&#8217;t find this setting anywhere.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
