💾 Archived View for chirale.org › 2008-08-07_161.gmi captured on 2024-08-31 at 11:55:58. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-05-12)
-=-=-=-=-=-=-
Tested on Drupal x
Often we haven’t a full control of machines we have sites hosted in. It’s called “shared hosting”, and it could be cheap as problematic. On a such environment, I had some privileges like “CREATE TABLE, CREATE VIEW” etc. revoked for some weeks. Results? Some enabled modules missed their table, and some CCK fields cannot store their content.
Symptoms: on admin/logs/watchdog you get errors like this:
Table 'echozdbprefix_scheduler' doesn't exist query: SELECT all.sh django2gmi.sh processing README.md wp2gmi.sh FROM drp_running_scheduler WHERE nid = 1481 in ...
After privileges are restored, to solve this issue recreating missing tables you have to:
Backup your database.
Disable tainted module
Via phpMyAdmin or similar tools, go to system table (e.g. dbprefix_system) and delete the disabled module row, e.g.
| | | | | | | | | | |----------------------------------------------|-----------|--------|-----------------------------------------------------|--------|----------|-----------|----------------|--------| | filename | name | type | description | status | throttle | bootstrap | schema_version | weight | | sites/all/modules/scheduler/scheduler.module | scheduler | module | This module allows nodes to be published and unpub… | 0 | 0 | 0 | 2 | 0 |
Reload the module page and enable the module.
Now table for this module will be recreated. For each “table doesn’t exist” error you have to follow these steps. Note that all saved settings (if exists) for that module will be lost.