<?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:slash="http://purl.org/rss/1.0/modules/slash/" version="2.0">

<channel>
	<title>Real Estate Blog Lab</title>
	
	<link>http://www.realestatebloglab.com</link>
	<description>A Laboratory For Real Estate Blogging</description>
	<lastBuildDate>Wed, 28 Jul 2010 19:22:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</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" type="application/rss+xml" href="http://feeds.feedburner.com/RealEstateBlogLab" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="realestatebloglab" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">RealEstateBlogLab</feedburner:emailServiceId><feedburner:feedburnerHostname xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>CSS3 for IE</title>
		<link>http://www.realestatebloglab.com/real-estate-blogging/css3-for-ie/</link>
		<comments>http://www.realestatebloglab.com/real-estate-blogging/css3-for-ie/#comments</comments>
		<pubDate>Wed, 28 Jul 2010 19:22:23 +0000</pubDate>
		<dc:creator>Dave Smith</dc:creator>
				<category><![CDATA[Real Estate Blogging]]></category>
		<category><![CDATA[CSS3 for IE]]></category>
		<category><![CDATA[CSS3 PIE]]></category>

		<guid isPermaLink="false">http://www.realestatebloglab.com/?p=813</guid>
		<description><![CDATA[Now you can have your CSS3 styles in IE too.<p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/real-estate-blogging/css3-for-ie/">CSS3 for IE</a> </h3>

</p>
]]></description>
			<content:encoded><![CDATA[<div class='embaArticle' style='display:inline'><p>There&#8217;s a project out there called PIE.  It is in beta.  I tested version 1 yesterday.  Version 2 is out today.  I&#8217;ll take it for a spin soon.  I have no idea what version will be up by the time you read this post.  But I do know they post the latest at the top and date the files, nice.</p>
<p>It took me a couple of hours to figure out all the pieces.  There were bits of information spread all over the place.  Too many assumptions that we would all just &#8220;know&#8221; certain things.</p>
<p>I&#8217;ve removed the assumptions and will show you exactly how to get CSS3 functionality pushed to IE browsers from your blog.  Making it &#8220;pretty&#8221; for IE is now possible.</p>
<p>(When I wrote yesterday&#8217;s post <a title="css3 is here now" href="http://www.realestatebloglab.com/real-estate-blogging/css3-is-here-now/">CSS3 Is Here Now</a> I hadn&#8217;t found this yet)</p>
<h3>CSS3 PIE</h3>
<p>The first thing you want to do is download the files you will need.  <a title="PIE for IE" href="http://github.com/lojjic/PIE/downloads">PIE for IE</a></p>
<p>You will find three files inside the zip file.</p>
<p>PIE.htc<br />
PIE.php<br />
PIE_uncompressed.htc</p>
<p>PIE.htc is probably the only one you will need.  But if after doing all the instructions here it still doesn&#8217;t show up change the behavior line to PIE.php</p>
<p>Upload these three files to your current theme directory.  Ex.  If you are using TwentyTen, upload them to wp-content/themes/twentyten/</p>
<p>Second, Where you have added the CSS3 styles you will need to add:</p>
<p>behavior: url(/wp-content/themes/yourthemedirectory/PIE.htc);<br />
Followed by the CSS3 style WITHOUT THE -moz- in front of it.<br />
Using yesterdays example that will look like this:</p>
<p>#calloutbox {<br />
behavior: url(/wp-content/themes/yourthemedirectory/PIE.htc);<br />
border-radius:10px 10px 10px 10px;<br />
box-shadow:3px 3px 7px #333333;<br />
-moz-border-radius:10px 10px 10px 10px;<br />
-moz-box-shadow:3px 3px 7px #333333;<br />
}</p>
<p>Do this where ever you have inserted CSS3 styles in your style.css file.</p>
<p>Final note.  Don&#8217;t forget to put the leading &#8220;/&#8221;  before the wp-content/ etc.  If you do the styles will show up on the home page only.  This was part of the digging out all the details.</p>
<p>Now you can have the same rounded corners and drop shadows in IE.</p>
<p>Not all CSS3 commands are supported with PIE (yet)  but the basic ones you want to dress up your site are supported and easy to implement.</p>
<p>Now you can have your CSS3 styles in IE too.</p>
</div><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.realestatebloglab.com%2Freal-estate-blogging%2Fcss3-for-ie%2F&amp;layout=standard&amp;show-faces=true&amp;width=500&amp;action=like&amp;colorscheme=light" scrolling="no" frameborder="0″ allowTransparency="true" style="border:none; overflow:hidden; width:500px; height:60px"></iframe><p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/real-estate-blogging/css3-for-ie/">CSS3 for IE</a> </h3>

</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=W_eVi0Hqfow:NkWtB4uwfME:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=W_eVi0Hqfow:NkWtB4uwfME:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=W_eVi0Hqfow:NkWtB4uwfME:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=W_eVi0Hqfow:NkWtB4uwfME:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=W_eVi0Hqfow:NkWtB4uwfME:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=W_eVi0Hqfow:NkWtB4uwfME:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=W_eVi0Hqfow:NkWtB4uwfME:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=W_eVi0Hqfow:NkWtB4uwfME:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=W_eVi0Hqfow:NkWtB4uwfME:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=W_eVi0Hqfow:NkWtB4uwfME:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://www.realestatebloglab.com/real-estate-blogging/css3-for-ie/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CSS3 Is Here Now</title>
		<link>http://www.realestatebloglab.com/real-estate-blogging/css3-is-here-now/</link>
		<comments>http://www.realestatebloglab.com/real-estate-blogging/css3-is-here-now/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 16:46:10 +0000</pubDate>
		<dc:creator>Dave Smith</dc:creator>
				<category><![CDATA[Real Estate Blogging]]></category>
		<category><![CDATA[CSS3]]></category>
		<category><![CDATA[Drop shadows]]></category>
		<category><![CDATA[Rounded Corners]]></category>

		<guid isPermaLink="false">http://www.realestatebloglab.com/?p=766</guid>
		<description><![CDATA[<a href=http://www.realestatebloglab.com/real-estate-blogging/css3-is-here-now/><img src=http://www.realestatebloglab.com/wp-content/uploads/2010/07/FrankAl-Curves-150x150.jpg class=imgtfe hspace=5 align=left width=100  border=0></a>The formatting and "Eye Candy" ability with CSS3 is pretty amazing.<p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/real-estate-blogging/css3-is-here-now/">CSS3 Is Here Now</a> </h3>

</p>
]]></description>
			<content:encoded><![CDATA[<div class='embaArticle' style='display:inline'><h3>
<div id="attachment_812" class="wp-caption alignright" style="width: 352px"><a href="http://www.realestatebloglab.com/wp-content/uploads/2010/07/FrankAl-Curves.jpg"><img class="size-full wp-image-812 " title="Frank&amp;Al-Curves" src="http://www.realestatebloglab.com/wp-content/uploads/2010/07/FrankAl-Curves.jpg" alt="talking trash cans" width="342" height="233" /></a><p class="wp-caption-text">LOL, Good One Frank</p></div>
<p>Why Wait to Use it?</h3>
<p>I&#8217;ve started using some CSS3 styling here at the lab and on another site I&#8217;m currently developing.  I love it.  The formatting and &#8220;Eye Candy&#8221; ability with CSS3 is pretty amazing.  It used to be if you wanted rounded corners or drop shadows you had to create them as images and call them to be displayed.  Now you can add a couple lines of code and do both on the fly.  Want more curve, change a number, want a deeper shadow, change a number; it is that easy.</p>
<p>I&#8217;ll show you two examples in this post and provide the CSS3 behind the effect.  NOTE:  YOU WILL NOT SEE ANYTHING DIFFERENT IN IE.</p>
<p>You do have to have a &#8220;modern&#8221; full featured browser like Chrome, Firefox, Flock, or Safari (but safari requires it&#8217;s own code) in order to view CSS3.</p>
<p>Remember the post on <a title="add a call out box" href="http://www.realestatebloglab.com/real-estate-blogging/add-a-call-out-box-to-your-posts/">add a callout box</a> to your post?  I&#8217;ve added a little CSS3 styling to dress them up even more.  Below is a box and styling code.</p>
<hr />
<div id="calloutbox">
<h3>This box has CSS3 Styles Added</h3>
<ul>
<li>CSS3 is easy to add</li>
<li>Add a drop shadow</li>
<li>Or Rounded corners</li>
<li>Even a gradient background</li>
</ul>
</div>
<div>
<div>
<div>#calloutbox {</div>
<div>
<div>
<div><strong>-moz-border-radius:10px 10px 10px 10px;</strong></div>
<div><strong>-moz-box-shadow:3px 3px 7px #333333;</strong></div>
<div><strong>background-image:-moz-repeating-linear-gradient(75% 75% 99deg, #EDEDED, #FFFFFF, #EDEDED 55%);</strong></div>
<div>border:4px solid #990000;</div>
<div>float:right;</div>
<div>font-size:16px;</div>
<div>margin:1px 10px 10px;</div>
<div>padding:7px 10px 10px;</div>
</div>
</div>
<div>}</div>
<p>Can you spot what I put in this code segment that isn&#8217;t actually what is being displayed?</p>
<h3>Using CSS3 For your Theme</h3>
<p>I like it on the call out box, but I really like using CSS3 on the theme elements themselves.</p>
<p>My site <a title="Tucson Tired" href="http://www.tucsontired.com">Tucson Tired</a>, uses quite a bit of CSS3 styling for the theme layout.  All those rounded corners and drop shadows are CSS3.</p>
<p>Of course you have to be using Firefox or Chrome to see it.</p>
<p>Want to really appreciate the difference?  Open it in IE and in FF and compare.</p>
<p>There are plenty of CSS3 tutorials and sytax sites out there for you to find the code to create many more effects than the ones mentioned here.</p>
<p>This is just an introduction.  Have some fun.  Apply some CSS three to your styles and really add some &#8220;<em>Style</em>&#8220;.</p>
</div>
</div>
</div><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.realestatebloglab.com%2Freal-estate-blogging%2Fcss3-is-here-now%2F&amp;layout=standard&amp;show-faces=true&amp;width=500&amp;action=like&amp;colorscheme=light" scrolling="no" frameborder="0″ allowTransparency="true" style="border:none; overflow:hidden; width:500px; height:60px"></iframe><p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/real-estate-blogging/css3-is-here-now/">CSS3 Is Here Now</a> </h3>

</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=B20Jie756Po:9TzgawEquuQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=B20Jie756Po:9TzgawEquuQ:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=B20Jie756Po:9TzgawEquuQ:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=B20Jie756Po:9TzgawEquuQ:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=B20Jie756Po:9TzgawEquuQ:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=B20Jie756Po:9TzgawEquuQ:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=B20Jie756Po:9TzgawEquuQ:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=B20Jie756Po:9TzgawEquuQ:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=B20Jie756Po:9TzgawEquuQ:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=B20Jie756Po:9TzgawEquuQ:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://www.realestatebloglab.com/real-estate-blogging/css3-is-here-now/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Twenty Ten 1.0 And All-In-One SEO Post Title Issue</title>
		<link>http://www.realestatebloglab.com/twentyten/twenty-ten-1-0-and-all-in-one-seo-post-title-issue/</link>
		<comments>http://www.realestatebloglab.com/twentyten/twenty-ten-1-0-and-all-in-one-seo-post-title-issue/#comments</comments>
		<pubDate>Sun, 25 Jul 2010 12:28:59 +0000</pubDate>
		<dc:creator>Dave Smith</dc:creator>
				<category><![CDATA[TwentyTen]]></category>
		<category><![CDATA[Post Title Issue]]></category>
		<category><![CDATA[Twenty Ten 1.0]]></category>

		<guid isPermaLink="false">http://www.realestatebloglab.com/?p=810</guid>
		<description><![CDATA[If you don't want your Title Tags looking screwed up and messing with your SEO then upgrade Twenty Ten to 1.1 or uncheck "Rewrite Titles" on the All-in-One options page.<p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/twentyten/twenty-ten-1-0-and-all-in-one-seo-post-title-issue/">Twenty Ten 1.0 And All-In-One SEO Post Title Issue</a> </h3>

</p>
]]></description>
			<content:encoded><![CDATA[<div class='embaArticle' style='display:inline'><p>I noticed something strange when I installed the All-In-One SEO Pack on my new Twenty Ten installs.  There was an issue with the post title being displayed.</p>
<p>It would put the post title and the blog title together then repeat the blog title.  Causing the last word of the post title to be right up against the first blog title.</p>
<p>Ex.<br />
<strong>Upgrades6105 N Samantha Grove | 6105 N Samantha Grove</strong></p>
<p>It should read:</p>
<p><strong>Upgrades | 6105 N Samantha Grove</strong></p>
<p>I thought the issue was with All-In-One-SEO.  It turns out it is with Twenty Ten.</p>
<h3>Twenty Ten 1.0 solutions</h3>
<p>If you are using Twenty Ten 1.0 and All-In-One-SEO Pack go into the settings for All-In-One and uncheck &#8220;Rewrite Titles&#8221;</p>
<h3>Twenty Ten 1.1 header rewrite</h3>
<p>There is no issue with 1.1.  The theme header file was rewritten to comply with a standard used by most <acronym title='WordPress'>WP</acronym> Themes.</p>
<p>From Nacin on the upgrade:</p>
<blockquote><p>The only real change is that I removed the half-baked code using the  wp_title hook in order to customize the page title, and instead the code  was moved back into header.php and simplified a little.</p>
<p>I can call it half-baked because I was the one who wrote it. <strong>It interfered with some plugins</strong> and so we yanked it.</p></blockquote>
<p>It seems All-In-One is &#8220;some plugins&#8221; in this case, and probably others that rewrite post titles.</p>
<p>This is your heads up Lab Rats.  If you don&#8217;t want your Title Tags looking screwed up and messing with  your SEO then upgrade Twenty Ten to 1.1 or uncheck &#8220;Rewrite Titles&#8221; on  the All-in-One options page.</p>
</div><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.realestatebloglab.com%2Ftwentyten%2Ftwenty-ten-1-0-and-all-in-one-seo-post-title-issue%2F&amp;layout=standard&amp;show-faces=true&amp;width=500&amp;action=like&amp;colorscheme=light" scrolling="no" frameborder="0″ allowTransparency="true" style="border:none; overflow:hidden; width:500px; height:60px"></iframe><p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/twentyten/twenty-ten-1-0-and-all-in-one-seo-post-title-issue/">Twenty Ten 1.0 And All-In-One SEO Post Title Issue</a> </h3>

</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=ZaVl29vSK48:D_wJZtLZgVI:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=ZaVl29vSK48:D_wJZtLZgVI:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=ZaVl29vSK48:D_wJZtLZgVI:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=ZaVl29vSK48:D_wJZtLZgVI:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=ZaVl29vSK48:D_wJZtLZgVI:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=ZaVl29vSK48:D_wJZtLZgVI:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=ZaVl29vSK48:D_wJZtLZgVI:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=ZaVl29vSK48:D_wJZtLZgVI:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=ZaVl29vSK48:D_wJZtLZgVI:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=ZaVl29vSK48:D_wJZtLZgVI:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://www.realestatebloglab.com/twentyten/twenty-ten-1-0-and-all-in-one-seo-post-title-issue/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Modifying Twenty Ten CSS</title>
		<link>http://www.realestatebloglab.com/twentyten/modifying-twenty-ten-css/</link>
		<comments>http://www.realestatebloglab.com/twentyten/modifying-twenty-ten-css/#comments</comments>
		<pubDate>Sun, 25 Jul 2010 11:19:18 +0000</pubDate>
		<dc:creator>Dave Smith</dc:creator>
				<category><![CDATA[TwentyTen]]></category>
		<category><![CDATA[Twenty Ten CSS Tweaks]]></category>

		<guid isPermaLink="false">http://www.realestatebloglab.com/?p=807</guid>
		<description><![CDATA[Typically when adding your own structures to a CSS file you put them at the end of the file.<p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/twentyten/modifying-twenty-ten-css/">Modifying Twenty Ten CSS</a> </h3>

</p>
]]></description>
			<content:encoded><![CDATA[<div class='embaArticle' style='display:inline'><p>Typically when adding your own structures to a CSS file you put them at the end of the file.  They are easier to find down there and know where the original code ends and your additions/modifications begin.</p>
<h3>Twenty Ten CSS will throw you a loop</h3>
<p>I started making changes that way, but none of my changes were showing up.  Turns out the Devs at <acronym title='WordPress'>WP</acronym> put some Mobile Browser and Print Styling at the bottom of the style.css</p>
<p>/* =Mobile Safari ( iPad, iPhone and iPod Touch )<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211; */</p>
<p>Further down you will find:</p>
<p>/* =Print Style<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211; */</p>
<p>The best thing to do is go right above the Mobile Safari remarks and put your additions/modifications there.</p>
<p>Granted, sometimes you have to have put them higher in the code.  For those occasions, especially deletions I often will remark out the original code and place the new code directly below it.</p>
</div><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.realestatebloglab.com%2Ftwentyten%2Fmodifying-twenty-ten-css%2F&amp;layout=standard&amp;show-faces=true&amp;width=500&amp;action=like&amp;colorscheme=light" scrolling="no" frameborder="0″ allowTransparency="true" style="border:none; overflow:hidden; width:500px; height:60px"></iframe><p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/twentyten/modifying-twenty-ten-css/">Modifying Twenty Ten CSS</a> </h3>

</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=OqVkFZ9VXps:focApy-TYxQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=OqVkFZ9VXps:focApy-TYxQ:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=OqVkFZ9VXps:focApy-TYxQ:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=OqVkFZ9VXps:focApy-TYxQ:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=OqVkFZ9VXps:focApy-TYxQ:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=OqVkFZ9VXps:focApy-TYxQ:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=OqVkFZ9VXps:focApy-TYxQ:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=OqVkFZ9VXps:focApy-TYxQ:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=OqVkFZ9VXps:focApy-TYxQ:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=OqVkFZ9VXps:focApy-TYxQ:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://www.realestatebloglab.com/twentyten/modifying-twenty-ten-css/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Twenty Ten 1.1 Released</title>
		<link>http://www.realestatebloglab.com/twentyten/twenty-ten-1-1-released/</link>
		<comments>http://www.realestatebloglab.com/twentyten/twenty-ten-1-1-released/#comments</comments>
		<pubDate>Sun, 25 Jul 2010 00:48:03 +0000</pubDate>
		<dc:creator>Dave Smith</dc:creator>
				<category><![CDATA[TwentyTen]]></category>
		<category><![CDATA[Twenty Ten 1.1]]></category>
		<category><![CDATA[Wordpress Default theme update]]></category>

		<guid isPermaLink="false">http://www.realestatebloglab.com/?p=806</guid>
		<description><![CDATA[If you have already started making modifications to your copy of Twenty Ten you should backup the theme files and then install the latest version.<p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/twentyten/twenty-ten-1-1-released/">Twenty Ten 1.1 Released</a> </h3>

</p>
]]></description>
			<content:encoded><![CDATA[<div class='embaArticle' style='display:inline'><p>If you have already started making modifications to your copy of Twenty Ten you should backup the theme files and then install the latest version.</p>
<h3>Footer Tracking Codes</h3>
<p>Don&#8217;t forget if you have already inserted Tracking codes for Woopra, Google Analytics, Hittail, etc. you will need to put these back in the new footer.php.</p>
<p>Once it is installed you can add back the modifications you made to the CSS.  I know this is a pain.  But they have made alphabetical changes to the layout of the CSS which you will want to have on your existing site.</p>
<p>It is never easy having to look in two different places for code because of a version change.  So before you start making changes get version 1.1 of Twenty Ten on your site.</p>
</div><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.realestatebloglab.com%2Ftwentyten%2Ftwenty-ten-1-1-released%2F&amp;layout=standard&amp;show-faces=true&amp;width=500&amp;action=like&amp;colorscheme=light" scrolling="no" frameborder="0″ allowTransparency="true" style="border:none; overflow:hidden; width:500px; height:60px"></iframe><p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/twentyten/twenty-ten-1-1-released/">Twenty Ten 1.1 Released</a> </h3>

</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=h9_c3FJYi6I:Qkmd7vzJRYA:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=h9_c3FJYi6I:Qkmd7vzJRYA:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=h9_c3FJYi6I:Qkmd7vzJRYA:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=h9_c3FJYi6I:Qkmd7vzJRYA:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=h9_c3FJYi6I:Qkmd7vzJRYA:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=h9_c3FJYi6I:Qkmd7vzJRYA:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=h9_c3FJYi6I:Qkmd7vzJRYA:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=h9_c3FJYi6I:Qkmd7vzJRYA:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=h9_c3FJYi6I:Qkmd7vzJRYA:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=h9_c3FJYi6I:Qkmd7vzJRYA:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://www.realestatebloglab.com/twentyten/twenty-ten-1-1-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Site Title and Site Description</title>
		<link>http://www.realestatebloglab.com/twentyten/site-title-and-site-description/</link>
		<comments>http://www.realestatebloglab.com/twentyten/site-title-and-site-description/#comments</comments>
		<pubDate>Sat, 24 Jul 2010 16:21:50 +0000</pubDate>
		<dc:creator>Dave Smith</dc:creator>
				<category><![CDATA[TwentyTen]]></category>
		<category><![CDATA[Site Description]]></category>
		<category><![CDATA[Site Title]]></category>

		<guid isPermaLink="false">http://www.realestatebloglab.com/?p=804</guid>
		<description><![CDATA[Twenty Ten allows for a long title and a short description. But what if your site is the other way around. You have a short title but want a long description.<p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/twentyten/site-title-and-site-description/">Site Title and Site Description</a> </h3>

</p>
]]></description>
			<content:encoded><![CDATA[<div class='embaArticle' style='display:inline'><p>Twenty Ten allows for a long title and a short description.  But what if your site is the other way around.  You have a short title but want a long description.</p>
<p>You don&#8217;t have to change your description to fit the allotted 220 pixels.  Here is where you can change both.</p>
<h3>Site Title</h3>
<p>#site-title {<br />
float:left;<br />
font-size:30px;<br />
line-height:36px;<br />
margin:0 0 18px;<br />
width:700px;<br />
}</p>
<p>Change the width to what will allow your title to display on a single line.  If you only need 200px for your title set it to:<br />
width: 200px;<br />
That will buy you 500 pixels to exchange for use with the site description.</p>
<h3>Site Description</h3>
<p>#site-description {<br />
clear:right;<br />
float:right;<br />
font-style:italic;<br />
margin:14px 0 18px;<br />
width:220px;<br />
}</p>
<p>The default setting is 220px for the description width.  I can easily change this to 700 or 720px and use a longer description.</p>
<p>What about the size of the description font?</p>
<p>It is kind of small and being italic it isn&#8217;t easy for readers with let&#8217;s say &#8220;older eyes&#8221; to read it.  There isn&#8217;t any font size declared in the site description.  This means there is a default size that it is using.  How do you make it bigger?</p>
<p>This is easy.  Add the following:<br />
<strong>font-size: 16px</strong></p>
<p>Or whatever size you want.  16px is simply an example.</p>
<p>Be sure to do it inside the closing bracket for the site description.  It would now look like this:</p>
<p>#site-description {<br />
font-size: 16px;<br />
clear:right;<br />
float:right;<br />
font-style:italic;<br />
margin:14px 0 18px;<br />
width:720px;<br />
}</p>
<p>If you don&#8217;t like the italic simply remove the font-style:italic;  or if you want to keep it in the code change it to <strong>font-style:normal;</strong></p>
<p>Now you have a custom Site Title and Site Description for your blog.</p>
</div><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.realestatebloglab.com%2Ftwentyten%2Fsite-title-and-site-description%2F&amp;layout=standard&amp;show-faces=true&amp;width=500&amp;action=like&amp;colorscheme=light" scrolling="no" frameborder="0″ allowTransparency="true" style="border:none; overflow:hidden; width:500px; height:60px"></iframe><p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/twentyten/site-title-and-site-description/">Site Title and Site Description</a> </h3>

</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=nIq2NVFR9xM:enL63I0hWdU:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=nIq2NVFR9xM:enL63I0hWdU:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=nIq2NVFR9xM:enL63I0hWdU:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=nIq2NVFR9xM:enL63I0hWdU:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=nIq2NVFR9xM:enL63I0hWdU:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=nIq2NVFR9xM:enL63I0hWdU:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=nIq2NVFR9xM:enL63I0hWdU:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=nIq2NVFR9xM:enL63I0hWdU:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=nIq2NVFR9xM:enL63I0hWdU:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=nIq2NVFR9xM:enL63I0hWdU:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://www.realestatebloglab.com/twentyten/site-title-and-site-description/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Twenty Ten the New Default Theme</title>
		<link>http://www.realestatebloglab.com/twentyten/twenty-ten-the-new-default-theme/</link>
		<comments>http://www.realestatebloglab.com/twentyten/twenty-ten-the-new-default-theme/#comments</comments>
		<pubDate>Fri, 23 Jul 2010 18:28:35 +0000</pubDate>
		<dc:creator>Dave Smith</dc:creator>
				<category><![CDATA[TwentyTen]]></category>
		<category><![CDATA[Twenty Ten CSS Tweaks]]></category>
		<category><![CDATA[Twenty Ten Theme]]></category>

		<guid isPermaLink="false">http://www.realestatebloglab.com/?p=802</guid>
		<description><![CDATA[I've decided to start a new category dedicated to Twenty Ten Theme and modifications that can be made to it quickly and easily.<p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/twentyten/twenty-ten-the-new-default-theme/">Twenty Ten the New Default Theme</a> </h3>

</p>
]]></description>
			<content:encoded><![CDATA[<div class='embaArticle' style='display:inline'><h3>TwentyTen the Category</h3>
<p>Twenty Ten is the new default theme for WordPress as of release 3.0 .  I&#8217;ve been setting up sites using it for a couple of months now.  It is a great theme and there is a lot you can do with it.  I tweak it a lot.  Therefore, I&#8217;ve decided to start a new category dedicated to Twenty Ten Theme and modifications that can be made to it quickly and easily.</p>
<p>Some quick changes can make it look completely different.  The new header area and background layout area provide a great playground for variation in theme.</p>
<p>The <acronym title='WordPress'>WP</acronym> team recommends any changes be made to a child theme and not the default.  I know one reason why and you need to be aware of this.</p>
<p>Every time you update <acronym title='WordPress'>WP</acronym> the Twenty Ten Theme is replaced as well.  Any custom CSS you put in the default them is wiped out.  Same is true for any changes you made to the code in the various parts of the theme.  So Be advised YOU NEED TO BACKUP TWENTY TEN EVERY TIME THERE IS AN UPDATE!!  especially if you have made modifications.</p>
<p>I don&#8217;t like working with child themes.  Maybe someday, but I&#8217;ve had a little experience with them and find it very labor intensive to make changes.  I like firebug on one tab and the CSS editor in another.  Make a change and update.  Maybe I&#8217;m missing something.  But for now I edit the default theme itself.</p>
<h3>Short, short posts</h3>
<p>Some of these post are going to be very short.  Most of what I&#8217;ll cover are tweaks in the CSS that will make a difference in the appearance of the theme.  They will all be filed under TwentyTen.</p>
<p>Some will be a little longer.  It takes more than a few words to describe how to change the header image size and width.  Or change the layout to make the sidebar or content areas bigger.</p>
<p>If you are looking for ways to tweak Twenty Ten come here.</p>
<p>If you don&#8217;t find what you are looking for leave a comment, I&#8217;ll see what I can do and write a post on the tweak.</p>
<h3>Example Post</h3>
<hr />
<h3>Clear Both for Header Tags</h3>
<p>You will find this statement in the CSS.</p>
<p>h1, h2, h3, h4, h5, h6 {<br />
font-weight: normal;<br />
clear: both;<br />
}</p>
<p>The clear both will make it impossible to display an image beside an h3 tag in your post.</p>
<h3>The simple solution.</h3>
<p>There is typically no reason to clear both on any header tag below an h2 tag.  Therefore change this to:</p>
<p>h1, h2,  {<br />
font-weight: normal;<br />
clear: both;<br />
}</p>
<p>Your h3 and below tags can now be used with an image displayed either right or left.</p>
</div><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.realestatebloglab.com%2Ftwentyten%2Ftwenty-ten-the-new-default-theme%2F&amp;layout=standard&amp;show-faces=true&amp;width=500&amp;action=like&amp;colorscheme=light" scrolling="no" frameborder="0″ allowTransparency="true" style="border:none; overflow:hidden; width:500px; height:60px"></iframe><p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/twentyten/twenty-ten-the-new-default-theme/">Twenty Ten the New Default Theme</a> </h3>

</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2HFIJbWqYZs:uqvBAjqUNvw:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2HFIJbWqYZs:uqvBAjqUNvw:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=2HFIJbWqYZs:uqvBAjqUNvw:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2HFIJbWqYZs:uqvBAjqUNvw:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=2HFIJbWqYZs:uqvBAjqUNvw:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2HFIJbWqYZs:uqvBAjqUNvw:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=2HFIJbWqYZs:uqvBAjqUNvw:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2HFIJbWqYZs:uqvBAjqUNvw:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=2HFIJbWqYZs:uqvBAjqUNvw:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2HFIJbWqYZs:uqvBAjqUNvw:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://www.realestatebloglab.com/twentyten/twenty-ten-the-new-default-theme/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>A Couple of Gotcha’s with WP 3.0 Upgrade to Avoid</title>
		<link>http://www.realestatebloglab.com/wordpress/a-couple-of-gotchas-with-wp-3-0-upgrade-to-avoid/</link>
		<comments>http://www.realestatebloglab.com/wordpress/a-couple-of-gotchas-with-wp-3-0-upgrade-to-avoid/#comments</comments>
		<pubDate>Sun, 11 Jul 2010 13:38:30 +0000</pubDate>
		<dc:creator>Dave Smith</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress 3.0 upgrade]]></category>

		<guid isPermaLink="false">http://www.realestatebloglab.com/?p=800</guid>
		<description><![CDATA[<div class='embaArticle' style='display:inline'><p>The other day I was asked &#8220;Hey, <acronym title='The Dial-up Geek'>Dave</acronym>, you upgraded to WordPress 3.o yet?&#8221;</p>
<p>Kinda, I have most of my sites on <acronym title='WordPress'>WP</acronym> 3.0.  The newer ones were easy.  Three of those were already on 3.0 Beta or 3.0 RC.</p>
<p>The small sites running 2.9.2 were a snap as well.  I don&#8217;t know if I mentioned it earlier or not, but if you are running any kind of cache plugin you will want to de-active it before you upgrade.  Since WPMU is now integrated into 3.0 there can be an issue with a cache plugin.</p>
<p>I found another this week while upgrading the Tucson Real Estate blog.  It has quite a few plugins running and some special code in place to speed up page load times.  Because of this I hesitated to run the upgrade till I had more than a few minutes to dedicate to it.</p>
<p>I can&#8217;t stress enough that you:</p>
<ol>
<li>Backup your Database</li>
<li>Backup your wp-content directory</li>
<li>Have a copy of 2.9.2 available to FTP back if needed</li>
<li>Be prepared to restore your database from OUTSIDE <acronym title='WordPress'>WP</acronym> itself</li>
<li>Optional but recommended for this update (DE-Activate all Plugins)</li>
</ol>
<p>I had all this in place when I pushed the button for auto upgrade.   All except the De-active all plugings.</p>
<p>Yep, you guessed it.  FATAL ERROR.  BIG TIME.</p>
<p>I restored the DB and uploaded the 2.9.2 files back in place.</p>
<p>This time I de-activated all plugins except for a few that I needed to keep the theme functioning.  And a couple I thought totally safe.</p>
<p>The upgrade was successful.  Now I started activating plugins in groups.  My second group brought back the Fatal Error.  I deleted those plugins with FTP but to no avail.  You guessed it.  Restore all again.</p>
<p>This time it was one at a time re-activation.</p>
<h3>NexGen Gallery Fatal Error</h3>
<p>The NexGen Gallery plugin was the one.  There wasn&#8217;t anything wrong with NexGen Gallery.  There was an update to the plugin.  But I hadn&#8217;t take the time to see if the upgrade was needed before the upgrade or after.  It turned out to be before.</p>
<p>Once I deleted the nexgen gallery by FTP and refreshed I was able to get back to the admin panel.  Using FTP I put the nexgen gallery plugin back into the plugin directory.  Before activation I updated the plugin then activated.  All was fine.</p>
<p>So I&#8217;ve found two ways to take a site into FATAL ERROR territory.  (Not a fun place to go)  But there was no panic.  I knew I had all the files I needed and the knowledge to fix any issues that would arise.  It is nice not to see FATAL ERROR and have your heart in your throat.</p>
<p>What about the Lab?  No, it is still on 2.9.2.  I have a lot of plugins active here at the Lab.  I&#8217;m going to run a fresh backup of the database and files then de-activate all the plugins before hitting that auto upgrade button.  I might get to it yet this weekend.  When I do I&#8217;ll let you know.</p>
<h3>Is it Safe to Upgrade to 3.0?</h3>
<p>Yes, I think it is.  This major upgrade was released on June 17th.  We are at July 10 and there have been no bug fix releases.  This is testimony to what a great job the <acronym title='WordPress'>WP</acronym> community has done in getting 3.0 ready for release.  Don&#8217;t cut corners and you should do fine.  But I can&#8217;t stress enough de-activating plugins for this release.  Especially if you have a lot of plugins running on your site.  And when you turn them back on, do it one or two at a time.</p>
</div><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.realestatebloglab.com%2Fwordpress%2Fa-couple-of-gotchas-with-wp-3-0-upgrade-to-avoid%2F&amp;layout=standard&amp;show-faces=true&amp;width=500&amp;action=like&amp;colorscheme=light" scrolling="no" frameborder="0″ allowTransparency="true" style="border:none; overflow:hidden; width:500px; height:60px"></iframe><p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/wordpress/a-couple-of-gotchas-with-wp-3-0-upgrade-to-avoid/">A Couple of Gotcha&#8217;s with WP 3.0 Upgrade to Avoid</a> </h3>

</p>
<p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/wordpress/a-couple-of-gotchas-with-wp-3-0-upgrade-to-avoid/">A Couple of Gotcha&#8217;s with WP 3.0 Upgrade to Avoid</a> </h3>

</p>
]]></description>
			<content:encoded><![CDATA[<div class='embaArticle' style='display:inline'><p>The other day I was asked &#8220;Hey, <acronym title='The Dial-up Geek'>Dave</acronym>, you upgraded to WordPress 3.o yet?&#8221;</p>
<p>Kinda, I have most of my sites on <acronym title='WordPress'>WP</acronym> 3.0.  The newer ones were easy.  Three of those were already on 3.0 Beta or 3.0 RC.</p>
<p>The small sites running 2.9.2 were a snap as well.  I don&#8217;t know if I mentioned it earlier or not, but if you are running any kind of cache plugin you will want to de-active it before you upgrade.  Since WPMU is now integrated into 3.0 there can be an issue with a cache plugin.</p>
<p>I found another this week while upgrading the Tucson Real Estate blog.  It has quite a few plugins running and some special code in place to speed up page load times.  Because of this I hesitated to run the upgrade till I had more than a few minutes to dedicate to it.</p>
<p>I can&#8217;t stress enough that you:</p>
<ol>
<li>Backup your Database</li>
<li>Backup your wp-content directory</li>
<li>Have a copy of 2.9.2 available to FTP back if needed</li>
<li>Be prepared to restore your database from OUTSIDE <acronym title='WordPress'>WP</acronym> itself</li>
<li>Optional but recommended for this update (DE-Activate all Plugins)</li>
</ol>
<p>I had all this in place when I pushed the button for auto upgrade.   All except the De-active all plugings.</p>
<p>Yep, you guessed it.  FATAL ERROR.  BIG TIME.</p>
<p>I restored the DB and uploaded the 2.9.2 files back in place.</p>
<p>This time I de-activated all plugins except for a few that I needed to keep the theme functioning.  And a couple I thought totally safe.</p>
<p>The upgrade was successful.  Now I started activating plugins in groups.  My second group brought back the Fatal Error.  I deleted those plugins with FTP but to no avail.  You guessed it.  Restore all again.</p>
<p>This time it was one at a time re-activation.</p>
<h3>NexGen Gallery Fatal Error</h3>
<p>The NexGen Gallery plugin was the one.  There wasn&#8217;t anything wrong with NexGen Gallery.  There was an update to the plugin.  But I hadn&#8217;t take the time to see if the upgrade was needed before the upgrade or after.  It turned out to be before.</p>
<p>Once I deleted the nexgen gallery by FTP and refreshed I was able to get back to the admin panel.  Using FTP I put the nexgen gallery plugin back into the plugin directory.  Before activation I updated the plugin then activated.  All was fine.</p>
<p>So I&#8217;ve found two ways to take a site into FATAL ERROR territory.  (Not a fun place to go)  But there was no panic.  I knew I had all the files I needed and the knowledge to fix any issues that would arise.  It is nice not to see FATAL ERROR and have your heart in your throat.</p>
<p>What about the Lab?  No, it is still on 2.9.2.  I have a lot of plugins active here at the Lab.  I&#8217;m going to run a fresh backup of the database and files then de-activate all the plugins before hitting that auto upgrade button.  I might get to it yet this weekend.  When I do I&#8217;ll let you know.</p>
<h3>Is it Safe to Upgrade to 3.0?</h3>
<p>Yes, I think it is.  This major upgrade was released on June 17th.  We are at July 10 and there have been no bug fix releases.  This is testimony to what a great job the <acronym title='WordPress'>WP</acronym> community has done in getting 3.0 ready for release.  Don&#8217;t cut corners and you should do fine.  But I can&#8217;t stress enough de-activating plugins for this release.  Especially if you have a lot of plugins running on your site.  And when you turn them back on, do it one or two at a time.</p>
</div><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.realestatebloglab.com%2Fwordpress%2Fa-couple-of-gotchas-with-wp-3-0-upgrade-to-avoid%2F&amp;layout=standard&amp;show-faces=true&amp;width=500&amp;action=like&amp;colorscheme=light" scrolling="no" frameborder="0″ allowTransparency="true" style="border:none; overflow:hidden; width:500px; height:60px"></iframe><p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/wordpress/a-couple-of-gotchas-with-wp-3-0-upgrade-to-avoid/">A Couple of Gotcha&#8217;s with WP 3.0 Upgrade to Avoid</a> </h3>

</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=yVTvV1IBQgg:7ZKDAGnOSmA:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=yVTvV1IBQgg:7ZKDAGnOSmA:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=yVTvV1IBQgg:7ZKDAGnOSmA:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=yVTvV1IBQgg:7ZKDAGnOSmA:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=yVTvV1IBQgg:7ZKDAGnOSmA:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=yVTvV1IBQgg:7ZKDAGnOSmA:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=yVTvV1IBQgg:7ZKDAGnOSmA:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=yVTvV1IBQgg:7ZKDAGnOSmA:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=yVTvV1IBQgg:7ZKDAGnOSmA:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=yVTvV1IBQgg:7ZKDAGnOSmA:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://www.realestatebloglab.com/wordpress/a-couple-of-gotchas-with-wp-3-0-upgrade-to-avoid/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>BuddyPress A Few Simple Additions Needed for Great Growth Potential</title>
		<link>http://www.realestatebloglab.com/real-estate-blogging/buddypress-a-few-simple-changes-needed-for-great-growth-potential/</link>
		<comments>http://www.realestatebloglab.com/real-estate-blogging/buddypress-a-few-simple-changes-needed-for-great-growth-potential/#comments</comments>
		<pubDate>Sat, 10 Jul 2010 16:52:19 +0000</pubDate>
		<dc:creator>Dave Smith</dc:creator>
				<category><![CDATA[Real Estate Blogging]]></category>
		<category><![CDATA[BuddyPress]]></category>
		<category><![CDATA[BuddyPress Admin Profile Management]]></category>

		<guid isPermaLink="false">http://www.realestatebloglab.com/?p=797</guid>
		<description><![CDATA[<a href=http://www.realestatebloglab.com/real-estate-blogging/buddypress-a-few-simple-changes-needed-for-great-growth-potential/><img src=http://www.realestatebloglab.com/wp-content/uploads/2010/07/BuddyPressLogo.gif class=imgtfe hspace=5 align=left width=100  border=0></a>It is time for BP to expand its vision of itself.  Time to go beyond the narrow community, forum, blogs and groups functions within a narrow vertical market and increase the user base.  Add these Admin capabilities mentioned above and you have a whole new BuddyPress.<p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/real-estate-blogging/buddypress-a-few-simple-changes-needed-for-great-growth-potential/">BuddyPress A Few Simple Additions Needed for Great Growth Potential</a> </h3>

</p>
]]></description>
			<content:encoded><![CDATA[<div class='embaArticle' style='display:inline'><p><a href="http://www.realestatebloglab.com/wp-content/uploads/2010/07/BuddyPressLogo.gif"><img class="size-full wp-image-798 alignright" title="BuddyPressLogo" src="http://www.realestatebloglab.com/wp-content/uploads/2010/07/BuddyPressLogo.gif" alt="" width="287" height="66" /></a>Yes, I&#8217;m back working with BuddyPress.  Now that it is a plugin, available since <acronym title='WordPress'>WP</acronym> 2.9.2  I&#8217;m trying to use it for a non-profit organization membership directory.<br />
How&#8217;s that going?<br />
Like stepping back to the wild west of programming.  BuddyPress is only on version 1.2.5  Still very early in development.  However, it is time for it to make some changes in how it thinks about itself and how it functions.</p>
<h3>Not a One Trick Pony</h3>
<p>I don&#8217;t know what was initially on the minds of the BP development team.  I think it was along the lines of adding a social media component to WordPress.  Like building your own version of Ning.  Members can have their own blogs, groups, and forums are available.  As an admin I can enable and disable certain functions.  Which is helpful, but limited.</p>
<p>BuddyPress doesn&#8217;t need to be a one trick pony.  There are so many things it can be used for in a variety of settings.  If there were some additions to the admin functionality.  It is time for BuddyPress to evolve.  Time to think outside of just the Social Media Environment box and expand its user base in the process.  BuddyPress shouldn&#8217;t be just for the geeks.  ( I&#8217;ll admin I&#8217;m a brown belt geek ).</p>
<p>I have many suggestions in mind but for now I&#8217;m going to address one change/addition that would make BuddyPress a perfect fit for many businesses and organizations which will take a pass on it now.</p>
<h3>BuddyPress Profile Management</h3>
<p>About the only thing an admin can do with profiles in BP is to expand them and create new sub categories for profile groups.  This functionality is good, but lacking and there is one HUGE way it needs improvement.</p>
<h3>Admin Edit Only Profile Fields</h3>
<p>As an admin I need to have the ability to make some profile fields Admin Edit Only.  Why?  Many organizations, businesses and groups have memberships.  Those members have designations, categories, dues, renewal date, status, etc. .  It is necessary to have these fields in a profile so the member can &#8220;View&#8221; them but not &#8220;Change them&#8221;.  Right now there is not way for an admin to &#8220;lock&#8221; fields in a profile.</p>
<p>This single limitation eliminates Buddypress from consideration for a lot of businesses and organizations.</p>
<p>I know I&#8217;m not alone here are some of the posts and threads I&#8217;ve found while searching for an answer.</p>
<p><a href="http://premium.wpmudev.org/forums/topic/possible-to-lock-buddypress-xprofile-fields">Possible to &#8220;Lock&#8221; Buddypress xprofile fields</a></p>
<p><a href="http://buddypress.org/community/groups/creating-extending/forum/topic/desired-plugin-for-admin-interface-view-edit-of-buddypress-registration-fields/">Plugin for Admin interface to profiles</a></p>
<p><a href="http://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/restrict-xprofile-group-to-administrator-only-write-access/">Restrict xProfile group to Administrator-only write access</a></p>
<p><a href="http://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-manage-users-their-extended-profiles/">How to manage users &amp; their extended profiles?</a></p>
<p>There&#8217;s more, this is just a sampling, I hope someone at BuddyPress can focus on these Profile issues SOON.</p>
<h3>User Profile Admin and Edit Lock Capabilities</h3>
<p>This is one place where BuddyPress can do itself a huge favor.  Address these issues and the use of BuddyPress for Organizations and Business will grow exponentially.   Exponentially?  Really, or just hyperbole?</p>
<p>YES, really.  I know of a number of places I could use it for business solutions and customer interface and feedback with these additions.  Right Now, it is off the table as a solution for most of my clients that need this type of tool in their on-line marketing arsonal.</p>
<p>It is time for BP to expand its vision and how it views itself.  Time to go beyond the narrow community, forum, blogs and groups functions within a single vertical market and increase the user base.  Add these Admin capabilities mentioned above and you have a whole new BuddyPress.  Doors of opportunity are seldom this easy to open.  Anyone at BuddyPress listening?  I hope so.  I would love to use it more.</p>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 403px; width: 1px; height: 1px; overflow: hidden;">http://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-manage-users-their-extended-profiles/</div>
</div><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.realestatebloglab.com%2Freal-estate-blogging%2Fbuddypress-a-few-simple-changes-needed-for-great-growth-potential%2F&amp;layout=standard&amp;show-faces=true&amp;width=500&amp;action=like&amp;colorscheme=light" scrolling="no" frameborder="0″ allowTransparency="true" style="border:none; overflow:hidden; width:500px; height:60px"></iframe><p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/real-estate-blogging/buddypress-a-few-simple-changes-needed-for-great-growth-potential/">BuddyPress A Few Simple Additions Needed for Great Growth Potential</a> </h3>

</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2LKiS4EyzMs:Z0V7avfblPs:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2LKiS4EyzMs:Z0V7avfblPs:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=2LKiS4EyzMs:Z0V7avfblPs:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2LKiS4EyzMs:Z0V7avfblPs:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=2LKiS4EyzMs:Z0V7avfblPs:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2LKiS4EyzMs:Z0V7avfblPs:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=2LKiS4EyzMs:Z0V7avfblPs:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2LKiS4EyzMs:Z0V7avfblPs:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=2LKiS4EyzMs:Z0V7avfblPs:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=2LKiS4EyzMs:Z0V7avfblPs:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://www.realestatebloglab.com/real-estate-blogging/buddypress-a-few-simple-changes-needed-for-great-growth-potential/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Do you utilize the site command?</title>
		<link>http://www.realestatebloglab.com/real-estate-blogging/do-you-utilize-the-site-command/</link>
		<comments>http://www.realestatebloglab.com/real-estate-blogging/do-you-utilize-the-site-command/#comments</comments>
		<pubDate>Mon, 05 Jul 2010 16:34:59 +0000</pubDate>
		<dc:creator>Dave Smith</dc:creator>
				<category><![CDATA[Real Estate Blogging]]></category>
		<category><![CDATA[Google site command]]></category>
		<category><![CDATA[where is my site indexed]]></category>

		<guid isPermaLink="false">http://www.realestatebloglab.com/?p=795</guid>
		<description><![CDATA[Where is my site indexed on other sites?<p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/real-estate-blogging/do-you-utilize-the-site-command/">Do you utilize the site command?</a> </h3>

</p>
]]></description>
			<content:encoded><![CDATA[<div class='embaArticle' style='display:inline'><p><strong>PS. Up front, if you use the site command you still might want to read this post.</strong></p>
<p>I&#8217;m often asked &#8220;How&#8217;s my site doing&#8221;  I&#8217;m not getting much traffic and I don&#8217;t know why?</p>
<p>The first thing I do is run the site command in a Google search to see how many pages are in the Google index.  It also shows me how the title tags are being indexed and the excerpts being generated.</p>
<h3>The Site command</h3>
<p>I&#8217;m pretty sure many of you already know about the site command, for those that don&#8217;t it works like this:</p>
<ul>
<li>Open Google and enter site:yourdomain.com</li>
</ul>
<p>This will return how many pages are indexed and show the links to them.</p>
<p>Ex.  site:tucsontired.com  today will return 54 pages in the Google index.</p>
<h3>Where is my site indexed on other sites</h3>
<p>This might be the little twist you didn&#8217;t know.  You can also use the site command to find where your site is mentioned on the web.</p>
<p>How?  Add a space between the command and the url.  And put the url in quotes Ex.  Site: &#8220;tucsontired.com&#8221;  This will now return 436 results and show me where my site is indexed on other sites.</p>
<p>Try it out for your site.  Since today is the second 4th of July in 2010, (Since most count today as the holiday) and you have some geek time on your hands check this out.  Find anything interesting?</p>
</div><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.realestatebloglab.com%2Freal-estate-blogging%2Fdo-you-utilize-the-site-command%2F&amp;layout=standard&amp;show-faces=true&amp;width=500&amp;action=like&amp;colorscheme=light" scrolling="no" frameborder="0″ allowTransparency="true" style="border:none; overflow:hidden; width:500px; height:60px"></iframe><p><h3>From: <a href="http://www.realestatebloglab.com">Real Estate Blog Lab</a>   <a href="http://www.realestatebloglab.com/real-estate-blogging/do-you-utilize-the-site-command/">Do you utilize the site command?</a> </h3>

</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=Efpdqadgx1Y:BHHY8q_3yos:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=Efpdqadgx1Y:BHHY8q_3yos:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=Efpdqadgx1Y:BHHY8q_3yos:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=Efpdqadgx1Y:BHHY8q_3yos:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=Efpdqadgx1Y:BHHY8q_3yos:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=Efpdqadgx1Y:BHHY8q_3yos:F7zBnMyn0Lo"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=Efpdqadgx1Y:BHHY8q_3yos:F7zBnMyn0Lo" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=Efpdqadgx1Y:BHHY8q_3yos:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?i=Efpdqadgx1Y:BHHY8q_3yos:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RealEstateBlogLab?a=Efpdqadgx1Y:BHHY8q_3yos:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/RealEstateBlogLab?d=qj6IDK7rITs" border="0"></img></a>
</div>]]></content:encoded>
			<wfw:commentRss>http://www.realestatebloglab.com/real-estate-blogging/do-you-utilize-the-site-command/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
