Updating Wordpress Databasename

[Noturns]

I found out a easy way to update the Database name of a WP installation through phpmyadmin panel, However i can't seem to update or refresh the Parallels WP Settings with correct information. Is this a bug?

This is how to reproduce:

From phpMyAdmin select the database you want to select, in the tabs there's one called Operations, Go to the rename section.

Update the user privileges to the new Database name and remove the old privileges (save)
Then manually update the wp-config file which contains the 'Database name' (save)
Then goto Parallels Plesk > Websites & Domains> WordPress Installations > Change Settings
Here you should notice the Change Settings for the WordPress Installation still contains the old Database name.

Is there any way of updating this?
Looking forward in reading your replies

 

[IgorG]

You need to update database name in Plesk interface in Plesk database psa. But I strongly do not recommend you change something there. It can lead to database inconsistency and unpredictable consequences.
Why do you need change WP database names? What is your business case?

 

[Noturns]

Thanks for the reply.

I have installed 10-20 wordpress (small) websites on our hosting.
If we have more then 100 websites it would be very difficult to separate different DB names,
because Plesk random generates DB names like 'wordpress_a6' or 'wordpress_16'.

I have documented every websites corresponding to the database. However if my documentation is incorrect the database names in plesk would always be leading above my documentation.
If i want to know what DB corresponds to website. Then i would have to look at table_prefixes or view the table details.

That is why i want to reorganize and rename all DB names.

 

[KonstantinosS]

@Noturns I use custom installation for WP, and actually any app from Application Vault, and can enter manually the DB name, as well as the password. For your case, you can easily create a new DB, copy the data from the old DB to the new one, change the settings in WP configuration file to show the new DB's name, and then delete the old one. IF you're using WP Toolkit, just scan again for any WP installations to be on the safe side. You shouldn't have any issues with that method I'm suggesting.

 

[Noturns]

@KonstantinosS, thats a good suggestion. Thanks.
It would be nice dough, if the Database name field was not greyed out.

@igor, you where right. If the database name is changed through phpmyadmin. This leads to unpredictable consequences.

 

[KonstantinosS]

@KonstantinosS, thats a good suggestion. Thanks.
It would be nice dough, if the Database name field was not greyed out.

@igor, you where right. If the database name is changed through phpmyadmin. This leads to unpredictable consequences.

@Noturns, I don't see anything disabled in a custom installation through the App Vault.

Could you please post a screenshot of what's grayed out?

 

[Noturns]

It is only greyed out when the wordpress has already been created

 

[KonstantinosS]

It is only greyed out when the wordpress has already been created

Ok... Try changing wp_config.php settings for DB name and DB user (you can keep the same DB pass if you like) after you copy the current DB to the new DB name and create a new user for that new DB. Then re-scan for WP installations. It should work... I've transferred a few clients from a reseller that were WP sites, and WP Toolkit recognized the new sites instantly after scanning for WP installations.

 

[Noturns]

@KonstantinosS I think that i have successfully imported and updated the wp-config and checked with securtiy tool as you suggested.
What i actually meant was if you have setup a WP, you cannot alter the database name after it has been created.

However when i create a new WP with custom table prefix it still generates a new table prefix. Insted of the custom table prefix.
I can rename the table prefix to the original prefix with phpmyadmin, but i think this is not suppose to happen.

Here's an update: WP sites that contain %postname% permalinks are not linked any more. Maybe i have to do an wordpress export or something rather than a DB backup....

 

[KonstantinosS]

@KonstantinosS I think that i have successfully imported and updated the wp-config and checked with securtiy tool as you suggested.
What i actually meant was if you have setup a WP, you cannot alter the database name after it has been created.

@Noturns you shouldn't change the DB's name, what you should do is create a new db, copy the data from the previous DB to the new one, then change wp_config.php to link to the new DB. You can easily copy the data form one DB to another via Plesk.

However when i create a new WP with custom table prefix it still generates a new table prefix. Insted of the custom table prefix.
I can rename the table prefix to the original prefix with phpmyadmin, but i think this is not suppose to happen.

I'd suggest checking the KB for that prefix, otherwise, report it to Parallels tech support. Maybe it's a bug they haven't discovered yet. I've met one the other day in PBAS.

Here's an update: WP sites that contain %postname% permalinks are not linked any more. Maybe i have to do an wordpress export or something rather than a DB backup....

What do you mean with not linked any more??? Where should they be linked to? WP Toolkit? App Vault??? I always setup my WP sites with the /%postname%/ permalink, and never had any issues with plesk...

 

[Noturns]

Thanks, where can i report an issues by the way?

I think that one website had the permalink problem before i started.
Luckily in one website i could change the value into permalinks and it re-generated again.

 

[KonstantinosS]

Thanks, where can i report an issues by the way?

I think that one website had the permalink problem before i started.
Luckily in one website i could change the value into permalinks and it re-generated again.

I usually create a support request when I face an issue. If you've got a dedicated server license, I think support is free of charge if you enter your plesk key.

 

[UFHH01]

I usually create a support request when I face an issue. If you've got a dedicated server license, I think support is free of charge if you enter your plesk key.

This is only the case, when you directly purchase your licence over Parallels - in most cases, the server is rented in combination with a Plesk licence and you will get your primary support over your server-hosting company. Please read the full documentation about the different licences at: http://odin.com/hcap/support/