<?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>Knowledge Sharing &#187; Upgrade</title>
	<atom:link href="http://blog.danigunawan.com/tag/upgrade/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.danigunawan.com</link>
	<description>"Say it... although a word..."</description>
	<lastBuildDate>Mon, 04 Jan 2010 10:17:12 +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>Fixing WordPress 2.9 Upgrade Error</title>
		<link>http://blog.danigunawan.com/tips-and-trick/fixing-wordpress-2-9-upgrade-error/</link>
		<comments>http://blog.danigunawan.com/tips-and-trick/fixing-wordpress-2-9-upgrade-error/#comments</comments>
		<pubDate>Mon, 04 Jan 2010 10:17:12 +0000</pubDate>
		<dc:creator>Dagu</dc:creator>
				<category><![CDATA[Tips and Trick]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[Error]]></category>
		<category><![CDATA[patch]]></category>
		<category><![CDATA[Upgrade]]></category>

		<guid isPermaLink="false">http://blog.danigunawan.com/?p=612</guid>
		<description><![CDATA[I&#8217;ve experienced a problem while upgrading to Wordpress 2.9 a few days ago. My blog didn&#8217;t show the RSS widget. Some error are found in my dashboard also.

So, I started searching on the Internet how to solve my problem. And finally I found that there are some bugs in WordPress 2.9. They are:
Bug tersebut adalah:

Major [...]


Related posts:<ol><li><a href='http://blog.danigunawan.com/tips-and-trick/wordpress-error-after-automatic-upgrading/' rel='bookmark' title='Permanent Link: WordPress Error After Automatic Upgrading'>WordPress Error After Automatic Upgrading</a></li>
<li><a href='http://blog.danigunawan.com/tips-and-trick/wordpress-error-open_basedir-restriction-in-effect/' rel='bookmark' title='Permanent Link: Wordpress Error: open_basedir restriction in effect'>Wordpress Error: open_basedir restriction in effect</a></li>
<li><a href='http://blog.danigunawan.com/review/wordpress-2-8-review/' rel='bookmark' title='Permanent Link: WordPress 2.8 Review'>WordPress 2.8 Review</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve experienced a problem while upgrading to Wordpress 2.9 a few days ago. My blog didn&#8217;t show the RSS widget. Some error are found in my dashboard also.</p>
<p style="text-align: center;"><img class="aligncenter" title="Wordpress 2.9 Error" src="http://danigunawan.com/wp-content/uploads/2010/01/curl_setopt.jpg" alt="curl set opt" width="400" height="51" /></p>
<p>So, I started searching on the Internet how to solve my problem. And finally I found that there are some bugs in WordPress 2.9. They are:</p>
<p>Bug tersebut adalah:</p>
<ul>
<li><a title="major bug wordpress 2.9" href="http://core.trac.wordpress.org/ticket/11219" target="_blank">Major bug</a> was simply dismissed</li>
<li><a title="a related critical bug" href="http://core.trac.wordpress.org/ticket/11168" target="_blank">A related critical bug</a> was only <a title="partially fixed" href="http://core.trac.wordpress.org/ticket/11518" target="_blank">partially fixed</a>)</li>
<li><a title="a last critical bug" href="http://core.trac.wordpress.org/ticket/11505" target="_blank">A last critical bug</a> (and its <a title="child bug" href="http://core.trac.wordpress.org/ticket/11499" target="_blank">child bug</a>) crept in <a title="last" href="http://core.trac.wordpress.org/changeset/12424" target="_blank">at the last moment</a></li>
</ul>
<p>As a result of this:</p>
<ul>
<li>RSS widgets are completely broken on servers that are missing both of iconv and multi-byte string functions;</li>
<li>The curl transport is broken on some servers with an outdated library. This breaks the WP cron, and with it future posting, pings, etc.</li>
</ul>
<p>Not all sites are affected, of course. Most aren&#8217;t, in fact. But for those few who are, the situation is frustrating.</p>
<p>To solve this problem, you need to follow this steps:</p>
<p>1. Download this patch (from semiologic.com):</p>
<p><a title="wordpress 2.9 patch" href="http://danigunawan.com/wp-content/uploads/2010/01/wp-2.9-patch.zip" target="_blank">WordPress 2.9 Patch</a></p>
<p>2. Extract all files (class-simplepie.php, default-widgets.php, http.php) to <strong>wp-includes</strong> directory. Replace the old files with the patch files.</p>
<p>3. Done…</p>
<p>Good luck… :)</p>


<p>Related posts:<ol><li><a href='http://blog.danigunawan.com/tips-and-trick/wordpress-error-after-automatic-upgrading/' rel='bookmark' title='Permanent Link: WordPress Error After Automatic Upgrading'>WordPress Error After Automatic Upgrading</a></li>
<li><a href='http://blog.danigunawan.com/tips-and-trick/wordpress-error-open_basedir-restriction-in-effect/' rel='bookmark' title='Permanent Link: Wordpress Error: open_basedir restriction in effect'>Wordpress Error: open_basedir restriction in effect</a></li>
<li><a href='http://blog.danigunawan.com/review/wordpress-2-8-review/' rel='bookmark' title='Permanent Link: WordPress 2.8 Review'>WordPress 2.8 Review</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://blog.danigunawan.com/tips-and-trick/fixing-wordpress-2-9-upgrade-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New Release of Joomla 1.5.12</title>
		<link>http://blog.danigunawan.com/web/new-release-of-joomla-1-5-12/</link>
		<comments>http://blog.danigunawan.com/web/new-release-of-joomla-1-5-12/#comments</comments>
		<pubDate>Fri, 03 Jul 2009 12:38:36 +0000</pubDate>
		<dc:creator>Dagu</dc:creator>
				<category><![CDATA[Joomla]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[CMS]]></category>
		<category><![CDATA[Release]]></category>
		<category><![CDATA[Update]]></category>
		<category><![CDATA[Upgrade]]></category>

		<guid isPermaLink="false">http://blog.danigunawan.com/?p=561</guid>
		<description><![CDATA[From the Joomla Security newsletter, I know that there&#8217;s a new version of Joomla. But, my email provider sent it to spam folder. I just don&#8217;t know why.. huff.. :(
From the official Joomla website:
The Joomla Project is pleased to announce the immediate availability of Joomla 1.5.12 [Wojmamni Ama Woi]. This release contains a number of [...]


Related posts:<ol><li><a href='http://blog.danigunawan.com/cms-joomla/joomla-1-5-13-security-release/' rel='bookmark' title='Permanent Link: Joomla 1.5.13 Security Release'>Joomla 1.5.13 Security Release</a></li>
<li><a href='http://blog.danigunawan.com/cms/joomla-in-the-future/' rel='bookmark' title='Permanent Link: Joomla in the Future'>Joomla in the Future</a></li>
<li><a href='http://blog.danigunawan.com/review/joomla-won-best-cms-award-again/' rel='bookmark' title='Permanent Link: Joomla! Won &quot;Best CMS Award&quot; (Again)'>Joomla! Won &quot;Best CMS Award&quot; (Again)</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>From the <strong>Joomla Security </strong>newsletter, I know that there&#8217;s a new version of Joomla. But, my email provider sent it to spam folder. I just don&#8217;t know why.. huff.. :(</p>
<p>From the official <a title="Joomla!" href="http://www.joomla.org" target="_blank">Joomla</a> website:</p>
<blockquote><p>The Joomla Project is pleased to announce the immediate availability of Joomla 1.5.12 [Wojmamni Ama Woi]. This release contains a number of bug fixes and three moderate-level security fixes. It has been less than a month since <a href="http://www.joomla.org/announcements/release-news/5235-joomla-1511-security-release-now-available.html" target="_blank">Joomla 1.5.11</a> was released on June 3, 2009.</p>
<p>This release marks an important milestone for the Joomla Project due to the upgrade of the PEAR library to the new BSD licensed version, which brings the codebase into full compliance with the GPL. In addition, this release contains an important upgrade to TinyMCE v 3.2.4.1.</p>
<p>The Production Working Group&#8217;s goal is to continue to provide regular, frequent updates to the Joomla community.</p></blockquote>
<p><a href="http://joomlacode.org/gf/download/frsrelease/10547/41305/Joomla_1.5.12-Stable-Full_Package.zip">Download Joomla 1.5.12 (Full package)</a><br />
<a href="http://joomlacode.org/gf/download/frsrelease/10548/41314/Joomla_1.5.11_to_1.5.12-Stable-Patch_Package.zip">Download Joomla 1.5.11 &gt; 1.5.12 update package</a><br />
<a href="http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseView&amp;release_id=10548" target="_blank">All 1.5.12 Packages</a></p>


<p>Related posts:<ol><li><a href='http://blog.danigunawan.com/cms-joomla/joomla-1-5-13-security-release/' rel='bookmark' title='Permanent Link: Joomla 1.5.13 Security Release'>Joomla 1.5.13 Security Release</a></li>
<li><a href='http://blog.danigunawan.com/cms/joomla-in-the-future/' rel='bookmark' title='Permanent Link: Joomla in the Future'>Joomla in the Future</a></li>
<li><a href='http://blog.danigunawan.com/review/joomla-won-best-cms-award-again/' rel='bookmark' title='Permanent Link: Joomla! Won &quot;Best CMS Award&quot; (Again)'>Joomla! Won &quot;Best CMS Award&quot; (Again)</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://blog.danigunawan.com/web/new-release-of-joomla-1-5-12/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Error After Automatic Upgrading</title>
		<link>http://blog.danigunawan.com/tips-and-trick/wordpress-error-after-automatic-upgrading/</link>
		<comments>http://blog.danigunawan.com/tips-and-trick/wordpress-error-after-automatic-upgrading/#comments</comments>
		<pubDate>Mon, 15 Jun 2009 12:24:36 +0000</pubDate>
		<dc:creator>Dagu</dc:creator>
				<category><![CDATA[Tips and Trick]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[Error]]></category>
		<category><![CDATA[Maintenance]]></category>
		<category><![CDATA[Upgrade]]></category>

		<guid isPermaLink="false">http://blog.danigunawan.com/?p=559</guid>
		<description><![CDATA[Briefly unavailable for scheduled maintenance. Check back in a minute.
Got that message? And you can&#8217;t view your blog neither login to admin area? And now you wish you didn&#8217;t click automatic upgrade link? No need to worry, we will fix it.
Before we fix it, we shoud know what is going on? WordPress, like other systems, [...]


Related posts:<ol><li><a href='http://blog.danigunawan.com/tips-and-trick/wordpress-error-open_basedir-restriction-in-effect/' rel='bookmark' title='Permanent Link: Wordpress Error: open_basedir restriction in effect'>Wordpress Error: open_basedir restriction in effect</a></li>
<li><a href='http://blog.danigunawan.com/wordpress/wordpress-org-releases-2-8-beta-1/' rel='bookmark' title='Permanent Link: WordPress.org Releases 2.8 Beta 1'>WordPress.org Releases 2.8 Beta 1</a></li>
<li><a href='http://blog.danigunawan.com/review/wordpress-2-8-review/' rel='bookmark' title='Permanent Link: WordPress 2.8 Review'>WordPress 2.8 Review</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<blockquote><p>Briefly unavailable for scheduled maintenance. Check back in a minute.</p></blockquote>
<p>Got that message? And you can&#8217;t view your blog neither login to admin area? And now you wish you didn&#8217;t click automatic upgrade link? No need to worry, we will fix it.</p>
<p>Before we fix it, we shoud know what is going on? <a title="wordpress 2.8" href="http://blog.danigunawan.com/review/wordpress-2-8-review/" target="_blank">WordPress</a>, like other systems, is not perfect. Eventough it has automatic upgrade, it doesn&#8217;t mean your wordpress installation will always successfully upgraded using automatic upgrade. That&#8217;s why we should back up our blog before upgrading it. So, why that message appear? Does it mean our installation failed? Maybe. WordPress creates a file named <strong>.maintenance</strong> before upgrading process. Just in case there are visitors accessing your blog during upgrading process, they will see &#8220;<strong>Briefly unavailable for scheduled maintenance. Check back in a minute.</strong>&#8221; message instead of your under-upgrading blog. Somehow, I don&#8217;t know exactly why, the file .maintenance is not deleted by WordPress. If this thing happens, you will see maintenance message.</p>
<p>So, how to fix it? It&#8217;s a piece of cake. Login to your web host using CPanel or SSH, remove the .maintenance file. You can find that file in your <span style="text-decoration: underline;">WordPress installation directory</span> (<strong>the directory that has wp-admin directory</strong> &#8211; <span style="color: #ff0000;"><strong>not inside wp-admin directory</strong></span>). After you do it, refresh your blog. We hope your blog will be back&#8230; :)</p>
<p><strong>Question:</strong> I can&#8217;t see .maintenance file<br />
<strong>Answer: </strong>Yes, it&#8217;s a hidden file. If you are using SSH try <strong>ls -a </strong>command. If you use CPanel, don&#8217;t forget to check <strong>show hidden files</strong> while opening your installation directory using file manager.</p>


<p>Related posts:<ol><li><a href='http://blog.danigunawan.com/tips-and-trick/wordpress-error-open_basedir-restriction-in-effect/' rel='bookmark' title='Permanent Link: Wordpress Error: open_basedir restriction in effect'>Wordpress Error: open_basedir restriction in effect</a></li>
<li><a href='http://blog.danigunawan.com/wordpress/wordpress-org-releases-2-8-beta-1/' rel='bookmark' title='Permanent Link: WordPress.org Releases 2.8 Beta 1'>WordPress.org Releases 2.8 Beta 1</a></li>
<li><a href='http://blog.danigunawan.com/review/wordpress-2-8-review/' rel='bookmark' title='Permanent Link: WordPress 2.8 Review'>WordPress 2.8 Review</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://blog.danigunawan.com/tips-and-trick/wordpress-error-after-automatic-upgrading/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
