<?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>Life, Hacks, and Internet &#187; WordPress</title>
	<atom:link href="http://pufone.org/blog/type/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://pufone.org/blog</link>
	<description>AdSense Money with WordPress in Google while Hacking.</description>
	<lastBuildDate>Fri, 05 Feb 2010 14:07:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>TinyMCE wysiwyg in WordPress is No Good</title>
		<link>http://pufone.org/blog/tinymce-wysiwyg-in-wordpress-is-no-good/</link>
		<comments>http://pufone.org/blog/tinymce-wysiwyg-in-wordpress-is-no-good/#comments</comments>
		<pubDate>Thu, 07 Jun 2007 23:20:37 +0000</pubDate>
		<dc:creator>Cugone</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://pufone.org/blog/tinymce-wysiwyg-in-wordpress-is-no-good/</guid>
		<description><![CDATA[The default WordPress wysiwyg writing tool, TinyMCE is a piece of shit. First, there&#8217;s the character escaping. I can&#8217;t upload and embed a god damn flash video (*.flv) because TinyMCE decides to escape and &#34;correct&#34; all the friggin code:

Then there&#8217;s the upload tool. It doesn&#8217;t generate valid code. It sends apostrophes instead of commas, then [...]]]></description>
			<content:encoded><![CDATA[<p>The default WordPress <a rel="external nofollow" title="Wikipedia article on WYSIWYG" name="Wikipedia article on WYSIWYG" target="_blank" href="http://en.wikipedia.org/wiki/WYSIWYG">wysiwyg</a> writing tool, TinyMCE is a piece of shit. First, there&#8217;s the character escaping. I can&#8217;t upload and embed a god damn flash video (*.flv) because TinyMCE decides to escape and &quot;correct&quot; all the friggin code:</p>
<p align="center"><img width="512" height="181" align="absmiddle" src="http://pufone.org/blog/wp-content/uploads/2007/06/tinymce-wordpress-escaping.png" alt="TinyMCE character escaping in WordPress" title="TinyMCE character escaping" /></p>
<p>Then there&#8217;s the upload tool. It doesn&#8217;t generate valid code. It sends apostrophes instead of commas, then after saving the post, it changes the tag properties to UPERCASE! WTF man, XHTML 1.0 transitional asks for lowercase tag properties. Also, there is no width, height and alt for the img tag properties when uploading images. This is crucial to image SEO. Switching to <span id="more-46"></span> Code view doesn&#8217;t help. I&#8217;d be better off with a plain text editor.</p>
<p align="center"><img width="300" height="100" alt="FCKeditor buttons" src="http://pufone.org/blog/wp-content/uploads/FCKeditor-buttons.gif" title="FCKeditor buttons" /></p>
<p align="center">Nuff said, i switched to <a rel="external nofollow" href="http://www.deanlee.cn/wordpress/fckeditor-for-wordpress-plugin/" target="_blank" name="Dean's FCKEditor WordPress Plugin" title="Dean's FCKEditor WordPress Plugin">Dean&#8217;s FCKEditor plugin</a> for WordPress. Thanks Dean!</p>
<p><a href="http://www.fckeditor.net/" target="_blank" name="FCKeditor oggicial website" title="FCKeditor oggicial website">FCKeditor</a> is a great &quot;What You See Is What You Get&quot; aka WYSIWYG tool. Too bad it doesn&#8217;t work with Opera due to compatibility issues. Whell, as I said before, plain code is better than TinyMCE because ultimately I verify for code errors before posting, and besides I have <a href="http://pufone.org/getfirefox.html" onclick="window.open(this.href,'DownloadFireFoxwithGoogleToolbar','resizable=yes,location=no,menubar=no,scrollbars=no,status=yes,toolbar=no,fullscreen=no,dependent=no,width=620,height=240,status'); return false" name="Download FireFox with Google Toolbar" title="Download FireFox with Google Toolbar">FireFox</a>, so that makes it acceptable.</p>
<p>If you know any other WYSIWYG plugins besides these two, please let me know.</p>
]]></content:encoded>
			<wfw:commentRss>http://pufone.org/blog/tinymce-wysiwyg-in-wordpress-is-no-good/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Upgrading to WordPress 2.2</title>
		<link>http://pufone.org/blog/upgrading-to-wordpress-22/</link>
		<comments>http://pufone.org/blog/upgrading-to-wordpress-22/#comments</comments>
		<pubDate>Wed, 16 May 2007 23:28:48 +0000</pubDate>
		<dc:creator>Cugone</dc:creator>
				<category><![CDATA[AdSense]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://pufone.org/blog/upgrading-to-wordpress-22/</guid>
		<description><![CDATA[As you might know, today WordPress version 2.2 has been released.
After reading the changelog, I decided to upgrade pufone.org blog and also write a guide with screenshots. Who knows this might help some of you out there. Here is how I upgraded from WordPress 2.1.3 to WordPress 2.2:
First, i downloaded WordPress 2.2.
Then i begun the [...]]]></description>
			<content:encoded><![CDATA[<p>As you might know, today <strong><a href="http://wordpress.org/development/2007/05/wordpress-22/" target="_blank" rel="external nofollow">WordPress version 2.2</a></strong> has been released.</p>
<p>After reading the changelog, I decided to upgrade pufone.org blog and also write a guide with screenshots. Who knows this might help some of you out there. Here is how I upgraded from WordPress 2.1.3 to WordPress 2.2:</p>
<p>First, i downloaded <a href="http://wordpress.org/download/" rel="external nofollow">WordPress 2.2</a>.<br />
Then i begun the backup. The backup process consists of two parts:</p>
<ul>
<li>The MySQL backup</li>
</ul>
<p>I backed up my WordPress database using phpMyAdmin, if you don&#8217;t have it installed, you might want to read <a href="http://fragments.turtlemeat.com/mysql-database-backup-restore-phpmyadmin.php" rel="external nofollow" target="_blank">this</a> tutorial. (half way down the page)<!--adsense#468x60-mainpage-ad--><br />
To do this you first need to <span id="more-25"></span>select the database, then click on the Export link:<br />
<!--adsense#post-link--></p>
<p style="text-align: center"><a href="http://pufone.org/blog/upgrading-to-wordpress-22/exporting-wp-database-1/" rel="attachment wp-att-26" title="Exporting wp database 1" target="_blank"><img src="http://pufone.org/blog/wp-content/uploads/2007/05/exporting-wp-database1.thumbnail.png" alt="Exporting wp database 1" /></a></p>
<p>Then you have to select all the tables in the database (Ctrl+A) and check all the boxes i have checked, then click on Go, like this:<br />
<!--adsense#middle-post-ad--></p>
<p style="text-align: center"><a href="http://pufone.org/blog/upgrading-to-wordpress-22/exporting-wp-database-2/" title="Exporting wp database 2" rel="attachment wp-att-27" target="_blank"><img src="http://pufone.org/blog/wp-content/uploads/2007/05/exporting-wp-database2.thumbnail.png" alt="Exporting wp database 2" /></a></p>
<ul>
<li>The File/FTP backup</li>
</ul>
<p>This is pretty much straight forward. I have backed up the whole www folder because there are some other files like .htaccess that WordPress might screw in the upgrade process:</p>
<p style="text-align: center"><a href="http://pufone.org/blog/upgrading-to-wordpress-22/backing-up-the-www-folder/" rel="attachment wp-att-28" title="Backing up the www folder" target="_blank"><img src="http://pufone.org/blog/wp-content/uploads/2007/05/backing-up-files-ftp.thumbnail.png" alt="Backing up the www folder" /></a></p>
<p>The next step in upgrading to WordPress 2.2 is to deactivate all the plugins. You can do that by accessing your wp-admin&#8230; oh you know this <img src='http://pufone.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p style="text-align: center"><a href="http://pufone.org/blog/upgrading-to-wordpress-22/deactivating-the-wordpress-plugins/" title="Deactivating the WordPress Plugins" rel="attachment wp-att-29" target="_blank"><img src="http://pufone.org/blog/wp-content/uploads/2007/05/deactivating-wp-plugins.thumbnail.png" alt="Deactivating the WordPress Plugins" /></a></p>
<p>Now you have to delete some files from the WordPress folder. Generally, it is a good idea to delete whatever is possible because the uploading process may not correctly overwrite an existing file and that may cause problems later.</p>
<p><strong>DO NOT DELETE these folders and files:</strong></p>
<ul>
<li> wp-config.php file;</li>
<li> wp-content folder;</li>
<li> wp-images folder;</li>
<li> wp-includes/languages/ folder&#8211;if you are using a language file, do not delete this folder;.</li>
<li> .htaccess file&#8211;if you have added custom rules to your .htaccess, do not delete it;</li>
<li> Custom Content and/or Plugins&#8211;if you have any images or other custom content or Plugins inside the wp-content folder, do NOT delete them.</li>
</ul>
<p><strong>Delete these Files and Folders:</strong></p>
<ul>
<li> wp-* (except for those above), readme.html, wp.php, xmlrpc.php, and license.txt; files; Typically files in your root or wordpress folder. Again, don&#8217;t delete the wp-config.php file.</li>
<li> wp-admin folder;</li>
<li> wp-includes folder; If using a language file remember don&#8217;t delete the wp-includes/languages/ folder</li>
<li> wp-content/cache folder; You only see this folder if you are upgrading FROM WordPress 2.0.</li>
</ul>
<p><!--adsense#middle-post-ad--></p>
<p>After you have cleaned up like mentioned above you have to upload the WordPress 2.2 files to the server.</p>
<p style="text-align: center"><a href="http://pufone.org/blog/upgrading-to-wordpress-22/uploading-wordpress-22-files/" rel="attachment wp-att-30" title="Uploading WordPress 2.2 files" target="_blank"><img src="http://pufone.org/blog/wp-content/uploads/2007/05/uploading-wp-files-ftp.thumbnail.png" alt="Uploading WordPress 2.2 files" /></a></p>
<p>Now you need to run the Upgrade script by accessing  /wp-admin/upgrade.php and follow the simple steps.</p>
<p style="text-align: center; vertical-align: top"><a href="http://pufone.org/blog/upgrading-to-wordpress-22/wordpress-upgrade-script/" title="WordPress Upgrade script" rel="attachment wp-att-31" target="_blank"><img src="http://pufone.org/blog/wp-content/uploads/2007/05/wp-upgrade-script.thumbnail.png" alt="WordPress Upgrade script" /></a> =&gt; <a href="http://pufone.org/blog/upgrading-to-wordpress-22/wordpress-upgrade-script-complete/" target="_blank" rel="attachment wp-att-32" title="WordPress Upgrade script complete"><img src="http://pufone.org/blog/wp-content/uploads/2007/05/wp-upgrade-complete.thumbnail.png" alt="WordPress Upgrade script complete" /></a> =&gt; Tada! <a href="http://pufone.org/blog/upgrading-to-wordpress-22/pufone-after-upgrade/" rel="attachment wp-att-33" title="Pufone after Upgrade" target="_blank"><img src="http://pufone.org/blog/wp-content/uploads/2007/05/pufone-blog-after-upgrade.thumbnail.png" alt="Pufone after Upgrade" /></a></p>
<p>Login and check if it&#8217;s all good under the hood. Activate the Plugins, etc, etc&#8230;</p>
<p style="text-align: center"><a href="http://pufone.org/blog/upgrading-to-wordpress-22/activating-plugins/" target="_blank" rel="attachment wp-att-34" title="Activating Plugins"><img src="http://pufone.org/blog/wp-content/uploads/2007/05/wp-admin-activate-plugins.thumbnail.png" alt="Activating Plugins" /></a></p>
<p><!--adsense#middle-post-ad--></p>
<p><strong>Conclusion:</strong></p>
<ul>
<li>WordPress version 2.2 integrates widgets by default, without the need of  installing the automatic plugin. The AdSense manager from mutube doesn&#8217;t work correctly when using the widget ads. It doesn&#8217;t remember the specific ad settings(type, size, colour&#8230;) it just displays the default ad. This forced me to  remove the AdSense Widgets
<p style="text-align: center"><a href="http://pufone.org/blog/upgrading-to-wordpress-22/adsense-widget-problems/" rel="attachment wp-att-35" title="Adsense Widget Problems"><img src="http://pufone.org/blog/wp-content/uploads/2007/05/adsense-plugin-problems.thumbnail.png" alt="Adsense Widget Problems" /></a></p>
</li>
<li><strike>The Preview function is not available while writing posts.</strike> Writing this post has been difficult without it <img src='http://pufone.org/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  . Maybe it is turned off by default but i didn&#8217;t manage to find the setting. <strong>EDIT:</strong> The preview is displayed in a new window. There is a small preview link at the top of the writing page.</li>
<li>Overall i didn&#8217;t notice improvements, but i somehow feel better that i have the latest WordPress. Version 2.2 that is!</li>
</ul>
<p>You can find the official upgrading tutorial <a href="http://codex.wordpress.org/Upgrading_WordPress" rel="external nofollow" target="_blank" title="WordPress.org Upgrade Tutorial">here</a>. Good luck with your WordPress Upgrade!</p>
]]></content:encoded>
			<wfw:commentRss>http://pufone.org/blog/upgrading-to-wordpress-22/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
