As reported at #1028378: "Administer releases" checkbox visible on maintainers tab for sandboxes ...
Verified on a local test site, so it's definitely a project_release bug. We just need to do the trick where project_release_project_permission_info() inspects the given $project and alters what it says accordingly. See #1003552: Pass the project to hook_project_permission_info() for more.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | gtc_sandbox_maintainers.png | 16.84 KB | eliza411 |
| #4 | gct_sandbox_releases.png | 34.41 KB | eliza411 |
| #2 | 1028572-2.sandbox-no-administer-releases-perm.patch | 1.45 KB | dww |
Comments
Comment #1
dwwRolling a quick patch for this, stay tuned.
Comment #2
dwwCommitted the attached to HEAD, imported into bzr vendor, and merged into the git-dev branch. I can't see it in action now, since git-dev is currently offline while being rebuilt. But I tested locally and it's fine.
Comment #3
dwwTagging for sandbox projects, too...
Comment #4
eliza411 commentedI'm reopening this because after the Jan 19 build "Administer releases" still appears, unchecked and disabled. I can assign it to a co-maintainer, and when I do, it gets checked for me.
In addition (and seems like it's related), the Releases tab is still visible. I can check the box, and the setting is saved. This does nothing before I add a co-maintainer and still appears to do nothing afterward, although I haven't tested past this stage so I'm not totally sure what I would see.
Comment #5
dwwI bet all this is from #1032634: Creating new projects totally broken. Please re-test once that's deployed to another rebuild of git-dev.
Comment #6
dwwActually, given #1028378-8: "Administer releases" checkbox visible on maintainers tab for sandboxes, I'm going to call this fixed again.