Custom Database Table Prefix Not Allowed?

  • I’ve had my website for several years but have only recently tried to sit down and really understand WordPress. I’m working through a book called The Tao of WordPress by Jeff Starr and it recommends customizing the Database Table Prefix in the wp-config file.

    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

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)

  • Hi @greentub

    On bluehost you’ll most likely need to login to phpmy admin and update the names of the database tables.

    https://www.bluehost.com/help/article/managing-your-db-using-phpmyadmin

    Even tho this article is hostgator, it still might help you to rename the tables within phpmyadmin:
    https://www.hostgator.com/help/article/how-to-rename-database-tables-in-phpmyadmin

    lisa

    (@contentiskey)

    also, check in your wp-config.php file to see what $table_prefix is displayed

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Really, if you have only one WP site installed on that database, there’s no advantage to changing the prefix.

    Changing the prefix is fine, but it typically has to be updated in several places like the database and wp-config. If you’re getting an installation prompt, then you’ve most likely missed one of the locations. Also, be sure to make regular backups first in case you accidentally mess something up.

    If your host offers something like cPanel, then you might be able to change them all at once with one of its management apps like Softaculous.

    In terms of security, changing the database prefix to something obscure might theoretically block some poorly automated attacks, but it’s not very likely to help much. You would be much better off using a combination of strong passwords (especially for admins and editors), keeping your plugins/theme/core up to date, replacing unmaintained plugins, and setting up security software like WordFence and Cloudflare.

    Hi Jonathan and thanks for reaching out! Bluehost does allow for the modification of the database prefix, however, other modifications need to be made in order for it to work with your site. Additional modification of the database tables to correct the prefixes would also be necessary along with anywhere else it may appear in your site files. As Evan had mentioned earlier in this thread, databases can be managed through the PHPmyadmin tool. This article has more information on that:

    https://www.bluehost.com/help/article/managing-your-db-using-phpmyadmin

    This is out of our scope of support so we would recommend consulting a developer for any additional guidance with website development. As far as Bluehost goes though, there should not be any restrictions on your hosting to prevent these changes. Support would likely be unable to recommend the edits due to the chance of something going wrong to the point that would require developer intervention. Support is however available to try and answer any hosting related questions you may have here:

    https://www.bluehost.com/contact

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Custom Database Table Prefix Not Allowed?’ is closed to new replies.