Hello,
I have MODX 3.1.2 and ClientConfig 2.5.0 and 4 Contexts.
In Manger I can’t select all available contexts.
Only the first two.
Don’t understand why.
Is it a bug?
Thank you in advance.
bye
Chris
What exactly do you mean by that?
Is it that when you go to manager/?a=home&namespace=clientconfig and open the dropdown “Choose Context”, that not all your contexts get listed? Or are all the contexts in the dropdown, but you can’t select them?
In the dropdown “Choose Contex” I have all contexts listet plus Global.
But I can’t select all, only the first two.
I can’t reproduce this. Is anything special about the bottom 2 contexts?
Does an error get output to the console of the developer tools in the browser, when you select one of the bottom 2 contexts?
In the “Network” tab (of the developer tools), does a new AJAX-request get added with the action-parameter = mgr/settings/getcontextaware when you select a context? Is this request sucessful (status = 200)?
nothing.
I can’t select. Its not selectable.
Only Global, and the first, second option ist selectable.
Strange
yes. but Only for the first two dropdown options.
This is very weird.
Could it be a CSS issue? Some element with a higher “z-index” that overlays the dropdown?
wow. Good idea.
Thats right.
If I remove in Inspektor the container ‘x-panel-bwrap"‘ after the dropdown, then it is selectable. Strange. My be a bug?
I think you can reproduce it with more than 3 contexts.
I tested with 5 contexts and different windows-sizes, but I still can’t reproduce the issue.
What’s the content of this container (as there seems to be multiple such containers on the site)?
Now I have a better information:
this container may be the problem:
<div id="clientconfig-formpanel-home" class=" x-panel form-with-labels x-panel-noborder x-form-label-left">
If I extend margin-top: 100px, then I can select.
Well, I still can’t reproduce the issue.
Maybe it’s the “Field type” of the available settings that has an influence, or some other installed extra.
In the code, I don’t see any “z-index” that are explicitly set.
The CSS file that ClientConfig loads is also nearly empty.
If you can reproduce the issue on another installation, then open an issue about this on Github.
Otherwise maybe just extend the CSS file from the extra, so that it works on your system.