Skip to content

Visual editor migration#4187

Merged
aforcier merged 2 commits intorelease/5.5from
issue/new-editor-migration
Jun 8, 2016
Merged

Visual editor migration#4187
aforcier merged 2 commits intorelease/5.5from
issue/new-editor-migration

Conversation

@maxme
Copy link
Contributor

@maxme maxme commented Jun 7, 2016

Note: there is no changes in the DB, but since we have all other migrations done there I added the visual editor migration there.

  1. old users upgrading from any versions to this version should have the new editor available and enabled
  2. new users should have the new editor available and enabled
  3. users who previously disabled the new editor should have it enabled
    WordPress.com Notifications in Android #3 is about our future announcement "hey check out the new editor" and I guess these users are rare.

@maxme maxme added this to the 5.5 milestone Jun 7, 2016
@aforcier
Copy link
Contributor

aforcier commented Jun 8, 2016

Confirmed that upgrading from vanilla and clean installing this branch enables the editor properly.

As we discussed, #3 should affect few enough users that it's not worth adding a special rule for.

:shipit: 🎉

@aforcier aforcier merged commit e7edff6 into release/5.5 Jun 8, 2016
@aforcier aforcier deleted the issue/new-editor-migration branch June 8, 2016 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants