Closed (duplicate)
Project:
Workbench Access
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Aug 2015 at 13:03 UTC
Updated:
30 Sep 2015 at 19:45 UTC
Jump to comment: Most recent
Comments
Comment #2
sgdev commentedI can confirm the feedback from @tobiasb. This is a major issue.
Upgrading to 7.x-1.3 causes the taxonomy field to render without any section options. I haven't tested for all user types yet, but I do know this impacts a user that has editorial assignments to all sections by role (/admin/config/workbench/access/roles). Rolling back the patch from #1950590 fixes the problem.
Let me know if I can provide any further details, thanks.
Comment #3
JimV commentedSame story here. 7.x-1.3 left my taxonomy access control fields with no options to select while creating nodes. Rolling back #1959590 brought everything back.
Comment #4
sgdev commentedThis is definitely an issue with "all sections by role." I just did a quick check of a user that I know has an assignment to only one section via the Editors tab, and the taxonomy field renders correctly.
We have managers with access to the entire section hierarchy via the Roles tab, not the Editors tab. They are the users impacted by this.
Comment #5
sgdev commentedAdding as a related issue so they are cross-referenced.
Comment #6
katannshaw commentedI experienced this behavior as well. This is what I noticed after updating to 7.x-1.3:
Create content = limited # of groups shown
Edit content = message displayed "#My Page Name# is assigned to the Administration editorial group(s), which may not be changed."
Reverting back to 7.x-1.2 fixed this issue for me.
Comment #7
sgdev commented@jayhawkfan75, I'm confused by your comment here: https://www.drupal.org/node/2547039#comment-10195937
The issue described on this thread and the patch on Issue #2547039 are the same. I applied the #2547039 patch to 7.x-1.3 and it rolls back the patch introduced in #1959590. I had no problem applying the patch and did not get the "(Cannot apply hunk @@ 8 )" error message you mentioned in post #3 (https://www.drupal.org/node/2547039#comment-10193683).
Anyone having the issue described on this thread should apply this patch to a clean version of 7.x-1.3:
https://www.drupal.org/node/2547039
Comment #8
katannshaw commented@ron_s: You should be confused, as I was incorrect. The patch would not apply *for me* automatically (using NetBeans) so I did so manually and it fixed the issue for me as well! Thanks for the clarification:-)
Comment #9
sgdev commentedNo worries, I wonder why... I was able to apply it automatically with PhpStorm. Maybe NetBeans has issues applying patches created using the "git format-patch" format?
Comment #10
katannshaw commented@ron_s: I'm starting to thing so. It's not the first patch I've tried to apply using NetBeans where I've received a similar message to "Cannot apply hunk @@ ...". I'm working on moving to Phpstorm in the near future and this is yet another reason to do so. I do greatly appreciate your help on this one. It was a doozie.
Comment #11
ptocco commentedCan someone explain how to roll back 7.x1.3?
Should I simply download and expand this:
workbench-7.x-1.2.tar.gz
Then copy it directly into my existing Workbench folder? Or is there something else to know?
Comment #12
sgdev commented@ptocco, do you use drush? That's the easiest way to do so. You can select what version you want to download from the command line.
If you don't use drush, just download the 7.x-1.2 version of Workbench Access (not "workbench" as you posted in your message).: https://www.drupal.org/node/1900378 It should be placed at the same location your other modules reside, such as /sites/all/modules.
Comment #13
kwfinken commentedThis is the same issue and symptoms as https://www.drupal.org/node/2558593.
Comment #14
agentrickardMarking as duplicate of #2547039: Not applying access by user and role settings correctly