Opened 2 years ago
Closed 9 months ago
#3554 closed Defect (fixed)
Upgrades being run multiple times from 1.7.X -> 1.8.0
| Reported by: | brettp | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | Elgg 1.8 Beta 2 |
| Component: | Core | Version: | 1.8 Beta |
| Severity: | blocker | Keywords: | |
| Cc: | brett@… | Difficulty: | moderate |
Description
This results in fatal errors during the upgrade process.
Change History (4)
comment:1 Changed 2 years ago by Brett Profitt
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 2 years ago by brettp
I think I have this one working, but anyone having this problem please reopen if errors pop up.
I know we wanted to keep the specific bootstrapping out of core but I couldn't come up with a cleaner way to do it. If someone has a better idea or suggestions please let me know.
comment:3 Changed 9 months ago by bambam
- Resolution fixed deleted
- Status changed from closed to reopened
- Version changed from 1.8 Beta to 1.8.8
I still have the same error.
I was using version 1.7.10, tried to update to 1.8.8 this didn't work.
Then first updated to version 1.7.15 this goes good.
When i upgrade to version 1.8.01 again this error:
Duplicate column name 'admin'
QUERY: ALTER TABLE elgg_users_entity ADD admin ENUM('yes', 'no') NOT NULL DEFAULT 'no' AFTER banned
Help me out please.
comment:4 Changed 9 months ago by cash
- Resolution set to fixed
- Status changed from reopened to closed
- Version changed from 1.8.8 to 1.8 Beta
Brett fixed this particular issue - see the commit that was linked above.
This feels more like a support request so I suggest using the forms at http://community.elgg.org/ - join the technical support group. You should link to this ticket here so people can this text. If we determine this is a problem with Elgg, we can open a new ticket.
Here's a little information that will be helpful in tracking this down:
2010040201 is the upgrade for adding the admin column and was pre-Elgg 1.8. If the upgrade to 1.8 is trying to run this, it means that you already have a value for "processed_upgrades" in your datalist table. This should only be possible from a previous failed upgrade to 1.8. Since we don't have any information about the previous failed upgrade, it is impossible to figure out the cause. It appears that you did not restore the database after the failed upgrade the first time and now are stuck with your db being in a bad state. I believe deleting the "processed_upgrades" row in the datalist table should reset you to a valid state. We always recommend backing up a database when running an upgrade. Good luck and please use the community site for further help.
Fixes #3554. Pulled 1.7->1.8 upgrade bootstrapping into a separate function. Made the plugin upgrade that forwards (2011010101) set itself in the processed upgrades.