I have a global profile type, ‘Programs’, which is accessible to many groups, but in some groups, the checkbox that would normally allow me to give access to it for that group is disabled. Any ideas why this might happen and what can be done about it?
Thanks,
-= G =-
Hi G,
That checkbox gets readonly=“readonly” if your group already has content of that type (the intention being, we don’t want to allow un-checking of it if you already have content of that type). I’m not sure how this situation could’ve arisen where it has content but not editing ability for it (maybe a shared item with auto-accept as live)?
One option to address would be to try re-saving the Programs profile type with this checkbox enabled:
which I believe would set it to available for all groups by default.
Another option would be, as a one-off, to experiment and see if in the inspector you can remove the readonly=“readonly” in the group editor and then re-save the group that way.
Once it’s enabled, I’d be curious to know if there were profiles of that type in the group to explain the readonly criteria; if we can get steps to reproduce this we can file it as a bug to fix in core. Let us know, thanks!
Ah I see - what happened is that a number of profiles were originally created in a different group, then when several departments merged, the profiles were just moved into the new group before that group was given access to the profile type (because I didn’t think of doing that in advance). Only problem is, then it wasn’t possible to see the profiles in the new group, or add more in that group since the profile type didn’t show in the profiles tab.
I didn’t want to make the profile type available to all groups, but knowing how it works from what you said, I temporarily moved the profiles into another group, then checked the box to add the type to the new group, then moved the profiles back, and that took care of it.
Thanks for the quick response…
-= G =-