Closed (outdated)
Project:
Flag
Version:
7.x-3.x-dev
Component:
Flag core
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
19 Sep 2012 at 03:27 UTC
Updated:
18 Aug 2025 at 10:29 UTC
Jump to comment: Most recent
Comments
Comment #1
joachim commentedYou should install 2.0 on a production site. 3.x is not yet ready. There is already an upgrade path, as with (most) Drupal modules.
Comment #2
liliplanet commentedThank you Joachim!
Comment #3
ñull commentedWhat is the present situation? I have this other issue #2042263: Allow direct unflag and apparently I need ver. 3.x for it. When I do:
In other words I cannot upgrade. I will continue developing what I need, by uninstalling and starting from scratch, for the production site I will have to migrate / update all existing bookmark flags to 3.x
Comment #4
joachim commentedCan you try the upgrade process via the UI?
It's very important that nothing tries to clear caches before the upgrade process is complete -- maybe drush is doing that?
Comment #5
ñull commentedThanks for the support! That did it!
Comment #6
lotyrin commentedIs there any way to support upgrades with Drush? Our deployment is fully automated, we'll have to do this manually this time, but for any others in that boat.
Comment #7
lotyrin commentedComment #8
joachim commentedWe're far from being the first module that's changed its table names. Lots of core modules did this from 6-7. I've had a look at core module hook_update_n()s and I can't see what they're doing to prevent this kind of crash.
Comment #9
ivnishClosed as outdated because Drupal 7 is EOL