<?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>stepheno.net &#187; Wordpress</title>
	<atom:link href="http://stepheno.net/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://stepheno.net</link>
	<description>Captivating communication confusion</description>
	<lastBuildDate>Sun, 22 Jan 2012 13:50:42 +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 Plugins: Getting Started</title>
		<link>http://stepheno.net/2007/03/29/wordpress-plugins-getting-started/</link>
		<comments>http://stepheno.net/2007/03/29/wordpress-plugins-getting-started/#comments</comments>
		<pubDate>Thu, 29 Mar 2007 10:19:52 +0000</pubDate>
		<dc:creator>stephen olsen</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Web 2.0]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://stepheno.net/2007/03/29/wordpress-plugins-getting-started/</guid>
		<description><![CDATA[After upgrading to WordPress 2.1 I did check out some plugin alternatives, before blindly activating or upgrading my existing plugins. Today I came across Top 30 WordPress Plugins in Blogosphere, where the plugins are ranked and explained. So if you &#8230; <a href="http://stepheno.net/2007/03/29/wordpress-plugins-getting-started/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p></p><br /><p>After <a href="http://stepheno.net/2007/03/26/painful-wordpress-21-upgrade/" title="Painful WordPress 2.1 Upgrade">upgrading to WordPress 2.1</a> I did check out some plugin alternatives, before blindly activating or upgrading my existing plugins. Today I came across <a href="http://www.staska.net/2007/03/27/top-30-wordpress-plugins-in-blogosphere/" title="Top 30 WordPress Plugins in Blogosphere">Top 30 WordPress Plugins in Blogosphere</a>, where the plugins are ranked and explained.</p>
<p><img src="http://stepheno.net/wpso/wp-content/2007/03/wptop30plugins.jpg" alt="Screenshot Staska.netTop 30 WP Plugins" /></p>
<p>So if you are considering installing WordPress, or already have it and are looking for some good plugins this post at <a href="http://www.staska.net" title="Staska.net">staska.net</a> looks great.</p>
]]></content:encoded>
			<wfw:commentRss>http://stepheno.net/2007/03/29/wordpress-plugins-getting-started/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Painful WordPress 2.1 Upgrade</title>
		<link>http://stepheno.net/2007/03/26/painful-wordpress-21-upgrade/</link>
		<comments>http://stepheno.net/2007/03/26/painful-wordpress-21-upgrade/#comments</comments>
		<pubDate>Mon, 26 Mar 2007 09:54:18 +0000</pubDate>
		<dc:creator>stephen olsen</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Web 2.0]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://stepheno.net/2007/03/26/painful-wordpress-21-upgrade/</guid>
		<description><![CDATA[So I finally put off an hour to upgrade to WordPress 2.1. That hour quickly turned into almost three hours, when wp-cache, although &#8220;deactivated&#8221;, caused havoc to my new installation of WordPress 2.1. After uploading all the files, I was &#8230; <a href="http://stepheno.net/2007/03/26/painful-wordpress-21-upgrade/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p></p><br /><p>So I finally put off an hour to upgrade to WordPress 2.1. That hour quickly turned into almost three hours, when wp-cache, although &#8220;deactivated&#8221;, caused havoc to my new installation of WordPress 2.1.</p>
<p><img src="http://stepheno.net/wpso/wp-content/2007/03/wordpress21.jpg" alt="Screenshot WordPress 2.1 Homepage" /></p>
<p>After uploading all the files, I was looking forward to the simple Upgrade script, which wouldn&#8217;t show.<br />
I had to go searching forums and others&#8217; failed experiences util I isolated the problem to wp-cache. I ended up having to manually edit several lines, and just give up on running wp-cache for now. Otherwise, I like some of the new face changes of WordPress, and have yet to see</p>
]]></content:encoded>
			<wfw:commentRss>http://stepheno.net/2007/03/26/painful-wordpress-21-upgrade/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WordPress 2.0.6 Partially Solves one.com Error?</title>
		<link>http://stepheno.net/2007/01/06/wordpress-206-partially-solves-onecom-error/</link>
		<comments>http://stepheno.net/2007/01/06/wordpress-206-partially-solves-onecom-error/#comments</comments>
		<pubDate>Sat, 06 Jan 2007 19:44:31 +0000</pubDate>
		<dc:creator>stephen olsen</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Information]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[RSS]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://stepheno.net/2007/01/06/wordpress-206-partially-solves-onecom-error/</guid>
		<description><![CDATA[I just updated stepheno.net to WordPress 2.0.6. It appears that some of the initial errors and problems I stumbled upon when I was installing WordPress 2.0.5 for the first time here at one.com are now solved. (My workaround for WP &#8230; <a href="http://stepheno.net/2007/01/06/wordpress-206-partially-solves-onecom-error/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p></p><br /><p>I just updated stepheno.net to <a title="WordPress 2.0.6 released" href="http://wordpress.org/development/2007/01/wordpress-206/">WordPress 2.0.6</a>. It appears that some of the initial errors and problems I stumbled upon when I was installing WordPress 2.0.5 for the first time here at one.com are now solved. (My workaround for WP 2.0.5 can be read here: <a title="Installing WordPress at one.com" href="http://stepheno.net/2006/12/05/installing-wordpress/">Installing WordPress at one.com</a>).</p>
<p> <img id="image91" alt="WordPress Screenshot" src="http://stepheno.net/wpso/wp-content/2007/01/wp206.jpg" /></p>
<p>As visitors may experience, I am still struggling redirecting to my RSS feed at FeedBurner (<a title="stepheno.net Migrating to FeedBurner" href="http://stepheno.net/2006/12/17/stephenonet-migrating-to-feedburner/">stepheno.net Migrating to FeedBurner</a>). This has to do with 30x Location awkwardness at one.com, I am working on trying different solutions. I can however state that my feed is accessible directly at: <a href="http://feeds.feedburner.com/stepheno">http://feeds.feedburner.com/stepheno</a></p>
<p>(Also redirecting apparently works sometimes with Google Reader using the url <a href="http://stepheno.net/feed">http://stepheno.net/feed</a> .)</p>
]]></content:encoded>
			<wfw:commentRss>http://stepheno.net/2007/01/06/wordpress-206-partially-solves-onecom-error/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Installing WordPress at one.com</title>
		<link>http://stepheno.net/2006/12/05/installing-wordpress/</link>
		<comments>http://stepheno.net/2006/12/05/installing-wordpress/#comments</comments>
		<pubDate>Tue, 05 Dec 2006 11:25:11 +0000</pubDate>
		<dc:creator>stephen olsen</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[You might have stumbled upon a couple problems while trying to install WordPress on your own newly acquired website hosted at one.com. Because of some small limitations in their service, the initial steps at wordpress didn&#8217;t work. However the following &#8230; <a href="http://stepheno.net/2006/12/05/installing-wordpress/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p></p><br /><p>You might have stumbled upon a couple problems while trying to install WordPress on your own newly acquired website hosted at one.com. Because of some small limitations in their service, the initial steps at wordpress didn&#8217;t work. However the following steps should make your journey through the jungle just a little bit easier.<span id="more-1"></span></p>
<p>(Initially following the true <a title="guide" href="http://stepheno.net/codex.wordpress.org/Installing_WordPress">guide</a> at WordPress)</p>
<p>1. Creating a database<br />
After inquiring with one.com support I finally had to surrender to the fact that you are restricted to one database and one user at one.com. Shuffling myself after this defeat of a disorganized database for all your desires, the next challenges lay ahead.</p>
<p>2. Config.php<br />
You&#8217;ll have to enter the all around databasename, username and password you received in your mail (hint: its the username and password that belong to mysql) Leave localhost as it is.<br />
Personally I decided to change the table_prefix slightly. Rename &#8230;sample to config.php</p>
<p>3. Get hold of the plugin: <a title="WordPress Tuneup" href="http://txfx.net/code/wordpress/wordpress-tuneup/wordpress-205-tuneup/">wordpress-205-tuneup</a> and put the plugin into the directory wordpress/wp-content/plugins</p>
<p>4. Upload your wordpress folder to your website. Personally I would keep the wordpress folder for tidiness&#8217; sake, and not upload all the small wp files directly into your root directory.</p>
<p>5. Head over to http://www.your.site/wordpress/wp-admin/install.php<br />
After naming wordpress and filling in your email it&#8217;ll give you a username and password. Here the weird stuff might start.</p>
<p>6. Go to the login url http://www.your.site/wordpress/wp-login.php<br />
Type in your username and password and hit enter. In my case it seemed to process, then spewed out a 302 Found document, telling me it had found itself. Well I reload and tred again. Nothing!</p>
<p>7. So I cheated I found the direct url to get to the plugin-page and pasted it in:</p>
<p>http://www.your.site/wordpress/wp-admin/plugins.php</p>
<p>Find the WordPress 2.0.5 Tune Up plugin in the list and click, Activate, to the right<br />
Again you may be directed to another 302 page, so try hitting reload. It now directed me back to the plugins page and said it was activated.</p>
<p>8. But you&#8217;ll want your blog to appear in the root URL. ie. http://www.your.site  and NOT http://www.your.site/wordpress . Because you&#8217;ll want your visitors to get to your blog as easily as possible.</p>
<p>9. Basically you need to do the following (<a title="Creating WP in its own dir" href="http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory">Details</a> at WordPress)<br />
Go to Site admin -> Options (General)<br />
Change Blog address to: http://www.your.site  (stripping /wordpress/)<br />
Click Update options<br />
Then you need to (via ftp) copy index.php and .htaccess from your wordpress folder to your root directory and change the following code in your index.php file:<br />
require(&#8216;./wp-blog-header.php&#8217;); to require(&#8216;./wordpress/wp-blog-header.php&#8217;);</p>
<p>10. Congratulations, you are now ready to rumble *cough* blog.</p>
]]></content:encoded>
			<wfw:commentRss>http://stepheno.net/2006/12/05/installing-wordpress/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
	</channel>
</rss>

