<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" 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:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>We Fix WordPress Blogs</title>
	
	<link>http://www.wefixwp.com</link>
	<description>Get Expert Help Enhancing, Upgrading, and Migrating Your WordPress Blog</description>
	<pubDate>Thu, 09 Jul 2009 20:36:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/WeFixWP" type="application/rss+xml" /><item>
		<title>Just in time … WordPress 2.8.1 arrives</title>
		<link>http://feedproxy.google.com/~r/WeFixWP/~3/Y-rHJI3plyM/</link>
		<comments>http://www.wefixwp.com/just-in-time-wordpress-281-arrives/#comments</comments>
		<pubDate>Thu, 09 Jul 2009 20:36:38 +0000</pubDate>
		<dc:creator>WeFixWP</dc:creator>
		
		<category><![CDATA[We Fix WP]]></category>

		<guid isPermaLink="false">http://www.wefixwp.com/?p=294</guid>
		<description><![CDATA[<p>Today WordPress announced the launch of its latest version: 2.8.1. The WeFixWP team couldn&#8217;t be more happy!</p>
<p>While we have had the pleasure of helping a bunch of new clients who blindly pressed that &#8220;Update to 2.8&#8243; button, many people were&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p>Today WordPress announced the launch of its latest version: 2.8.1. The WeFixWP team couldn&#8217;t be more happy!</p>
<p>While we have had the pleasure of helping a bunch of new clients who blindly pressed that &#8220;Update to 2.8&#8243; button, many people were often caught unaware of what an automatic upgrade can do to production blogs.</p>
<p>We would love to think that bloggers would take the time to back up their existing configuration before taking the plunge, but alas they usually just take that leap of faith.</p>
<p>We applaud Matt Mullengweg and his team to create such an easy to use platform, but we have found that 2.8, in particular, had a lot of issues and conflicts:</p>
<ul>
<li>Blank screens of death</li>
<li>Missing WYSIWYG editors</li>
<li>Conflicting plugins</li>
<li>PHP errors</li>
<li>and more</li>
</ul>
<p>We want to caution everyone to have a plan for &#8220;what if something goes wrong.&#8221;  We recommend learning how to clone your blog and test the updates on a development server before launching live.  Don&#8217;t know how or don&#8217;t want to know how? Get someone to help you before pressing that button.</p>
<p>We look forward to putting 2.8.1 through its paces.  We think this <a href="http://wordpress.org/development/2009/07/wordpress-2-8-1/" target="_blank">latest release</a> will be a &#8220;must install.&#8221;</p>
<img src="http://feeds.feedburner.com/~r/WeFixWP/~4/Y-rHJI3plyM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.wefixwp.com/just-in-time-wordpress-281-arrives/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.wefixwp.com/just-in-time-wordpress-281-arrives/</feedburner:origLink></item>
		<item>
		<title>Our Favorite Plugins: Viper’s Video Quicktags</title>
		<link>http://feedproxy.google.com/~r/WeFixWP/~3/mevbU1VC294/</link>
		<comments>http://www.wefixwp.com/our-favorite-plugins-vipers-video-quicktags/#comments</comments>
		<pubDate>Fri, 15 May 2009 19:27:47 +0000</pubDate>
		<dc:creator>WeFixWP</dc:creator>
		
		<category><![CDATA[We Fix WP]]></category>

		<guid isPermaLink="false">http://www.wefixwp.com/?p=281</guid>
		<description><![CDATA[<p>Want to easy include videos in your posts? Look no further than the robust <a href="http://wordpress.org/extend/plugins/vipers-video-quicktags/" target="_blank">Viper&#8217;s Videos Quicktag plugin</a>.</p>
<h3>How to Use It</h3>
<ul>
<li>Upon successful install, you&#8217;ll find new video icons in the Write panel.</li>
<li> To embed a video, simply click the icon from&#8230;</li></ul>]]></description>
			<content:encoded><![CDATA[<p>Want to easy include videos in your posts? Look no further than the robust <a href="http://wordpress.org/extend/plugins/vipers-video-quicktags/" target="_blank">Viper&#8217;s Videos Quicktag plugin</a>.</p>
<h3>How to Use It</h3>
<ul>
<li>Upon successful install, you&#8217;ll find new video icons in the Write panel.</li>
<li> To embed a video, simply click the icon from the video site you wish to use, then copy and paste the URL that the video is located into the prompt box.  This works in both Visual and HTML modes.</li>
<li>The video will play upon click right inside your post.</li>
</ul>
<h3>Features</h3>
<ul>
<li>You can fully configure how the videos are displayed by adjusting for your blog&#8217;s width, height, colors, alignment, etc.</li>
<li>Supports a wide variety of video sites / filetypes:
<ul>
<li>YouTube (including playlists)</li>
<li> Google Video</li>
<li>DailyMotion</li>
<li>Vimeo</li>
<li>Veoh</li>
<li>Viddler</li>
<li>Metacafe</li>
<li>Blip.tv</li>
<li>Flickr videos</li>
<li>Spike.com/IFILM</li>
<li>MySpaceTV</li>
<li>Flash Video Files (FLV)</li>
<li> QuickTime (MOV, etc.)</li>
<li> Generic video files (AVI, MPEG, WMV, etc.)</li>
</ul>
</li>
</ul>
<h3>Why do we love it?</h3>
<ul>
<li><strong>It&#8217;s easy to use -</strong> just click one of the video icons in the Write screen (rich editor included) and then paste the URL that the video is located at into the prompt box</li>
<li><strong>It&#8217;s well maintained</strong> - The author does a great job keeping it updated and compliant with the latest versions of WordPress.</li>
<li><strong>Works every time</strong> - The plugin never conflicts, always compliant, and every version we&#8217;ve ever used has performed beautifully</li>
</ul>
<img src="http://feeds.feedburner.com/~r/WeFixWP/~4/mevbU1VC294" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.wefixwp.com/our-favorite-plugins-vipers-video-quicktags/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.wefixwp.com/our-favorite-plugins-vipers-video-quicktags/</feedburner:origLink></item>
		<item>
		<title>Display a warning message to IE6 users</title>
		<link>http://feedproxy.google.com/~r/WeFixWP/~3/r2UDe71CeHM/</link>
		<comments>http://www.wefixwp.com/display-a-warning-message-to-ie6-users/#comments</comments>
		<pubDate>Fri, 20 Mar 2009 14:16:10 +0000</pubDate>
		<dc:creator>WeFixWP</dc:creator>
		
		<category><![CDATA[WordPress Tips]]></category>

		<category><![CDATA[ie6]]></category>

		<category><![CDATA[message]]></category>

		<category><![CDATA[warning]]></category>

		<guid isPermaLink="false">http://www.wefixwp.com/?p=162</guid>
		<description><![CDATA[<p>Are you tired of visitors still using the obsolete and buggy IE6? We are. With yesterday&#8217;s launch of Internet Explorer 8, there is little excuse to not upgrading. But for those who insist on using this platform, you can warn&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p>Are you tired of visitors still using the obsolete and buggy IE6? We are. With yesterday&#8217;s launch of Internet Explorer 8, there is little excuse to not upgrading. But for those who insist on using this platform, you can warn them that your site is not (purposely) optimized for their viewing.</p>
<p>Here&#8217;s how to display a message only to IE6 users, asking them to upgrade their prehistoric browser.</p>
<p>The first thing to do is to create a style for our message. To do so, paste the following code in your <strong>style.css</strong> file:</p>
<pre>#ie-message {
background:#C00;
text-align:center;
border-bottom:1px solid #900;
color: #fff;
position:absolute;
top:0;
padding:5px;
width:100%;
}
#ie-message a {
color: #fff;
}</pre>
<p>Once done, open <strong>header.php</strong> and paste this code just after the &lt;body&gt; tag:</p>
<pre>&lt;!--[if lte IE 6]&gt;
   &lt;div id="ie-message"&gt;
      Your browser is obsolete. Please upgrade to &lt;a href="http://www.getfirefox.com" target="_new"&gt;Mozilla Firefox&lt;/a&gt;.
   &lt;/div&gt;
&lt;![endif]--&gt;</pre>
<p>Save the file and you&#8217;re done. Only IE6 users will see that message asking them to upgrade.</p>
<p><img class="alignnone size-full wp-image-253" title="ie6-warning" src="http://www.wefixwp.com/wp-content/uploads/2009/03/ie6-warning.jpg" alt="ie6-warning" width="660" height="415" /></p>
<img src="http://feeds.feedburner.com/~r/WeFixWP/~4/r2UDe71CeHM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.wefixwp.com/display-a-warning-message-to-ie6-users/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.wefixwp.com/display-a-warning-message-to-ie6-users/</feedburner:origLink></item>
		<item>
		<title>Upgrade to WordPress 2.7.1</title>
		<link>http://feedproxy.google.com/~r/WeFixWP/~3/HxyhYWPaPhU/</link>
		<comments>http://www.wefixwp.com/upgrade-to-wordpress-271/#comments</comments>
		<pubDate>Wed, 11 Feb 2009 17:47:24 +0000</pubDate>
		<dc:creator>WeFixWP</dc:creator>
		
		<category><![CDATA[We Fix WP]]></category>

		<guid isPermaLink="false">http://www.wefixwp.com/?p=217</guid>
		<description><![CDATA[<p>Yesterday, WordPress <a href="http://wordpress.org/development/2009/02/wordpress-271/" target="_blank">announced</a> the launch of version 2.7.1.</p>
<p>This is considered a maintenance release, which fixed <a href="http://trac.wordpress.org/query?status=closed&#38;milestone=2.7.1&#38;resolution=fixed&#38;order=priority">68 tickets</a>. Although it’s not a security update, it’s always a good idea to keep your WordPress software up-to-date.</p>
<p>If you are already running 2.7, you can&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p>Yesterday, WordPress <a href="http://wordpress.org/development/2009/02/wordpress-271/" target="_blank">announced</a> the launch of version 2.7.1.</p>
<p>This is considered a maintenance release, which fixed <a href="http://trac.wordpress.org/query?status=closed&amp;milestone=2.7.1&amp;resolution=fixed&amp;order=priority">68 tickets</a>. Although it’s not a security update, it’s always a good idea to keep your WordPress software up-to-date.</p>
<p>If you are already running 2.7, you can update to 2.7.1 via the Tools-&gt;Upgrade menu, or you can <a href="http://wordpress.org/download/">download the package</a> and upgrade manually. (<em><strong>Tip</strong></em>: <em>Perform safe upgrading practices and please backup your database first!</em>)</p>
<p>Not on the 2.7 path? We can assist you in <a href="/help-me-upgrade-my-blog/">updating</a> your WordPress blog quickly and easily.</p>
<img src="http://feeds.feedburner.com/~r/WeFixWP/~4/HxyhYWPaPhU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.wefixwp.com/upgrade-to-wordpress-271/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.wefixwp.com/upgrade-to-wordpress-271/</feedburner:origLink></item>
		<item>
		<title>Create a handwritten signature with a WordPress shortcode</title>
		<link>http://feedproxy.google.com/~r/WeFixWP/~3/y6xNSVmerg0/</link>
		<comments>http://www.wefixwp.com/create-a-handwritten-signature-with-a-wordpress-shortcode/#comments</comments>
		<pubDate>Mon, 09 Feb 2009 16:33:47 +0000</pubDate>
		<dc:creator>WeFixWP</dc:creator>
		
		<category><![CDATA[WordPress Tips]]></category>

		<category><![CDATA[shortcode]]></category>

		<category><![CDATA[signature]]></category>

		<guid isPermaLink="false">http://www.wefixwp.com/?p=156</guid>
		<description><![CDATA[<p>Did you ever want to add a handwritten signature to your posts just like you would when signing a letter? Here&#8217;s a nice code snippet to create a &#8220;signature&#8221; shortcode.</p>
<p>First, you have to get a signature image. To do so,&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p>Did you ever want to add a handwritten signature to your posts just like you would when signing a letter? Here&#8217;s a nice code snippet to create a &#8220;signature&#8221; shortcode.</p>
<p>First, you have to get a signature image. To do so, scan your signature or create one using your favorite photo editor. Once you have it, name it signature.jpg and upload it into your <strong>wp-content/themes/yourtheme/images</strong> directory.</p>
<p>Then, open the <strong>functions.php</strong> file from within your theme. If your theme doesn&#8217;t have that file, just create it. Paste the following code in it:</p>
<pre>function sc_signature() {
   return '&lt;div id="signature"&gt;&lt;/div&gt;';
}
add_shortcode('signature', 'sc_signature');</pre>
<p>Last, define the style for the <strong>#signature id</strong> by adding the following code to your <strong>style.css</strong>:</p>
<pre>#signature {
background:url(images/signature.jpg) no-repeat top left;
width:100px;
height:100px;
}</pre>
<p>Note: You may have to edit the width and height to fit your image size.</p>
<p>Now, when you&#8217;ll want to insert your signature at the end of a post, simply switch WordPress editor to HTML mode and type the following:</p>
<pre>[signature]</pre>
<p>Here it is in action&#8230;<br />
<div id="signature"></div></p>
<img src="http://feeds.feedburner.com/~r/WeFixWP/~4/y6xNSVmerg0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.wefixwp.com/create-a-handwritten-signature-with-a-wordpress-shortcode/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.wefixwp.com/create-a-handwritten-signature-with-a-wordpress-shortcode/</feedburner:origLink></item>
		<item>
		<title>Burned Your Feed at Feedburner? Google is Taking it Over</title>
		<link>http://feedproxy.google.com/~r/WeFixWP/~3/zhFZ7lbun8U/</link>
		<comments>http://www.wefixwp.com/burned-your-feed-at-feedburner-google-is-taking-it-over/#comments</comments>
		<pubDate>Mon, 26 Jan 2009 21:17:04 +0000</pubDate>
		<dc:creator>WeFixWP</dc:creator>
		
		<category><![CDATA[WordPress Tips]]></category>

		<guid isPermaLink="false">http://www.wefixwp.com/?p=145</guid>
		<description><![CDATA[<p><img class="noborder size-full wp-image-146" title="feedburnerflame" src="http://www.wefixwp.com/wp-content/uploads/2009/01/feedburnerflame.gif" alt="" width="179" height="190" align="right" />Google purchased Feedburner (our favorite feed mirror and statistics company) in the summer of 2007, and they now are pushing FeedBurner users to move their accounts under the Google umbrella.</p>
<p>Google has set a deadline for transfering your feeds: February 28,&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p><img class="noborder size-full wp-image-146" title="feedburnerflame" src="http://www.wefixwp.com/wp-content/uploads/2009/01/feedburnerflame.gif" alt="" width="179" height="190" align="right" />Google purchased Feedburner (our favorite feed mirror and statistics company) in the summer of 2007, and they now are pushing FeedBurner users to move their accounts under the Google umbrella.</p>
<p>Google has set a deadline for transfering your feeds: February 28, 2009. Check out this <a href="http://www.problogdesign.com/general-tips/make-the-move-from-feedburner-to-google/" target="_blank">tutorial from Pro Blog Design</a> so you can do it before Google redirects your feed to a very unpleasant 404 error. You also can read more <a href="https://www.google.com/support/feedburner/bin/answer.py?answer=126303" target="_blank">Google FAQs here</a>.</p>
<p>While this is happening, we&#8217;ve noticed some recent performance issues at Feedburner, and unfortunately for Google, they are becoming quite well documented on Twitter.</p>
<p>We have been Feedburner users for a while and were shocked that there has been no emails regarding this switch. We have seen the link on Feedburner, but feel with a major change in service, Google could have been more proactive. Expect some bumps moving forward &#8230;</p>
<img src="http://feeds.feedburner.com/~r/WeFixWP/~4/zhFZ7lbun8U" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.wefixwp.com/burned-your-feed-at-feedburner-google-is-taking-it-over/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.wefixwp.com/burned-your-feed-at-feedburner-google-is-taking-it-over/</feedburner:origLink></item>
		<item>
		<title>Meet the WeFixWP Team at SXSW Interactive</title>
		<link>http://feedproxy.google.com/~r/WeFixWP/~3/MpeVa9Dru_E/</link>
		<comments>http://www.wefixwp.com/meet-the-wefixwp-team-at-sxsw-interactive/#comments</comments>
		<pubDate>Fri, 16 Jan 2009 16:29:28 +0000</pubDate>
		<dc:creator>WeFixWP</dc:creator>
		
		<category><![CDATA[We Fix WP]]></category>

		<guid isPermaLink="false">http://www.wefixwp.com/?p=139</guid>
		<description><![CDATA[<p><a href="http://sxsw.com" target="_blank"><img class="size-medium wp-image-140" title="sxsw09" src="http://www.wefixwp.com/wp-content/uploads/2009/01/sxsw09.gif" alt="" width="140" height="100" align="right"/></a>Our travel plans are complete - WeFixWP will be at this year&#8217;s SXSW! This conference:</p>
<blockquote><p>&#8230; celebrates the creativity and passion behind the coolest new media technologies. In addition to panel sessions that cover everything from web design to bootstrapping to&#8230;</p></blockquote>]]></description>
			<content:encoded><![CDATA[<p><a href="http://sxsw.com" target="_blank"><img class="size-medium wp-image-140" title="sxsw09" src="http://www.wefixwp.com/wp-content/uploads/2009/01/sxsw09.gif" alt="" width="140" height="100" align="right"/></a>Our travel plans are complete - WeFixWP will be at this year&#8217;s SXSW! This conference:</p>
<blockquote><p>&#8230; celebrates the creativity and passion behind the coolest new media technologies. In addition to panel sessions that cover everything from web design to bootstrapping to social networks, attendees make new business connections at the three-day Trade Show &amp; Exhibition &#8230;</p></blockquote>
<p>We hope to meet you there!</p>
<img src="http://feeds.feedburner.com/~r/WeFixWP/~4/MpeVa9Dru_E" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.wefixwp.com/meet-the-wefixwp-team-at-sxsw-interactive/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.wefixwp.com/meet-the-wefixwp-team-at-sxsw-interactive/</feedburner:origLink></item>
		<item>
		<title>Happy Holidays from WeFixWP!</title>
		<link>http://feedproxy.google.com/~r/WeFixWP/~3/E4o34w4RgsY/</link>
		<comments>http://www.wefixwp.com/happy-holidays-from-wefixwp/#comments</comments>
		<pubDate>Tue, 23 Dec 2008 20:09:22 +0000</pubDate>
		<dc:creator>WeFixWP</dc:creator>
		
		<category><![CDATA[We Fix WP]]></category>

		<category><![CDATA[Christmas 2009]]></category>

		<category><![CDATA[Happy Holidays]]></category>

		<guid isPermaLink="false">http://www.wefixwp.com/?p=134</guid>
		<description><![CDATA[<p><img class="noborder aligncenter size-full wp-image-135" title="WeFixWP Christmas 2008" src="http://www.wefixwp.com/wp-content/uploads/2008/12/cr-xmas08.jpg" alt="" width="500" height="664" /></p>
<p>We would like to send out some special holiday cheer to all our wonderful clients, partners, and friends. We are so thankful to have such a great network of people who we enjoy working with!</p>
<p>May 2009 be filled with tons&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p><img class="noborder aligncenter size-full wp-image-135" title="WeFixWP Christmas 2008" src="http://www.wefixwp.com/wp-content/uploads/2008/12/cr-xmas08.jpg" alt="" width="500" height="664" /></p>
<p>We would like to send out some special holiday cheer to all our wonderful clients, partners, and friends. We are so thankful to have such a great network of people who we enjoy working with!</p>
<p>May 2009 be filled with tons of inspirational blog posts, huge traffic influxes and more twitter followers then you could ever dream of…</p>
<p>Cheers! Dana &amp; Karen</p>
<img src="http://feeds.feedburner.com/~r/WeFixWP/~4/E4o34w4RgsY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.wefixwp.com/happy-holidays-from-wefixwp/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.wefixwp.com/happy-holidays-from-wefixwp/</feedburner:origLink></item>
		<item>
		<title>WordPress 2.7 and Auto Updates</title>
		<link>http://feedproxy.google.com/~r/WeFixWP/~3/KZTqfeFsQDY/</link>
		<comments>http://www.wefixwp.com/wordpress-27-and-auto-updates/#comments</comments>
		<pubDate>Thu, 11 Dec 2008 16:09:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[We Fix WP]]></category>

		<guid isPermaLink="false">http://www.wefixwp.com/?p=127</guid>
		<description><![CDATA[<p><a href="http://wordpress.org/development/2008/12/coltrane/" target="_blank">WordPress 2.7</a> or &#8220;Coltrane&#8221; was released last night. Here are some of the features you can look forward to:</p>
<ol>
<li>A new interface that allows you to do things faster with fewer clicks.</li>
<li>A drag-and-drop dashboard that allows you to arrange the things that&#8230;</li></ol>]]></description>
			<content:encoded><![CDATA[<p><a href="http://wordpress.org/development/2008/12/coltrane/" target="_blank">WordPress 2.7</a> or &#8220;Coltrane&#8221; was released last night. Here are some of the features you can look forward to:</p>
<ol>
<li>A new interface that allows you to do things faster with fewer clicks.</li>
<li>A drag-and-drop dashboard that allows you to arrange the things that are most important to you (actually everything is pretty customizable now).</li>
<li>Install any plugin from WordPress.org with a single click.</li>
<li>Automatic, built-in upgrades for new releases with a single click.</li>
</ol>
<p>The WeFixWP team wants everyone to take special notice of feature #4. We want to caution those of you out there with custom themes and/or those of you who have lots of plugins - it still may not be as easy as you think.</p>
<p>While WordPress is making a great effort to offer the ability for all to upgrade future releases with one click, it&#8217;s still important to remember (as with all software) things can go wrong.</p>
<p>Please backup your blog&#8217;s database and turn off all your plugins before pressing that button. Also, take the time to ensure that your theme as well as all your plugins are compatible with the newest release.</p>
<p>We&#8217;ve already read tweets from those who have plunged into the upgrade and came out with a broken blog and without a rollback. Diligence will still be important moving forward.</p>
<p>That said, we are still excited because this upgrade looks rather nice - good luck out there!</p>
<img src="http://feeds.feedburner.com/~r/WeFixWP/~4/KZTqfeFsQDY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.wefixwp.com/wordpress-27-and-auto-updates/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.wefixwp.com/wordpress-27-and-auto-updates/</feedburner:origLink></item>
		<item>
		<title>What Happened to My Blog’s Sidebars in IE?</title>
		<link>http://feedproxy.google.com/~r/WeFixWP/~3/78n2oyuXVr8/</link>
		<comments>http://www.wefixwp.com/what-happened-to-my-blogs-sidebars-in-ie/#comments</comments>
		<pubDate>Thu, 11 Dec 2008 15:38:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[We Fix WP]]></category>

		<guid isPermaLink="false">http://www.wefixwp.com/?p=122</guid>
		<description><![CDATA[<p>The WeFixWP team has been fielding a lot of questions this week about missing sidebars when viewing the blog in Internet Explorer.</p>
<p>If your blog looked OK one day and a mess the next, the fix can be actually pretty simple.&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p>The WeFixWP team has been fielding a lot of questions this week about missing sidebars when viewing the blog in Internet Explorer.</p>
<p>If your blog looked OK one day and a mess the next, the fix can be actually pretty simple. Here&#8217;s what check for first:</p>
<ol>
<li>Review some of your recent posts by Manage &gt; Posts &gt; Edit</li>
<li>Click over to the HTML tab</li>
<li>Look for some rogue code, often you&#8217;ll find an unneeded &lt;div&gt; tag or another HTML tag that was not closed properly.</li>
<li>Delete the code and press the Save button.</li>
<li>Your sidebars should now be back in IE.</li>
</ol>
<p>How to prevent this? Be careful when cutting and pasting content from Word documents and other websites / blogs because they often have HTML formatting that gets entered into your site and causing havoc.</p>
<p>Take advantage of the Kitchen Sink icon (see image below) to reveal more editing features. Then either use the Paste as Plain Text (T) or Paste from Word (W) icons to clean up any formatting brought over. When pasting from Word, we often click on the HTML tab and remove all extraneous formatting code that is often found toward the top of the post editor.</p>
<p><img class="aligncenter size-full wp-image-123" title="kitchensink" src="http://www.wefixwp.com/wp-content/uploads/2008/12/kitchensink.gif" alt="" width="500" height="123" /></p>
<p>If that doesn&#8217;t bring back the toolbars, you may have a theme problem - but it&#8217;s a good place to start.</p>
<img src="http://feeds.feedburner.com/~r/WeFixWP/~4/78n2oyuXVr8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://www.wefixwp.com/what-happened-to-my-blogs-sidebars-in-ie/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.wefixwp.com/what-happened-to-my-blogs-sidebars-in-ie/</feedburner:origLink></item>
	</channel>
</rss>
