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

Classic Editor #8

Open
annevk opened this issue May 28, 2021 · 6 comments
Open

Classic Editor #8

annevk opened this issue May 28, 2021 · 6 comments

Comments

@annevk
Copy link
Member

annevk commented May 28, 2021

I had to install the Classic Editor plugin as otherwise we keep losing paragraphs left and right. (Or I'm missing something obvious?)

Not sure if this creates problems for migration, or has that happened already?

cc @domenic

@domenic
Copy link
Member

domenic commented May 28, 2021

There's a drop-down to switch to raw HTML mode; did you try that?

We'll lose all plugins on the next deploy unless we edit the config.

@annevk
Copy link
Member Author

annevk commented May 28, 2021

I have clicked around a ton and also tried a different browser and have not found that option thus far. (I disabled the Classic Editor to once again try finding it, no luck.)

@domenic
Copy link
Member

domenic commented May 28, 2021

Click the three-vertical-dots menu to get this:
image then click "Code editor".

@domenic
Copy link
Member

domenic commented May 28, 2021

You can also set a personal preference to always default to that on your user profile:
image

@annevk
Copy link
Member Author

annevk commented May 29, 2021

So somehow I had that checked already (which also makes the Editor part of the dropdown disappear which explains why I did not see it) so I guess I was already using the code editor. However, the code editor does not show p tags for me and so when I make an edit and save, all those tags end up disappearing.

@andreubotella somehow dealt with it though when creating their post so I might still be missing something.

@domenic
Copy link
Member

domenic commented Dec 1, 2021

OK, I ran into this now. There do not appear to be any great solutions with vanilla WordPress: WordPress/gutenberg#11211 . People suggest installing TinyMCE Advanced and that gives you an option to disable <p>-stripping.

@andreubotella appears to have gotten around it by using <!-- wp:paragraph -->, which I will do for now. But I should figure out how to install plugins in the Dockerfile so that we don't run into this again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants