Here is the steps to generate the issue
- Create a Container or Forum
- Select an existing template forum from Access control template selection
- Select two check box to use this template for future forum & container access control
"Remember this selection" & "Use the selected forum's settings as defaults for new forums and containers"
- Save the container
- While going to create a new Forum or Container template selection will be found there.
- Also all access control item will be selected based on template selection except two checkbox ("Remember this selection" & "Use the selected forum's settings as defaults for new forums and containers")
- Resulting while creating third item (either Forum or Container) template not selected.
- So we need to select this checkbox "Use the selected forum's settings as defaults for new forums and containers." each time we save a container & forum.
Comment | File | Size | Author |
---|---|---|---|
#3 | access_control_selection-2021149-1.patch | 878 bytes | jonline |
access-control.png | 49.01 KB | jonline |
Comments
Comment #1
jonline CreditAttribution: jonline commentedAfter some workaround I have found a solution
I have modified 188 number line from forum_access.admin.inc
'#default_value' => FALSE,
to
'#default_value' => !empty($template_tid),
This resolved the issue I have reported
Comment #2
salvisThank you for your report and proposed fix. I'm able to reproduce the problem in D7. Apparently, this is a porting bug, and we don't have tests covering that functionality yet.
This code is a bit tricky and we need to nail down the expected behavior with tests before we touch it.
Anyone wants to provide a patch?
Comment #3
jonline CreditAttribution: jonline commentedHere is the patch... Hope this patch will work as I am new in GIT and never create a patch before :)
Comment #4
salvisThank you for the patch. Its form looks ok. When you post a patch, you can set the Status to NR and your patch will automatically be queued for testing by the testbot. This saves work for the maintainer and gives you some feedback pretty quickly.
Comment #6
salvisAside from the patch not being applicable, we really do need tests for this functionality.
#3 would always set both checkboxes to be either both on or both off, which is falling short of what we want.
Comment #7
salvis