Opened 13 years ago
Closed 13 years ago
#22626 closed defect (bug) (fixed)
Link Manager is disabled even if you have custom links
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 3.5 | Priority: | normal |
| Severity: | normal | Version: | 3.5 |
| Component: | General | Keywords: | has-patch commit |
| Focuses: | Cc: |
Description (last modified by )
When upgrading from 3.4.2, link manager is disabled even if you have links, due to inaccurate $wp_current_db_version check in upgrade_350().
We check for version 21501, however it was bumped to 21707 in [21710].
Related: http://wordpress.org/support/topic/links-50?replies=19#post-3433313.
Attachments (1)
Change History (6)
#2
@
13 years ago
- Keywords commit added
Oh man. That's fun. I saw a few reports in the forums, but it worked for me in a brief test. Great catch.
#4
@
13 years ago
Took me a few moments to fully understand the report. To be clear, we handled the links upgrade routine in r21501, but after that, we bumped the DB version for 3.4.2, to the current revision, 21707. Obviously, 21501 < 21707, so upgrades weren't firing when you went from 3.4.2 to trunk.
In the future, we should probably just increment by 1 in a branch. It's so rare and usually is only to flush rewrite rules.
22626.patch uses version 22006, which is 3.5-beta1.