You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, my client who has the same permissions as the admin, cannot see the children for a Collections resource, instead seeing "This resource doesn't have any children". The admin sees the children just fine.
Also if I copy a link to a particular child resource and view it with the client account, they can edit it just fine.
Happens for 3.7.0 as well as 3.7.1 (just updated today)
Any idea what's causing this?
The text was updated successfully, but these errors were encountered:
For me (also having the problem with invisible child documents) it seems that I identified the point why I can't see any childs in collections. It's the "sort field" in Collection Templates/General Settings.
And for the name rules: " Name - Name of the field; can be any field from modResource, any TV name (prefixed with tv_, TV name must NOT contain a dot ) or any Tagger group alias (prefixed with tagger_)"
I took a TV "tvname" from my child page template and set this as "tv_tvname" in "Sort field". After saving the collection seems empty. Returning to a standard TV like "publishedon" the childs are visible.
UPDATE: Finally, it seems that it was a consequence of unfortunate circumstances that it did not work. Probably I made a few mistakes in defining the Collections or overlooked some important factors (missing tv_ prefixes and others). This shows that working with Collections is generally not easy, but I was able to solve it for myself in the end.
Hi, my client who has the same permissions as the admin, cannot see the children for a Collections resource, instead seeing "This resource doesn't have any children". The admin sees the children just fine.
Also if I copy a link to a particular child resource and view it with the client account, they can edit it just fine.
Happens for 3.7.0 as well as 3.7.1 (just updated today)
Any idea what's causing this?
The text was updated successfully, but these errors were encountered: