To be clear, here’s the screenshot on how to do it.
Step 1 : click on 2 in the Number of Columns Screen options.

Step 2 : Update the status to Live and click on Save.

For those looking for it, I know how you feel. I just felt too stupid to not thinking about it. Admittedly, it’s probably one of the many plugins affected by the latest WordPress enhancements. I bet once rich updated the plugin to conform with the new standard, then it won’t be a problem anymore.

Source:

http://quirm.net/forum/topic.php?id=4716

Incoming search terms:

• eshop test mode
• disable eshop test mode
• disable test mode eshop
• eshop in test mode
• eshop turn off the test mode
• test mode eshop plugin

Step 1

Suppose that you want mod as your new table prefix, run the following in your phpMyAdmin.

RENAME TABLE wp_commentmeta TO mod_commentmeta
,wp_comments TO mod_comments
,wp_links TO mod_links
,wp_options TO mod_options
,wp_postmeta TO mod_postmeta
,wp_posts TO mod_posts
,wp_terms TO mod_terms
,wp_term_relationships TO mod_term_relationships
,wp_term_taxonomy TO mod_term_taxonomy
,wp_usermeta TO mod_usermeta
,wp_users TO mod_users;


Step 2


UPDATE `mod_options`
SET `option_name` = 'mod_user_roles'
WHERE `option_name` ='wp_user_roles'
AND `blog_id` =0;


Step 3


UPDATE `mod_usermeta`
SET `meta_key` = REPLACE( `meta_key` , 'wp_', 'mod_' )
WHERE option_name LIKE 'wp_%';

The preceding two steps are needed because in the later versions of WordPress, some tables are converted to records. Skipping these two steps will lead to permission error. To be specific, the error is as below.

You do not have sufficient permissions to access this page.

Hmn… well, that’s just it.

Usual Disclaimer

Renaming your table doesn’t mean that you’ll be safe from the bad guys (otherwise known as ‘hackers’). It’s just one of the holes to plug and will only help in hardening your installation. However, be aware that there could be other things that can break or compromised. So be vigilant and always install the latest version of WordPress.

Incoming search terms:

• table prefix home pl
• wordpress tagged with prefix

More info to follow

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 problem. And it also solves a string of other things, too.
• Failed Upgrade - 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’s script here

However, these solutions are only applicable for older versions of WordPress. If you have a clean install, you should not encounter this. That’s why it didn’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.

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’s no more active development. And so when some of the codes were deprecated, the plugin fails.

So what’s the problem then? Old Plugins.

Incoming search terms:

• wordpress plugins You do not have sufficient permissions to access this page

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 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 phpMyAdmin.

Incoming search terms:

• mysql rename table recursively
• rename multiple tables mysql
• rename table in mysql
• rinomina wp-posts in my sql


UPDATE bb_meta
SET meta_value = 'wpmu_'
WHERE meta_key = 'wp_table_prefix';


That’s of course considering your bbPress table is bb_meta and the new prefix for WordPress/WordPress mu is wpmu.

1. Login to your server via FTP
2. navigate to wp-contents folder
3. rename the existing upgrade folder to a new name(you can also choose to delete)
4. under wp-contents folder, create a new folder named upgrade
5. set permission of the new upgrade folder to 666
6. re-run the upgrade from within wordpress

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.

I’ll need to find that out because there’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.

Do you have any idea how I would be able to solve this?

But with the rise in popularity of WordPress, it has evolved in a more robust application framework where you can build your application on. It still lacks a lot of features other CMS have but it has all the important ones. It has become an increasingly flexible framework where you can build your application on. And with the help of talented template designers, has moved the presentation of WordPress sites even higher. And despite its improved capabilities, WordPress still managed to maintain improve it’s uberly simplistic and almost idiot-proof administration interface.

I think a post over at graduallythensuddenly.com on “WordPress Makes Drupal Irrelevant” explains it further. And if you want to make your application adhere to the MVC(model-view-controller) framework, somebody has just explained how to do it over at nixonmcinnes.co.uk.

And as for me, is it time for me to use WordPress on that web application that I’ve been postponing for the longest time? You bet, it is! And as a matter of fact, I should have started earlier. Actually, I already migrated one custom-script-powered website into wordpress over the weekend out of necessity.

But this decision to migrate to WordPress doesn’t mean I’ll be dumping Joomla altogether. I’ll still use Joomla and will still be my choice for full-cms and complex website for the time being. However when it comes simple blogsite to magazine type websites, WordPress is the way. And one of the added indispensable bonus is the ease of administration. It’s so damn simple, it’s almost idiot proof.

Incoming search terms:

• wordpress application framework
• wordpress as an application framework
• wordpress as application framework
• use wordpress as application framework