Support » Plugin: PublishPress Revisions: Submit, Moderate, Schedule and Approve Revisions » Behavior when using Classic Editor plug-in

  • Resolved hima_art

    (@hirapapa)


    Since I can’t use English, I ask questions with the help of Google Translate.

    Thank you for providing a nice plugin.

    I installed it immediately and tried it, but when the “Classic Editor” plug-in is enabled, clicking the edit link of a revision opens the screen in the legacy editor (visual or text).

    Regardless of whether the standard editor of “Classic Editor” is set to “Gutenberg”, the editor used by the user is set to “Gutenberg”, or both of them are set to “Gutenberg”, all are opened in the legacy editor.

    It can be solved only by stopping the “Classic Editor” plugin, but since old posts are created with the legacy editor, it is unavoidable to use “Classic Editor”, so if possible, “Classic Editor” I want to use your plug-in as well.

    Is it possible to make them work together in some way?

    Thank you.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor publishpress

    (@publishpress)

    Hi @hirapapa

    Thanks for using PublishPress Revisions.

    Sorry, we don’t see this problem in our testing.

    Please contact us with the steps to see this problem: https://publishpress.com/contact/

    Step 1.
    Step 2.
    Step 3. etc

    hima_art

    (@hirapapa)

    Thank you for your reply.

    I also checked under what circumstances the edit screen opens in the old editor when you click Edit Revision.

    The phenomenon appears only when the “Classic Editor” plug-in is enabled and the “Allow users to switch editors” item is set to “Yes” in the “Classic Editor” plug-in settings.

    Plugin Contributor publishpress

    (@publishpress)

    OK, thanks @hirapapa. We’ll file this as a bug and get it fixed.

    Plugin Author Kevin Behrens

    (@kevinb)

    @hirapapa Under that Classic Editor configuration, the Edit Revision function will use whichever editor the published post was last edited with. In limited testing previously, I found this was the best way to avoid compatibility issues at revision publication. I’ll plan on revisiting the issue after we clear some other development tasks.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.