-
Notifications
You must be signed in to change notification settings - Fork 27
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
Radio settings #203
base: master
Are you sure you want to change the base?
Radio settings #203
Conversation
Add new radiogroup combo
This is cool. As far as that core fix goes, do we have to implement some kind of version check to prevent radiogroups from being used on <3.0.4? |
Probably a good idea! And also we should do the same for the 2.x branch, when modxcms/revolution#16467 is accepted. That version-check would need to go into this if-clause:
Correct? Do you know, if we have the MODX-version information there available? |
I've added a version compare function at the top of the file, so I can here more conveniently compare the versions: ClientConfig/assets/components/clientconfig/js/mgr/sections/home.js Lines 181 to 196 in 1d48f51
Even though the documentation says there should be a If an incompatible version is detected, I still had to work around the errors being thrown. So I hacked around them: ClientConfig/assets/components/clientconfig/js/mgr/sections/home.js Lines 225 to 236 in 1d48f51
I have just tested it in a 2.8.6 and a 2.8.8 setup. Still needs testing in v3. Would love to enable these new CC xtypes (yours especially) as soon as possible ❤️ |
Adds support for radiogroup-settings. See #202 for details.
Resolves #202
But needs to wait for modxcms/revolution#16404 to be accepted.