We are excited to release Version 1.1 of the WP Prefix Changer.
This plugin will allow you to change your database table prefix to mitigate new and automated vulnerabilities that attackers may use to gain access to your blog. Although not recommended, it can also be used in shared hosting environments where a user is only permitted one database and has multiple WordPress installs.
Changelog:
- Correctly sanitises table prefix input
- Additional checks are performed before modifying the wp-config.php file.
- MySQL user access is checked before proceeding with the prefix change.
- You get a Security Notice if your MySQL-User has ALL Privileges.
After receiving some error reports, we have confirmed the plugin is working on the following WP versions, 2.0.11 and 2.3.
We hope the new version will address past concerns and provide a more stable experience.
If you get some Error please Report it to us, as detailed as possible(WP version, Plugins, Template, Core changes, …). And we’ll try to track the error down.
Download the latest version (1.1) of WP Table Prefix Changer
[...] might want to check a plugin to do it, but I had problems with it and prefer the manual way as I will shown [...]
[...] WP Prefix Table Changer plugin is the great one. This tool will automatically change the default database table prefix to [...]
I went through the Table Prefix Change plug-in, am running WP 2.3.1 currently. Here’s the error message:
WordPress database error: [There is no such grant defined for user 'User' on host 'host']
SHOW GRANTS FOR ‘user’@'host’
Warning: Invalid argument supplied for foreach() in /Path/wp-content/plugins/prefix-changer.php on line 48
Your User which is used to access your Wordpress Tables/Database, hasn’t enough rights( is missing ALTER-right) to alter your Tablestructure.
I’m working on a new Version which hopefully solves much of these problems, although that you report something knew.
do i need to change another wp_ prefix in my database (some plugins using wp_ prefix too), besides like that was mentioned in Secure WP Whitepaper (pdf)?
Necessary I in place of wp prefix that was other,
If you use the Plugin it will do everything for you(except some potential hardcoded prefixes within the Plugintable structure). Anyway if you change the prefix manually you have to rename all tables from your previous prefix(mostly wp_) to your new one, in order to grant that your blog is fully functional after the change.
i’m still not yet understand about what your talking about “If you use the Plugin it will do everything for you”.
can you give more explanation?
If you use the Plugin and everything is setup correctly, the Plugin will rename all your WP tables to the latest prefix, all known hardcoded values which includes the prefix will be changed as well automatically. And your Config is changed although(if it has write permission for your Webserver, and afterwards we try to chmod your Config in such a way that it stays secure.
So the Plugin does all the work, you would have normally to do If you would follow our whitepaper.
Ever since I installed the prefix changer and got the error message above, I have had problems with loading my blog page. The browser just hangs, completed 13 out of 14 items, although if I cancel the page loading the blog reads just fine.
I can’t figure out what might have changed based on that one attempt to run your plug-in, but I’m wondering whether just reinstalling wp 2.3.1 will fix the problem.
Reading the activity log on my browser, it looks like it gets hung up just after accessing http://www.wp-stats-php.info/iframe/wpstats.php
Then it goes to which is where it times out. Any help sorting this out would be much appreciated.
Anne, like Philip said, he working on a new stable version of this tool, so be patient.
And as for your wp tables, have you rename all your primary WP tables manually? … or perhaps you doesn’t rename the right table?. Btw, not a little bit of WP folks which is not know that the primary WP prefix table like has mentioned on the secure WP whitepaper is only there’s on WP lower than 2.3.1 ! WP 2.3.1 doesn’t using some tables like mentioned over there, e.g. wp_categories, wp_link2cat, and wp_post2cat table. And in my experience, the wp_mt_tags must be renamed too! why? .. of course, to broke of an error which i get.
Perhaps my simple writings on my *lamme* blog can help you » http://aufklarung.org/computer/primary-tables-of-wp-231-which-must-be-renamed.mspx
[...] Natürlich gibt es auch für diese Arbeit ein Plugin, welches einem Anwender die Arbeit erleichtert und die Ändern schnell durchführt: WP Prefix Table Changer. [...]
[...] Rename your wordpress database prefixes. You don’t want people attacking your site just because they know you have the default info installed. This site here has the best instructions yet if you can’t get it to be changed automatically. [...]
Question:
Does plugin work with WordPress v. 2.5 too?
[...] the database table names. Wordpress allows for alternative database table names. There are several table prefix plugins which will do this for you, or you can follow manual instructions. Do note you may have problems [...]
[...] nel database. Wordpress consente nomi alternativi per le tabelle del database. Ci sono diversi plugin per definire il prefisso delle tabelle che faranno questo per te, oppure è possibile seguire le istruzioni manuali. È da notare [...]
[...] I would recommend going ahead and changing the table prefix. BlogSecurity.net has a plugin to make changing the Wordpress table prefix much [...]