Classic editor does not work as expected for specific user roles

  • Nirali Biniwale

    (@niralibiniwale)


    1 year ago

    Hello Team,

    I wanted to create a user role in WordPress that creates a new post with pending review status and once published, if he/she again wants to edit it then it should go to pending review status again.

    I am using the classic editor and ACF plugin on my existing website. So, I will experiment with my scenarios with classic editors and Gutenberg editors.

    This thing, I experimented with default roles without using any 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.

    I would appreciate any assistance with resolving this issue.

Viewing 2 replies - 1 through 2 (of 2 total)

  • I wanted to create a user role in WordPress that creates a new post with pending review status and once published, if he/she again wants to edit it then it should go to pending review status again.

    How are you creating the new user role?

    This workflow can easily be accomplished with the native Contributor role plus the additional edit_published_posts capability.

    And you can use a plugin like User Role Editor or PublishPress Capabilities to add the additional capability (among a ton of other features).

    The native roles and capabilities should remain the same whether you use the native Block or Classic editor. Third-party editors may have their own nuances.

    As to your tests:

    Author: In both editors, blogs were published directly without requiring review for both adding and editing scenarios.

    This is the designed behaviour of the AUTHOR role. Authors can publish and edit their already published posts — no approval is required. However, an Author cannot edit another user’s posts and cannot create PAGEs.

    Contributor: In both editors, new posts went through the review process. However, after publication, I was unable to edit them.

    Again, this is the designed behaviour. This is a lower role than Author, and an Editor or Administrator has to publish (approve) a Contributor’s posts to go live. Also, Contributors cannot edit their already-published posts, by design.

    Editor: In Gutenberg, everything worked as expected. In the classic editor, new posts followed the expected behavior, but editing posts resulted in direct publishing.

    The Editor role is the highest of the 3 roles you mentioned, only below Admins. Editors, like Authors, can publish and edit their own posts directly — no approval required. But Editors can also approve/publish/edit posts made by other users, publish PAGES, and even manage comments. Editors don’t need any approval to publish new posts or edit existing posts.

    I’ve provided the official documentation of the built-in roles and their capabilities below. These roles and capabilities, by default, should be independent of the editor used… but can be altered by plugins including the ones mentioned above.

    Roles and Capabilities

    Thread Starter Nirali Biniwale

    (@niralibiniwale)

    I am not creating any custom user role as of now, because WordPress itself gives many options to use.

    The native roles and capabilities should remain the same whether you use the native Block or Classic editor. Third-party editors may have their own nuances.

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

    Please find behaviour of Gutenberg and Classic editor for Contributor role.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Classic editor does not work as expected for specific user roles’ is closed to new replies.