Change WordPress user roles and capabilities › Forums › Bug Reports › URE Conflict with Workflow Plugin
- This topic has 7 replies, 3 voices, and was last updated 6 years, 1 month ago by Vladimir.
-
AuthorPosts
-
06/07/2018 at 19:39 #5006owoodardParticipant
I am using URE Pro with Oasis Workflow to manage page revisions. Each user’s primary role is Author. They then have a secondary role that the workflow plugin uses to manage the workflow.
To manage what pages users can view and edit, I’m using the allow functionality of URE pro. When I allow the user a parent page, they can view the appropriate pages. However, when they click on a page to edit it, the workflow plugin, after user confirmation, creates a duplicate page the user can edit. However, after the page is created, there is an error message that says “Sorry, you are not allowed to edit this item.” When the page is loaded in a new window or refreshed, it loads normally. If I remove the parent page from user, there is no error message buy they can then view all pages. Additionally, if I block all pages except the pages they can edit, there is no error message. However, this can be difficult to manage if new top-level pages are added or there are other structural changes.
The same behavior is happening with the events CPT when the appropriate id’s are allowed or blocked.
Have you seen anything like this before? Any suggestions to correct this behaviour while still allowing simple management?
07/07/2018 at 02:49 #5007VladimirKeymasterIt seems that URE does not see new created page ID between of allowed pages ID list just after that page creation. The most probable reason – new page does not have parent page on that moment.
I will look if it’s correct and how to resolve this.13/11/2018 at 05:05 #5266curtin-webteamParticipantHi Vladimir, any further updates on this issue?
I have User Role Editor Pro version 4.25.1, and Oasis Worklow Pro version 5.7 plugins and installed. I also encounter the “Sorry, you are not allowed to edit this item.” error message when I make a copy of Page with the Oasis Worklow Pro plugin. However, when I refresh the page I find the action was successful and the page was successfully copied/created.
Steps to reproduce:
- Click the “Make revision” button. Note: this creates a copy of an existing page and is a Oasis Worklow Pro feature.
- I encountered the error message “Sorry, you are not allowed to edit this item.”
- However if I refresh the page again, or request the same URL the page shows up fine
By the way, I’ve looked up the other related post on this issue but that hasn’t helped. I tried all three options “edit_posts”, “edit_published_posts”, “edit_others_posts” but still encounter the issue?
Cheers
13/11/2018 at 05:12 #5267VladimirKeymasterHi @curtin-webteam,
Do you restrict editing pages via URE Pro edit restrictions add-on?
Is it possible to get from you a copy of “Oasis Worklow Pro” plugin for testing? If Yes, share it with support [at-sign] role-editor.com via DropBox or similar.13/11/2018 at 05:50 #5268owoodardParticipantThe Oasis Workflow developer found a solution that worked in our case. I don’t remember what it was exactly, but in our case, I believe there was a modification to the order certain actions are executed. I found the Oasis Workflow developer great to work with, it may be worth reaching out to him.
13/11/2018 at 07:13 #5270curtin-webteamParticipantThanks for your response @Vladimir. Yes, I just restrict access to Pages with User Role Editor Pro’s “Posts Edit” feature. In the “Post Edit Access” pop-up dialog I list Ids in the “with category/taxonomy ID” field.
Perhaps let me first check with the Oasis Workflow support Team as @nzinner pointed out, in case it’s an issue from their plugin.
Thanks for your response @nzinner, I’ve sent a support ticket to them.
Cheers.
14/11/2018 at 01:30 #5274curtin-webteamParticipant@vladimir my issue is now resolved. The Oasis Workflow support team said, apparently, this is a known cache-related issue and sent me workaround code to fix it.
Cheers.
14/11/2018 at 01:35 #5275VladimirKeymaster@curtin-webteam, thanks for letting me know.
-
AuthorPosts
- You must be logged in to reply to this topic.