• Resolved Nirali Biniwale

    (@niralibiniwale)


    Hello team,

    I encountered an issue while attempting to revoke the publish_post capability from the Editor role. The behavior is as expected when using the default Gutenberg builder. However, with the classic editor, I’m facing a problem.

    There are two scenarios:

    1. An Editor role user creates a new post and clicks on publish. In this case, it should transition to the “pending review” status. (This is functioning correctly for both editors.)
    2. After the Admin approves the post, if the Editor user makes changes to the post, it should again go to “pending review” status. (This works as expected for Gutenberg but not for the Classic editor.)

    I would appreciate any assistance with resolving this issue.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Kavya Gokul (a11n)

    (@properlypurple)

    Hey @niralibiniwale! Have you tied testing this with a built-in role like Author or Contributor, without using the User Role Editor plugin? This might be a bug, but we need a little bit more testing to figure out the scope of how much is affected.

    Thread Starter Nirali Biniwale

    (@niralibiniwale)

    Hello @properlypurple,

    I experimented with default roles without using the User Role Editor plugin. Here are the outcomes:

    1. Author: In both editors, blogs were published directly without requiring review for both adding and editing scenarios.
    2. Contributor: In both editors, new posts went through the review process. However, after publication, I was unable to edit them.
    3. Editor: In Gutenberg, everything worked as expected. In the classic editor, new posts followed the expected behavior, but editing posts resulted in direct publishing.

    It seems like this issue is related to the WordPress core version rather than being specific to any particular plugin, or might be classic editor conflicts with the WordPress core version.

    Kavya Gokul (a11n)

    (@properlypurple)

    Hey @niralibiniwale! I’ve just tested this with both the block editor, and the classic editor plugin. The behaviour that’s seen for Contributor role is exactly like how you describe above. For other roles, they’re already able to publish their own posts by default, so that behaviour is also as expected.

    For your use-case, if you’re looking to have people submit posts for review, it looks like using the contributor role, or extending its capabilities using the plugin (User role Editor) would likely be the best way to go.

    Thread Starter Nirali Biniwale

    (@niralibiniwale)

    Yes, that’s what I am saying, when I use the User role editor plugin, it works perfectly for Gutenberg and not for Classic Editor.

    Then there might be an issue with the Classic editor or WordPress core version!

    Kavya Gokul (a11n)

    (@properlypurple)

    It looks like the best way here would be to file a bug for the classic editor. Since you’ve done most of the testing already, please share that in the report as well.

    Thread Starter Nirali Biniwale

    (@niralibiniwale)

    Sure.
    Please find video of Gutenberg & Classic editor’s behaviour for Contributor role:

    https://drive.google.com/file/d/1DAjDLZ0059oMvM-Iz1R4fjjtNmC1aFDR/view?usp=sharing

    Kavya Gokul (a11n)

    (@properlypurple)

    Thanks @niralibiniwale! I see that you filed the issue here, so the developers of the plugin will be able to take it from here.

    Thread Starter Nirali Biniwale

    (@niralibiniwale)

    Yes. Thanks @properlypurple for the advice to post the issue on GitHub page

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Classic editor plugin conflict with User Role Editor plugin’ is closed to new replies.