Skip to content

Add classic editor deprecation notice#16008

Merged
guarani merged 13 commits intodevelopfrom
add-classic-deprecation-notice
Mar 6, 2021
Merged

Add classic editor deprecation notice#16008
guarani merged 13 commits intodevelopfrom
add-classic-deprecation-notice

Conversation

@guarani
Copy link
Contributor

@guarani guarani commented Mar 3, 2021

Addresses wordpress-mobile/gutenberg-mobile#3209

This PR adds a deprecation notice to the classic editor for all users regardless of site type.

To test

  1. Create a new post using the classic editor. This can be done by changing the site editor preference to classic in My Site > Site Setting > Turn OFF Use Block Editor setting, and then creating a post as you normally would.
  2. Expect an alert to be shown notifying users of the future removal of the classic editor for new posts/pages.
  3. Smoke test the app to ensure the alert is not shown for existing posts with classic content or any other scenarios.
  4. I also tested the iOS share extension to make sure the popup doesn't show there.

Screenshot

PR submission checklist:

  • I have considered adding unit tests where possible.
  • I have considered adding accessibility improvements for my changes.
  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

@guarani guarani added the Aztec label Mar 3, 2021
@guarani guarani added this to the 16.9 milestone Mar 3, 2021
@peril-wordpress-mobile
Copy link

peril-wordpress-mobile bot commented Mar 3, 2021

You can trigger an installable build for these changes by visiting CircleCI here.

@peril-wordpress-mobile
Copy link

peril-wordpress-mobile bot commented Mar 3, 2021

You can trigger optional UI/connected tests for these changes by visiting CircleCI here.

@guarani guarani requested a review from cameronvoell March 5, 2021 22:59
@guarani guarani marked this pull request as ready for review March 5, 2021 22:59
Copy link
Contributor

@cameronvoell cameronvoell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good. Notice looks good in dark mode. I did not see it come up after the initial presentation, worked as expected 👍

@guarani guarani merged commit ef7e36c into develop Mar 6, 2021
@guarani guarani deleted the add-classic-deprecation-notice branch March 6, 2021 00:32
guarani pushed a commit to wordpress-mobile/WordPressMocks that referenced this pull request Mar 18, 2021
The [classic editor is deprecated](wordpress-mobile/WordPress-iOS#16008) and is [now being removed](wordpress-mobile/WordPress-iOS#15766) for Simple sites (except when editing existing posts with classic content or when using the iOS share extension).

This means that on Simple sites, the site settings screen will no longer have a "Enable block editor" switch. WPiOS has a UI test suite, `EditorAztecTests`, that runs on a mock Simple site ("Tri-County Real Estate") and tests various features of the classic editor.

Since the classic editor is going away for Simple sites, I think it makes sense to make `EditorAztecTests` run on an Atomic site instead of a Simple site. On WPiOS, this mock site is used for all other UI tests, so this has the side-effect of switching all WPiOS UI tests to run on a mock Atomic site instead of a mock Simple site. The same could be true for WPAndroid and the same considerations might apply.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants