Classic/Gutenberg 404’s

  • New install with BeTheme and demo import. All up to date.

    A number of my pages are throwing 404’s when I try to edit with Classic or Gutenberg. I also have BeBuilder and Visual Composer installed, and those work, for the same pages.

    All plugins off, same behavior: the remaining BeBuilder works, basic edit throws a 404.

    /wp-admin/post.php?post=17&action=edit

    Any thoughts?

    • This topic was modified 2 years, 2 months ago by andrewm57.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter andrewm57

    (@andrewm57)

    Also if I edit via Visual Composer, the front/inline version works. If I switch to backend editor, it 404’s.

    /wp-admin/post.php?post=17&action=edit&wpb_vc_js_status=true&classic-editor

    BeBuilder and Composer are add-ins for WordPress. They are not part of WordPress core whereas Gutenberg is part of the core. Builder and Composer store their data differently than Gutenberg. Gutenberg has no idea how to work with the page builder files. You would have to use the tools provided by the page builder. They are totally different applications. You are running 3 different site editors and expecting them to work together but they don’t.

    Thread Starter andrewm57

    (@andrewm57)

    Actually 4 editors: Classic, Gutenberg, BE & VC. But I’ve has this combo before, and all that happens is any page created with a higher editor pops a notice about do I really want to downgrade, and if I do it shows the special editor coding. Not a 404.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Classic/Gutenberg 404’s’ is closed to new replies.