-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set hide_children_in_tree for Collections that do not have containers as a child #13
Comments
This will be available in next version of MODX, because there is no way to get it working in current version... |
doh, there isn't?? I just tried that...setting the attribute "hide_children_in_tree" of the CollectionsContainer resource indeed hides the arrow... (this is not set "normally" though, e.g that attribute has value of 0, also when its a Collection)...I guess there's something that was a problem when doing so? I just saw 3 different editors clicking on that arrow...that's why it seems to be an issue for me... |
The problem is, that when you set this property, you will not be able to drag and drop resource in collections.... |
shit...yap...any possibility to hide that arrow via css?? |
hmm, probably you can try it based on the collections (not sure how it's named in real, LOL) class that it has because of the collecions icon. |
This works for me in MODX 2.3.2 to hide those triangles via css:
where tree-node-id is "context" + "_" + "resource id". |
If you'll have nested collections, or folder under collections, it will not work properly |
That's true. This is just a dirty fix for the case as described by exside. I currently have this situation, too, where there's nothing nested but the editors always click on the triangle. |
|
ad 1) resources under Collections have that flag set to 0 |
Oops, (1) was a bug in Gitify (which is now fixed) :) |
This will prevent displaying arrow before the Collection node in Resource tree when it has only Resource children (that are all hidden under children's tab).
The text was updated successfully, but these errors were encountered: