Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate assets to Gutenberg or get Classic Editor plugin installed #2

Open
bluesabre opened this issue May 21, 2020 · 0 comments
Open
Assignees
Labels
Milestone

Comments

@bluesabre
Copy link
Member

With the update to WordPress 5.x on the production server, we are now essentially forced to use Gutenberg as the Classic Editor plugin isn't available.

This has some unfortunate side-effects we need to either deal with or get the Classic Editor plugin installed and roll back to that for now.

Things that are broken with Gutenberg:
– Can't attach posts to releases on the post edit page

Things that would be convenient to have with Gutenberg:
– Upgrade shortcodes (mirrors, downloads, documentation) into blocks
– Download page automation (#1782876), which partly intertwines with migrating shortcodes to blocks

Launchpad Details: #LP1825478 Pasi Lallinaho - 2019-04-19 07:43:41 +0000

@bluesabre bluesabre added the high label May 21, 2020
@knomepasi knomepasi added this to the Gutenberg milestone May 25, 2020
@knomepasi knomepasi self-assigned this May 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants