Imporvement: checkbox in the class editor to hide unpublished object

[Yivan]

Actually all object in the folder, published or not, are show as options.
In some case, some object are not published (being in edition process and not finished to be correctly filled for instance) and they should not be available as choice.

Maybe a checkbox labeled "Hide unpublished" could be added to the 4 dropdown elements type. So this way user creating the class could decide on per case if object should be available or not depending published status.

[Yivan]

There is tricky case... what if the element is unpublished later and as been selected in some dropdown before.
Maybe to go simplier, unpublished will not be hidden but just adding the text (not published) behind the text for this choice in the dropdown (so user know it is not published actually...).

Better would be they are showed, but cannot be assigned/selected. And if they are already assigned as choice thay stay assigned (and can be unasigned/unselected). But I am not sure the ExtJs component could handle this.

[ThomasKeil]

This will most probably be possible.
Extjs' combobox can't disable items, but with a little help of templates and listeners it's possible.
See https://github.com/ThomasKeil/pimcore-plugin-DynamicDropdown/tree/disabled_items
It's not yet 100% nice since the cursor doesn't change and it get's hover-lighted, and I'm not yet sure if it's possible to change that, but it's usable.
I now need to add the configuration, I'll probably use a combobox like:

Handle unpublished objects: Show / Unselectable / Hidden

[Yivan]

@ThomasKeil I thinked a little more about this.
I ended finally to think maybe it should be leave as it was (no difference between published/not published) because:

• Pimcore native href/multihref don't do this difference and Pimcore work like this
• And the more important (that is why i opened the issue): finally unpublish object will not be available by the getter method in the frontend/public site (as unpublished). So selecting an unpublished (and uncomplete) object won't break the web site.

So it is more easy to keep it simple as it was, and it would permit to prepare association (even if not published).
Do you think we need enhancement finaly ? For me finaly it is ok as it was, keep it simple and Pimcore way. If you think too, you can revert and close the task. Sorry about having opened the issue without having thinking all of this before.

[ThomasKeil]

I think in any case I'll keep the visual feedback if an object is unpublished, so the user can decide what to do.

[Yivan]

Yes it is a nice addition as visuel indicator. Thanks.

[ThomasKeil]

I just committed a new release, the unpublished items are now grey, and can be configured to be unselectable.

[Yivan]

Thanks @ThomasKeil. I just tested it on last stable Pimcore.

I noticed the following problems:

• It work only for Dynamic Dropdown (the select). The 3 others (multiselect, itemselector and superbox) don't put item in gray and they are always selectable.

• For Dynamic Dropdown (the select), checking "Unpublished selectable" don't work because item are always non-selectable even if checked.

I try re-save the class and flushing all the caches and problems are always here.
Maybe the issue must be reopened.