divinelighting
Verified User
- Joined
- Mar 17, 2008
- Messages
- 108
On 2 occasions I have had issues with website databases I believe may be because of the directadmin backup process. Apparently there is a module on the website that thinks the table is missing (during backup), then it drops it altogether and tries to recreate it. Are there some recommended safeguards for sql in the DA backup process? Here is what someone had to say about my specific issue:
A check is done for each request to the store to see if the plugin is properly installed (and does not currently include a check for the "seo_cache" table). If the plugin detects something is broken, it attempts (among other things) to remove and re-install the "seo_cache" table. The only way the re-install is triggered is if the plugin settings have not been installed or accessing the database fails (intermittent connect, read, or write issues).
The "seo_cache" table can disappear if for some reason on your host the script stops running during this process (hosting issue), your user does not have permission to create tables (database permissions issue), or your database becomes unavailable during the uninstall / install process (hosting issue).
As a stop gap, you can disable removal and creation of "TABLE_SEO_CACHE" in seo.install.php. Intermittent database access issues may cause you other problems down the road - and the default settings for your plugin will be used instead of your configured ones when these are encountered. But at least the "seo_cache" table should not disappear.