If upgrading from early versions of Views Bookmark, the upgrade path does not work. It looks like a find/replace spree must have gotten loose on the flag.views_bookmark.inc file, where several table names were changed from "views_bookmark*" to "flag*".
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | flag_views_bookmark_fixes.patch | 3.43 KB | quicksketch |
| flag_views_bookmark_fixes.patch | 2.99 KB | quicksketch |
Comments
Comment #1
quicksketchI found one more issue in our upgrade path. Thanks clients using ridiculously old versions of modules! ;) We're currently running all the old upgrades from Views Bookmark if necessary based on the current schema version of Views Bookmark. Our logic includes:
Looking at the start of our for loop, you see that we're running an update starting at the current schema version. Meaning that the current schema update is run, but we're already on that version so it's causing it to perform that update twice (potentially causing several errors). Our for loop should instead start one *after* the current schema and read:
Comment #2
quicksketchCommitted to both branches.
Comment #3
mooffie commented(I've read the patch and it looks alright.)