<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	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/"
	>

<channel>
	<title>on the road &#187; WordPress</title>
	<atom:link href="http://blog.twolaneroads.com/tag/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.twolaneroads.com</link>
	<description>Riding farther, seeing more</description>
	<lastBuildDate>Tue, 24 Jan 2012 19:24:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>WordPress is getting a tad tiresome</title>
		<link>http://blog.twolaneroads.com/2008/11/27/wordpress-is-getting-a-tad-tiresome/</link>
		<comments>http://blog.twolaneroads.com/2008/11/27/wordpress-is-getting-a-tad-tiresome/#comments</comments>
		<pubDate>Fri, 28 Nov 2008 06:54:05 +0000</pubDate>
		<dc:creator>RF</dc:creator>
				<category><![CDATA[Blog tribulations]]></category>
		<category><![CDATA[Stupidity plain and simple]]></category>
		<category><![CDATA[stupidity]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blog.twolaneroads.com/?p=705</guid>
		<description><![CDATA[I had a new implementation of WordPress installed on a motorcycle site, which was previously written in html. I wasn&#8217;t aware of any problems with the WordPress visual editor until I encountered it on the new site. I did a search and was able to come up with quite a few solutions, but none of [...]]]></description>
			<content:encoded><![CDATA[<p>I had a new implementation of WordPress installed on a motorcycle site, which was previously written in html. I wasn&#8217;t aware of any problems with the WordPress visual editor until I encountered it on the new site. I did a search and was able to come up with quite a few solutions, but none of the solutions worked for me &#8212; or for many others, it seems. No big deal. Find a thread, post a question, and someone will eventually come up with something that works.</p>
<p>It would appear that some of us have touched a WordPress nerve, thus we have this:</p>
<blockquote><p>and here&#8217;s a general rant to those of you that are whining that your threads arent getting replied to (ive seen like 7-8 in the last 4 hours) &#8212; its a fucking holiday in the US (where 90% of us live), and some people dont spend them online. Im ONLY here because Im working. Get a grip &#8212; your dumb little &#8220;i cant get my adsense to show up&#8221; or your &#8220;i want an archives page&#8221; crap isnt more important than someone spending a damn holiday with their family, and away from a bunch ingrates that cant use a search box. FFS, most of you dont even say please, or thank you.</p></blockquote>
<p><a href="http://wordpress.org/support/topic/220455?replies=23" target="_blank">Go here if you want to see the thread</a>. I&#8217;m the guy with the palm tree in my avatar.</p>
<p>As a result of this, I have decided to leave my site in html and remove WordPress. It looks much better the way it is, and editing the html is a breeze for me.</p>
<p><strong>Thanks, but no thanks, WordPress.</strong></p>
<p>Link to site here.</p>
<p>Furthermore, I get absolutely no spam on the site since it&#8217;s in html. It&#8217;s not a high-traffic site, but it does get three to four hundred hits a month, purely for the technical articles.</p>
<p>And <em>whooami</em>, male or female<em> </em>WordPress goowill ambassador that you are, you&#8217;ll find sympathy in the dictionary, somewhere between <em>shit </em>and <em>syphilis</em>.</p>
<h2>Now for the history lesson</h2>
<p>You knew it was coming, right?</p>
<p>The <em>&#8220;it&#8217;s a fucking holiday in the U.S. of A.&#8221;</em> that <em>whooami </em>makes reference to is called Thanksgiving. It&#8217;s celebrated in the U.S. as a time when invading religious zealots gave thanks to the native North American population for letting them come ashore, bringing religious fervor, pestilence, slaughter, mass displacement and ownership to an otherwise pretty satisfied people as a whole.</p>
<p>Outside of North America, I can&#8217;t think of one other country or nation that celebrates Thanksgiving. Certainly not Mexico or Central America, where visitors from Europe (for you geography-challenged Americans, that&#8217;s a continent, not a country) brought disease, more pestilence, religion-induced slaughter, and conquest to a civilization that was more than a little advanced. Obviously, Europeans (people living on a continent, not a country) don&#8217;t celebrate Thanksgiving.</p>
<p>South America (another continent, consisting of many countries) doesn&#8217;t celebrate Thanksgiving. Nor does Asia, Australia, Africa, the Middle East and on and on and on. So basically, we have a country of 330 million people, far outnumbered by the remainder of the known world, completely in ignorance of the other six billion scattered here and there on the globe.</p>
<p>Oh well, it was ever thus.</p>
<p><em></em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.twolaneroads.com/2008/11/27/wordpress-is-getting-a-tad-tiresome/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Throwing stones</title>
		<link>http://blog.twolaneroads.com/2007/06/23/throwing-stones/</link>
		<comments>http://blog.twolaneroads.com/2007/06/23/throwing-stones/#comments</comments>
		<pubDate>Sat, 23 Jun 2007 12:03:06 +0000</pubDate>
		<dc:creator>RF</dc:creator>
				<category><![CDATA[Blog tribulations]]></category>
		<category><![CDATA[Hardware/Software]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blog.twolaneroads.com/2007/06/23/throwing-stones/</guid>
		<description><![CDATA[I just thought it was amusing that in order to recommend overcoming the security lapses of one product, one must use another product with its own security problems.]]></description>
			<content:encoded><![CDATA[<p>Oh look &#8211; someone is <a href="http://www.wincent.com/a/about/wincent/weblog/archives/2007/06/wordpress_flaw.php" target="_blank">slagging</a> WordPress because of security problems. He goes so far as to recommend a competitor, in this case, Moveable Type, which he promotes on his web site.</p>
<p>Should one take the time to read down to the last paragraph, one will discover that in order to have a secure Moveable Type (MT) installation, one must disable comments. His link to Moveable Type security notes mentions several additional security precautions one should take with Moveable Type to remain secure:</p>
<blockquote><p>If you can turn off comments and search then you can effectively hide all traces of your Movable Type installation from the public eye and just use it as a convenient tool for generating static but easily-updateable pages. Most people won&#8217;t even know you&#8217;re running Movable Type. By putting your install in an out-of-the-way location, you can use security through obscurity (not always a bad thing) to protect you from any flaws that might be in the product. I use this technique on my personal weblog&#8230;</p></blockquote>
<p>So then, in order to have a more secure blogging product, we do the following:</p>
<ul style="margin-right: 0px;" dir="ltr">
<li dir="ltr">convert to another platform, specifically MT;</li>
<li dir="ltr">turn off MT comments;</li>
<li dir="ltr">and while you&#8217;re at it, turn off your MT search function;</li>
<li dir="ltr">don&#8217;t advertise the location of your MT install;</li>
<li dir="ltr">move your MT install location to a more unintelligible URL.</li>
</ul>
<p>I really don&#8217;t have any problem with it all, I just thought it was amusing that in order to recommend overcoming the security lapses of one product, one must use another product with its own security problems.</p>
<p>Yawn.</p>
<p><em>(Thanks to <a title="WordPress security" href="http://ma.tt/2007/06/on-wp-security/" target="_blank">Photo Matt</a> for the post. He&#8217;s the founding developer of <a title="WordPress" href="http://wordpress.org" target="_blank">WordPress.</a>) </em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.twolaneroads.com/2007/06/23/throwing-stones/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Seamless WordPress 2.2.1 upgrade yet again</title>
		<link>http://blog.twolaneroads.com/2007/06/21/seamless-wordpress-221-upgrade-yet-again/</link>
		<comments>http://blog.twolaneroads.com/2007/06/21/seamless-wordpress-221-upgrade-yet-again/#comments</comments>
		<pubDate>Thu, 21 Jun 2007 17:47:13 +0000</pubDate>
		<dc:creator>RF</dc:creator>
				<category><![CDATA[Blog tribulations]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blog.twolaneroads.com/2007/06/21/seamless-wordpress-221-upgrade-yet-again/</guid>
		<description><![CDATA[The 2.2.1 upgrade provides some required security fixes as well as some bug fixes.]]></description>
			<content:encoded><![CDATA[<p>Once more, thanks to the <a title="Fully automatic upgrades " href="http://www.zirona.com/software/wordpress-instant-upgrade/" target="_blank">Instant Upgrade</a> plugin, version 0.2 from <a title="Zirona :: OpenSource-Consulting" href="http://www.zirona.com/startseite/">Zirona.</a> I&#8217;ve used it for the last two upgrades, and it has worked quickly and flawlessly. Of course, I also do my daily backups of the database and program modules in the event of any kind of failure. Call me <span style="text-decoration: line-through;">astute</span> paranoid one more time.</p>
<p>The 2.2.1 upgrade provides some required security fixes as well as some bug fixes.</p>
<p>I&#8217;ve noticed that some are complaining about the recent frequency of upgrades, as well as the trashing of plugins by those same upgrades. To them, I say, why not try <a title="Seamless WordPress upgrade" href="http://www.zirona.com/software/wordpress-instant-upgrade/" target="_blank">Instant Upgrade?</a></p>
<p>It won&#8217;t solve the plugin problem, but it certainly makes for a smooth, fast, trouble-free update: no searching for a site with the required files; no messing with manually moving files; no worrying about whether one has moved the correct files to the appropriate directories.</p>
<p>Thanks again, Zirona and <span class="subtitle">Alex G</span>ü<span class="subtitle">nsche</span>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.twolaneroads.com/2007/06/21/seamless-wordpress-221-upgrade-yet-again/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Contact form blues</title>
		<link>http://blog.twolaneroads.com/2007/06/05/contact-form-blues/</link>
		<comments>http://blog.twolaneroads.com/2007/06/05/contact-form-blues/#comments</comments>
		<pubDate>Wed, 06 Jun 2007 02:30:39 +0000</pubDate>
		<dc:creator>RF</dc:creator>
				<category><![CDATA[Blog tribulations]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blog.twolaneroads.com/2007/06/05/contact-form-blues/</guid>
		<description><![CDATA[I have no time for fiddling.]]></description>
			<content:encoded><![CDATA[<p><strong>Updated below </strong></p>
<p>I was having trouble with  <a title="Beast-Blog.com" href="http://green-beast.com/blog/" target="_blank">Beast-Blog.com&#8217;s</a> contact form on my site, so I scrapped it entirely in favor of another I found here at The Marketing Technology Blog. He calls it the <a href="http://www.marketingtechblog.com/projects/wp-contactform/">WordPress Contact Form with Spam Protection.</a></p>
<p>It&#8217;s configurable, it fits nicely on a page, and by the look of it, it will prevent email spamming. More importantly, it took a minimum of fiddling to get it set up &#8211; which is all I really care about at this point in my life.</p>
<p>I have no time for fiddling.</p>
<p>I&#8217;d rather be riding.</p>
<p><strong>Update</strong>:  The most recent version of this plugin (v3.1.2) is broken and doesn&#8217;t display properly in FireFox. IE isn&#8217;t so great either. Sigh. I&#8217;m off to find another one that does work.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.twolaneroads.com/2007/06/05/contact-form-blues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>For all my faithful readers&#8230;</title>
		<link>http://blog.twolaneroads.com/2007/05/31/for-all-my-faithful-readers/</link>
		<comments>http://blog.twolaneroads.com/2007/05/31/for-all-my-faithful-readers/#comments</comments>
		<pubDate>Thu, 31 May 2007 15:15:37 +0000</pubDate>
		<dc:creator>RF</dc:creator>
				<category><![CDATA[Blog tribulations]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blog.twolaneroads.com/2007/05/31/for-all-my-faithful-readers/</guid>
		<description><![CDATA[Fair warning: you might wish to turn off the feed readers for a bit.]]></description>
			<content:encoded><![CDATA[<p>all five of you:</p>
<p>Fair warning: you might wish to turn off the feed readers for a bit.</p>
<p>I&#8217;ve been investigating search engine querys that have hit my blog pages. Consequently, I&#8217;m going to be updating some of my posts with metas and tags over the next several days. The reason for this is that while some queries show up with a direct link to the page in question, others do not, and land on the blog&#8217;s front page, making finding the article difficult.</p>
<p>I know, I should have started this from the beginning, but who knew? Not me, obviously.</p>
<p>Of course, I would be most pleased if at some point you would turn me back on.</p>
<p>I&#8217;ll be using <a title="Tag it with All in One SEO Pack" href="http://wp.uberdose.com/2007/03/24/all-in-one-seo-pack/" target="_blank">All in One SEO Pack</a> for this &#8212; another plugin.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.twolaneroads.com/2007/05/31/for-all-my-faithful-readers/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

