Thanks for adding that protection in v64.
I just ran into the backup failure again this morning due to a database being renamed in PHPMyAdmin (PMA). I am curious about this: Why are we letting 1 user take down a whole server with settings that are known to conflict? PMA is an excellent and dare I say essential tool for many users, but if it's so easy to conflict with cPanel -- risky to allow.
If database schema inconsistency is causing such an issue with backup corruption, why are those features even allowed in PMA? For example, there is no way to manage users in the cPanel build of PMA, the tab is completely gone, I assume in order to prevent collisions with the cPanel DB system/API. While using PMA in domain/account level cPanel however, a user still has the option to "rename database" under Operations. Or if root, the option to drop database. Renaming the DB via PMA means that cPanel won't find it (since it still thinks its the old name).
Wouldn't it be less volatile if that option were removed? Or if not removed, how about a nice fat warn + validate checkbox "renaming or deleting databases from the PHPMyAdmin interface could corrupt the cPanel database handler, resulting in server backup failures. Please drop/rename via the cPanel interface instead. Check 'I Understand the Risk' to continue."
In addition, a warn on the export/import tabs stating a similar situation + validate checkbox "Full import or import database creation from the PHPMyAdmin interface could cause discrepancies within the cPanel database handler, resulting in server backup failures. It is recommended that you use the cPanel interface for any database export/import. Check 'I Understand the Risk' to continue."
I just ran into the backup failure again this morning due to a database being renamed in PHPMyAdmin (PMA). I am curious about this: Why are we letting 1 user take down a whole server with settings that are known to conflict? PMA is an excellent and dare I say essential tool for many users, but if it's so easy to conflict with cPanel -- risky to allow.
If database schema inconsistency is causing such an issue with backup corruption, why are those features even allowed in PMA? For example, there is no way to manage users in the cPanel build of PMA, the tab is completely gone, I assume in order to prevent collisions with the cPanel DB system/API. While using PMA in domain/account level cPanel however, a user still has the option to "rename database" under Operations. Or if root, the option to drop database. Renaming the DB via PMA means that cPanel won't find it (since it still thinks its the old name).
Wouldn't it be less volatile if that option were removed? Or if not removed, how about a nice fat warn + validate checkbox "renaming or deleting databases from the PHPMyAdmin interface could corrupt the cPanel database handler, resulting in server backup failures. Please drop/rename via the cPanel interface instead. Check 'I Understand the Risk' to continue."
In addition, a warn on the export/import tabs stating a similar situation + validate checkbox "Full import or import database creation from the PHPMyAdmin interface could cause discrepancies within the cPanel database handler, resulting in server backup failures. It is recommended that you use the cPanel interface for any database export/import. Check 'I Understand the Risk' to continue."