<?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>kwatog &#187; WordPress</title>
	<atom:link href="http://kwatog.com/tag/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://kwatog.com</link>
	<description>tech notes and general nonsense</description>
	<lastBuildDate>Thu, 29 Jul 2010 12:06:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Panglao WP</title>
		<link>http://kwatog.com/wp-themes/panglao-wp/</link>
		<comments>http://kwatog.com/wp-themes/panglao-wp/#comments</comments>
		<pubDate>Fri, 01 Jan 2010 14:32:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[WP Themes]]></category>
		<category><![CDATA[cufon]]></category>
		<category><![CDATA[lightword]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://kwatog.com/?p=193</guid>
		<description><![CDATA[It&#8217;s a modified version of the magnificent LightWord template by Andrei Luca More info to follow]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s a modified version of the magnificent <a href="http://www.lightword-theme.com/">LightWord</a> template by Andrei Luca </p>
<p>More info to follow</p>
]]></content:encoded>
			<wfw:commentRss>http://kwatog.com/wp-themes/panglao-wp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress : ‘You do not have sufficient permissions to access this page’</title>
		<link>http://kwatog.com/blog/wordpress/wordpress-you-do-not-have-sufficient-permissions-to-access-this-page/</link>
		<comments>http://kwatog.com/blog/wordpress/wordpress-you-do-not-have-sufficient-permissions-to-access-this-page/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 10:24:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[access this page]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[insufficient permissions]]></category>
		<category><![CDATA[plugins]]></category>

		<guid isPermaLink="false">http://kwatog.com/?p=175</guid>
		<description><![CDATA[The problem looks like below. You do not have sufficient permissions to access this page The supposed permission problem has occured before and mainly involves plugins. For older version of wordpress, your problem may be solved by one or both of the Change of table prefix - I suggest you visit this to solve that [...]]]></description>
			<content:encoded><![CDATA[<p>The problem looks like below.</p>
<blockquote><p>
You do not have sufficient permissions to access this page
</p></blockquote>
<p>The supposed permission problem has occured before and mainly involves plugins. For older version of wordpress, your problem may be solved by one or both of the </p>
<ul>
<li><strong>Change of table prefix -</strong> I suggest you visit <a href="http://beconfused.com/2007/08/28/how-to-solve-you-do-not-have-sufficient-permissions-to-access-this-page-in-wordpress/">this</a> to solve that problem. And it also solves a string of other things, too.
</li>
<li><strong>Failed Upgrade -</strong> If you used an automatic upgrade and failed, it is possible that the version number saved in the database is already updated. You can force upgrade it by updating the your version number. Another alternative is by using MarkAquit&#8217;s script <a href="http://markjaquith.wordpress.com/2006/03/28/wordpress-error-you-do-not-have-sufficient-permissions-to-access-this-page/">here</a></li>
</ul>
<p>However, these solutions are only applicable for older versions of WordPress. If you have a clean install, you should not encounter this. That&#8217;s why it didn&#8217;t work and was back to square one of investigation. Upon further checking, it turned out that the problem is related to old plugins. Apparently, there are plugins that was written before the current releases and whose parts of the code is no longer compliant with the current version of WordPress. </p>
<p>Finding the offending plugin is a bit tricky especially if you are using a lot of plugins. Luckily, I only encounter this in a contact page plugin and replace it accordingly with a new plugin which was released lately. The problem with my older plugin is that there&#8217;s no more active development. And so when some of the codes were deprecated, the plugin fails.</p>
<p>So what&#8217;s the problem then? Old Plugins. </p>
]]></content:encoded>
			<wfw:commentRss>http://kwatog.com/blog/wordpress/wordpress-you-do-not-have-sufficient-permissions-to-access-this-page/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rename Tables in MySQL</title>
		<link>http://kwatog.com/blog/mysql/rename-tables-in-mysql/</link>
		<comments>http://kwatog.com/blog/mysql/rename-tables-in-mysql/#comments</comments>
		<pubDate>Sun, 23 Aug 2009 02:20:15 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[phpMyAdmin]]></category>
		<category><![CDATA[rename]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[wordpress mu]]></category>

		<guid isPermaLink="false">http://kwatog.com/?p=121</guid>
		<description><![CDATA[If you want to hand code renaming tables, here&#8217;s the sample. Single Table RENAME TABLE wp_users TO kwg_users; multiple tables RENAME TABLE wp_users TO kwtg_users, wp_usermeta TO kwtg_usermeta, wp_site TO kwtg_wpsite, wp_signups TO kwtg_signups; This is handy when renaming a whole lot of tables as in the case of WordPress mu where each blog has [...]]]></description>
			<content:encoded><![CDATA[<p>If you want to hand code renaming tables, here&#8217;s the sample. </p>
<p><strong>Single Table</strong><br />
<code><br />
RENAME TABLE wp_users  TO kwg_users;<br />
</code></p>
<p><strong>multiple tables</strong><br />
<code><br />
RENAME TABLE wp_users  TO kwtg_users,<br />
                     wp_usermeta TO kwtg_usermeta,<br />
                     wp_site TO kwtg_wpsite,<br />
                     wp_signups TO kwtg_signups;<br />
</code></p>
<p>This is handy when renaming a whole lot of tables as in the case of <strong>WordPress mu</strong> where each blog has its own set of tables. If you decide to rename them for security reasons (like you forgot to change the default table prefix during installation), it will be a pain to change them one by one through <strong>phpMyAdmin</strong>.</p>
]]></content:encoded>
			<wfw:commentRss>http://kwatog.com/blog/mysql/rename-tables-in-mysql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Modified WP Table Prefix in bbPress</title>
		<link>http://kwatog.com/blog/uncategorized/modified-wp-table-prefix-in-bbpress/</link>
		<comments>http://kwatog.com/blog/uncategorized/modified-wp-table-prefix-in-bbpress/#comments</comments>
		<pubDate>Sun, 23 Aug 2009 02:13:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bbpress]]></category>
		<category><![CDATA[table prefix]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[wordpress mu]]></category>

		<guid isPermaLink="false">http://kwatog.com/?p=119</guid>
		<description><![CDATA[If you change your WordPress/WordPress mu table prefix (and thus, renamed the tables too) and you have a bbPress integrated with it, chances are your bbPress will lose its connection with WordPress since the configuration is not in bb-config.php. You&#8217;ll need to update the meta tables, too through mysql or phpmyadmin. Here&#8217;s the update query. [...]]]></description>
			<content:encoded><![CDATA[<p>If you change your WordPress/WordPress mu table prefix (and thus, renamed the tables too) and you have a bbPress integrated with it, chances are your bbPress will lose its connection with WordPress since the configuration is not in bb-config.php. You&#8217;ll need to update the meta tables, too through mysql or phpmyadmin. Here&#8217;s the update query.</p>
<p><code><br />
UPDATE bb_meta<br />
SET meta_value = 'wpmu_'<br />
WHERE meta_key = 'wp_table_prefix';<br />
</code></p>
<p>That&#8217;s of course considering your bbPress table is bb_meta and the new prefix for WordPress/WordPress mu is <strong>wpmu</strong>.</p>
]]></content:encoded>
			<wfw:commentRss>http://kwatog.com/blog/uncategorized/modified-wp-table-prefix-in-bbpress/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WordPress Upgrade Error(wp-comments)</title>
		<link>http://kwatog.com/blog/wordpress/wordpress-upgrade-errorwp-comments/</link>
		<comments>http://kwatog.com/blog/wordpress/wordpress-upgrade-errorwp-comments/#comments</comments>
		<pubDate>Sun, 16 Aug 2009 17:07:25 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[wp-comments]]></category>

		<guid isPermaLink="false">http://kwatog.com/?p=107</guid>
		<description><![CDATA[I&#8217;ve been encountering this for a number of times already and on each time, I had to upgrade WordPress manually(through SSH to make it faster). Now, I was able to partially solve this by removing/renaming the existing upgrade folder under wp-contents. You can follow the steps below. Login to your server via FTP navigate to [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been encountering this for a number of times already and on each time, I had to upgrade WordPress manually(through SSH to make it faster). Now, I was able to partially solve this by removing/renaming the existing upgrade folder under wp-contents. You can follow the steps below.</p>
<ol>
<li>Login to your server via FTP</li>
<li>navigate to <strong>wp-contents</strong> folder</li>
<li>rename the existing <strong>upgrade </strong>folder to a new name(you can also choose to delete)</li>
<li>under wp-contents folder, create a new folder named <strong>upgrade</strong></li>
<li>set permission of the new upgrade folder to 666</li>
<li>re-run the upgrade from within wordpress</li>
</ol>
<p><span id="more-107"></span><br />
The one thing that I noticed in this problem is the fact that it only happens on my WordPress installations on VPS. All other sites sitting on a shared cpanel-powered hosting do not encounter this. So there must be something wrong with my VPS configuration. </p>
<p>I&#8217;ll need to find that out because there&#8217;s still one annoying step that needs to be done before upgrading a WP installation. If you have over a dozen sites to update and they are sitting on different servers, it becomes an issue. A one-click solution would be most welcome.</p>
<p>Do you have any idea how I would be able to solve this?</p>
]]></content:encoded>
			<wfw:commentRss>http://kwatog.com/blog/wordpress/wordpress-upgrade-errorwp-comments/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
