Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By cgfx on
Seems the last bit of updates for Metatags caused some problems? First, the site was broken. Ok. Went back to the most recent backup. Everything seems normal unless I try to edit anything (except for blocks). I get this:
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'cubelight.image_dimensions' doesn't exist: SELECT * FROM {image_dimensions} id WHERE id.fid IN (:fids_0); Array ( [:fids_0] => 24 ) in file_entity_file_load() (line 225 of /var/www/cubelight.us/sites/all/modules/media/file_entity/file_entity.module).
The website encountered an unexpected error. Please try again later.
No idea how to fix this. Where do I even begin?
Comments
=-=
Doesn't look to be related to metatags as the error indicates an issue with file entity. using the error as google keywords uncovers multiple already existing discussions that you will need to work through : search results
I did so. But the range of
I did so. But the range of "solutions" appeared bewildering. Though, oddly, your search terms also revealed very different results than my own.
Editing any files is out, surely, since I do not code. Since this problem arose not by any coding done in my part, it seems reasonable that installing recommended updates or my installing and activating an otherwise unrelated module somewhere tripped up file entity somehow. This could include: Google Analytics, Date (necessary for Scheduler) and Scheduler.
Prior to that, everything worked without issue. Deactivating these modules doesn't appear to fix the issue.
Also having issues reproducing the problem in my sandbox. Migrating one of the current backups just borks the entire sandboxed site. (Yet the live site itself appears to work fine from recover.)
=-=
I'd start with a check of the issue queue of the module throwing the error to narrow down results.
I think I found it. I have no
I think I found it. I have no idea why this worked, or why you can't update a module via the browser admin interface (seriously, "Media is already installed."? That makes no sense at all, Drupal), but the Media module appears to have been the cause, only fixable via:
...so far as I can tell, anyway. Things appear to be working, so I'm going to grab a new backup and try to install it on my sandbox site on microceratops.local.
Anyway, your search terms provided the eventual answer. Here's hoping nothing else breaks.
Thanks!
More weirdness, after a
More weirdness, after a restore from backup:
This is going past the point where things still worked.
How does completely rolling back to a complete site backup not resolve this issue?
Sorry to belabor the obvious,
Sorry to belabor the obvious, but did you run update.php?
============================
Resonetrics: Better Tools for Building Brands
http://resonetrics.com
http://technologyformarketers.com
http://kittenassociates.org
http://www.linkedin.com/in/sammooreatresonetrics
I used drush updb:
I used drush updb:
But it doesn't appear to make any difference in this case.
When did you do this?
When did you do this?
If you roll back your database, you should probably roll back your codebase to match.
============================
Resonetrics: Better Tools for Building Brands
http://resonetrics.com
http://technologyformarketers.com
http://kittenassociates.org
http://www.linkedin.com/in/sammooreatresonetrics
Using Backup and Restore, I
Using Backup and Restore, I had selected "Entire Site" tar files. If that doesn't roll back the codebase, what does?