Moving backwards, not forwards

  • asherpentecost1

    (@asherpentecost1)


    7 years, 3 months ago

    The update to Gutenberg has been nothing short of a head ache with the only bright side being that my production site’s content is currently intact. However, I’m unable to edit any of it due to the insistence by Gutenberg’s code changes to decide how I want my content formatted by removing p and br tags and adding p tags where it sees fit to replace.

    Stuff.

    This has, much to my annoyance, added additional work to a website overhaul I have been working on as now I have to go back and touch every page an effectively redesign them to work around the idiocy that is Gutenberg and its decisions on how my content is formatted.

    So, THANK YOU for telling ME how MY CONTENT should look on MY WEBSITE.

Viewing 1 replies (of 1 total)
  • Mark Uraine

    (@mapk)

    6 years, 10 months ago

    Sorry to hear about your experience. I’ve run into this a couple times myself. Sounds like the issue resides within the Code Editor once the page converts to the new block editing experience. Is that correct?

    I’ve always noticed an issue when switching between the Code editor and the Visual editor as well.

Viewing 1 replies (of 1 total)

The topic ‘Moving backwards, not forwards’ is closed to new replies.