When I changed the prefix from “wp_” to “jkr_wp_” and checked my site, some pages rerouted to an installation page, asking me to install WordPress.
I contacted my server (bluehost) about it and was told that I can’t change the prefix because it is “on the database table.” I reverted the prefix back to “wp_” and the site works fine.
The book suggests that changing the prefix tightens the security and I’ve seen other articles online about doing this. Is it true that I can’t on bluehost?
Thanks,
Jonathan
Look at this
but in my wp-config
I do not remember I added the prefix 2f0857 to my dbs
The site is working fine . How come in my phpmy admin I have 2f0857_ ?
]]>Please take it out of the report
]]>When I update the ‘wp_’ prefix in the database (the table names and also records in the *_usermeta and the *_options tables) and wp-config.php to harden my site, I no longer have permission to log in. When I return the prefix to ‘wp_’, then I can log in.
I tested this this morning on a fresh installation of Core and the Seedlet theme, and received the same error message. When I returned the prefix to ‘wp_’, I could log in.
I’ve updated the database prefix in other themes with no issues. Is there something specific to updating Seedlet?
Guidance appreciated. =)
]]>And as I see via the Cron daemon log it has daily events there which don’t run because the plugin is missing.
I suspect it is “statistics” but would like to be sure.
So I want to drop the old tables and make a clean new installation because I like all Your plugins.
]]>The issue here is that ?User Registration? add a prefix with ‘user_registration_{$field_name}’, in my case the final name of field was ‘user_registration_user_phone’. Is there a way to disable or override this prefix with an empty string to connect the form field with the one I created?
]]>