patrickatwsrn

It would be great if this would be a thing in 3.1.

@Mark-H 150+ context seriously. Apart from this, I'd really like to see somthing that makes a lareger number of contexts more accessible.

Stumbled upon this issue today. It would be nice to hear what the dev team thinks about this problem and wheter or not this will ever be implemented. I would...

Works for me in 1.12.0. Please check and confirm.

Deactivating line 354 still solves the problem, ``` $c->where(array( //'class_key:!=' => 'CollectionContainer', // "NOT EXISTS (SELECT 1 FROM {$this->modx->getTableName('modResource')} r WHERE r.parent = modResource.id)" )); ``` Result: Question: https://docs.modx.com/current/en/extras/collections/index#collections-templates-new-in-version-2 says...

If the value of "parent" would be available from the advanced settings menu, resources could be moved to a new parent. Unfortunately, it has not been added: I'm aware that...

Change your Resource Type from Collections to Document and then back to Collections.

Still an issue > Just like the MODX Resource Tree itself, Collections supports nesting. You can create a Collection within another Collection. Sub Collection Containers will be displayed in the...

Duplicate of https://github.com/modxcms/Collections/issues/250 from Jan 2018. There is also a possible solution. Lets close this one and continue the discussion there.

https://github.com/modxcms/Collections/blob/4aa35b229787a0ec76dfcc50da578cf01ff69b1a/core/components/collections/processors/mgr/selection/getlist.class.php#L145 I believe that the labels of these buttons are handled by generic modx lexicon entries. If they would be handled by collections own lexicon, we could update our lexicon...