Comments on: Security Check – WordPress table prefix change adds more security

By: John

John — Tue, 03 Aug 2010 18:32:46 +0000

Thank you Mayank. Sound advice!

By: mayank

mayank — Mon, 02 Aug 2010 09:55:08 +0000

John most of the plugins will work, however it’ll make more sense if you can create the clone of your wordpress setup and test it. I would never suggest you to do it on production environment directly. Normally most of the plugins just take the setting as you change the database.

By: John

John — Sat, 31 Jul 2010 13:45:38 +0000

Thanks for the great post. I’d like to change the table prefix and I take Sherif’s point that future plugins should automatically find the new prefix, but my question is what happens to all the existing plugins – do that auto update or need re-installing to pick up the new prefix? Many Thanks.

By: links for 2009-06-29 at So It’s Come To This:

links for 2009-06-29 at So It’s Come To This: — Tue, 30 Jun 2009 05:07:24 +0000

[...] Security Check – WordPress table prefix change adds more security | Blog Design Studio (tags: wordpress security Database code) [...]

By: mayank

mayank — Tue, 26 May 2009 08:11:10 +0000

@shivaranjan – Thanks for taking up this point. I wasn’t even sure about it. I think Sherif’s point is right and should fix up things.

@sherif – why don’t you share the plugin with us, I will definitely write about it :)

By: Sherif

Sherif — Fri, 22 May 2009 11:53:01 +0000

Thanks for writing. I think that the table prefix change is the best security defense among all security measures you can take.

Shivaranjan, my wp-backup works and any plugin should work as it pick the prefix automatically.
If you have issues, let me know. I can find my backup plugin and share it with you.

Regards.

By: Shivaranjan

Shivaranjan — Thu, 21 May 2009 11:11:33 +0000

If we change the table prefix the security will be improved but if we are using some plugins like Wp-backup that rely on default tables then those plugins will not work. May be we have to then change the code of the plugin to match the new table prefix so we should be careful about upgrading plugins directly from dashboard instead we should download the new version of the plugin and then change the code to reflect the new table prefix. Correct me if i got something wrong?