Problems with "Create New Doc"
I have a ticket in ZenDesk that seems to indicate a problem with the "Create New Doc" feature. Group members of http://commons.gc.cuny.edu/groups/edr-605-fall-2015/ have been given the attached instructions to create and edit documents. I was able to edit without any difficulty, but when I create a new doc, it shows in my feed but not in the Doc list for the group. I thought at first that the problem was that users needed to select the "EDR 605 Fall 2015's Docs" tab, but that doesn't solve the problem. LMK if you all need more info.
#2 Updated by Boone Gorges over 6 years ago
- Category name changed from Groups (misc) to BuddyPress Docs
- Target version set to 1.8.13
It looks like this is due to a bug in BuddyPress Docs that was fixed in the version I pushed out earlier today. I've just updated the Commons to have the new version. Marilyn, can you test again? If you find that it's fixed, please convey to the reporter that it should now be possible to fix the group association by going to the Docs section of his/her profile, edit the Doc, and associate it with the appropriate group. Alternatively, if you supply me with a list of miscreated Docs (with URLs), I will do the fixing.
#5 Updated by Marilyn Weber over 6 years ago
Reopening this - it's working for me, but not for one of the group users. Her name is Helen Canaras, username helenc1021. When she goes in (she gave me her password so I can see it), the association is not there (see attached screenshot). Why would it work for me but not for her? (That q can remain rhetorical if it's easier to just fix it!)
#6 Updated by Boone Gorges over 6 years ago
It turns out that bbPress is messing this up. BuddyPress Docs works, in part, by mapping certain high-level capabilities to the 'read' capability. In a normal WordPress installation, all roles have 'read'. But the custom bbPress roles do not have 'read', and on the Commons, many users get bbPress roles for some reason.
In https://github.com/cuny-academic-commons/cac/commit/123195eb92320a813b69ffc17c4571025ef9c164 I force 'read' for all roles. It appears to solve the problem. Marilyn, could you verify please?