I have noticed that the default group's (ootb groups) that come with the install were renamed, repurposed and set up in a nested security model. If I decommission those and add new groups, I am able to create publications, view and assign the rights to groups. Still troubleshooting
I am not sure if this is an answer or just a work-around, but if I
check "All Publications" then re-create the publication (clear browser cache, etc) - also helps if publication name is different then the old one (Tridion cache I assume) - then I am able to see and define the
rights for my group!! :)
So quickly here are steps to re-create:
User Group with certain availability setting permissions for the specific sub-set of publications defined directly under the
description fields of the
General tab upon group creation.
Then create new publications (not sure if its just limited to
child publications or not)
Go into your publication and attempt to define your
rights per your security model and you will NOT see anything visible to select - this was not always the case at 1st, but did just notice that it happened over a few iterations and expanding the
BluePrint for new products and inheritance and re-implementing new security model designs. Also, important to note it was only on my clustered environment instances.
Quick steps to fix:
- Go back to your pre-defined group and check
- Clear your browser cache, hard refresh the
TCM and/or recycle the app pool and/or bounce the app - whatever it takes to get it to work
- Go back into your
BluePrint Viewer and create another child publication using a different name..
- Then open publications properties,
security tab, select a group/user and you should see your
rights listed on the right hand-side - as expected.
- Then you can go back and rename your publication as it was before or continue creating and defining your groups on that branch as you go.
Down n' dirty explanation. I'll try to revisit here soon. Gotta run and get back my lost time!