MODX Community

Collections children not visible for account

Unusual problem I never encountered before. I have an admin account, and a client account that was a copy of the admin account, with same Superuser permissions.

When the client logs in and clicks on a collection, none of the children are visible. It just says “This resource doesn’t have any children”, however, when I login under the main admin I can see the children. Also this isnt a browser issue because if I login as the client I see the same thing - no children, and when my client logs in with the admin credentials she can see the children.

Any ideas here? The only real difference I can see between the two accounts is that the client account is not sudo.

1 Like

Are you absolutely certain you’re logging in at the same URL? i.e. both using https or http and both using www. or not? Just something to check to begin with.

1 Like

Yes the site is forced to use https…although even if I used http and https it should not affect the display of children for a Collections resource.

1 Like

Have you tried checking dev console in the area where the children should be?

1 Like

Are the children published?

Are they in a different resource group than the parent?

1 Like

Not sure what you mean here Chrisandy

1 Like

Some of the children are published, some aren’t but that shouldn’t matter since all the children show up in the Collections resource in MODX. Also the client account can perfectly edit any of the resource children (I manually changed the ID in the edit url) so its not like there is a permissions problem there.

I posted this in Github in the Collections repo so I’m hoping to get a response. The issue is the same under 3.7.1 which was released within the last day.

1 Like

By checking the dev console I mean right click on the area where the children should show (in Chrome) and click on inspect and then ‘console’ - any errors or warnings? Also, an outside chance but try changing the ‘per page’ setting of the parent to say 5 rather than what it’s defaulted at.

1 Like

After an odyssey, which I have described in this thread: Collections page not editable, empty area, I now have the same problem. No child documents are visible, both for the admin and the editor account. It doesn’t matter if I created it in the collection or if I dragged an existing document there or if I change a document with children to a collection. The child documents disappear (and will be visible again if I change the collection to document).

1 Like

Seems that I identified the problem why I can’t see any childs in collections. It’s the “sort field” in Collection Templates/General Settings.

In https://docs.modx.com/extras/revo/collections is defined: “Sort field - Default field to sort by (Same rules as for name in columns definitions).”

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.

1 Like

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.

1 Like

Great, you are learning so much! Trust me it took me days to find a typo in a login routine, happens to us all