Closed (cannot reproduce)
Project:
File Entity (fieldable files)
Version:
7.x-2.0-unstable7
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Dec 2012 at 07:45 UTC
Updated:
9 Jun 2015 at 18:33 UTC
Jump to comment: Most recent
Comments
Comment #1
jpwester commentedI am seeing the same thing. Is there a more elegant solution?
Comment #2
ParisLiakos commentedi cant understand why the table was already there..you was upgrading from unstable6 to nstable7?
Comment #3
Chris CharltonFor I was stuck in an update loop - every time I ran update.php Drupal/Drush kept reporting update 7200 needed to run. I ended up getting past this somehow.
Comment #4
devin carlson commentedAs rootatwc mentioned in #2 the image_dimensions table is only created during module installation or by update 7200.
A borked uninstall of File entity or another contrib module creating the same table are the only possible causes of the table existing (that I can think of). Otherwise, I haven't been able to reproduce this problem.
Comment #5
jpwester commentedI was upgrading from unstable6 to unstable7, yes.
Comment #6
nixter commentedAn easy way to bypass the creation of a table that exists and get Drupal to stop saying you have an update like this. (7200 - Create the {image_dimensions} database table.) is to go into the System table and change the Schema from 7199 to 7200.
This worked like a champ and got ride of the error we had.
Here is another example of a simular issue with the field collection module. Comment #5 and #6
#1783456: Enable re-running failed update_7001(), adding revision fields
Comment #7
bousley commentedStill having this issue years alter and I'm unable to fix on Acquia Dev Desktop or on the Cloud. So, I'm unable to update Drupal core for a site that I've taken over maintenance on. When I attempt to do so this is the message I get: