-
Notifications
You must be signed in to change notification settings - Fork 61
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
Any reason not to support option pages? #57
Comments
Sorry for the GH issue noise, but thanks for the two pointers above for getting this working on options pages. Just what I was needing. |
@pogla thanks for helping with the solution. Would you mind opening a PR
for such a change?
Den ons. 1. aug. 2018, 01:41 skrev Michael Beckwith <
[email protected]>:
Sorry for the GH issue noise, but thanks for the two pointers above for
getting this working on options pages. Just what I was needing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#57 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC7sAr73ugA8TbQAvttgQU38SVjm2Th0ks5uMOsqgaJpZM4UK76e>
.
--
*José Carlos*
|
@jcchavezs Sure: #59 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There seems to be no support for option pages by default. Is there any reason why not?
It can be added by modifying the cmb2-conditionals.js file with:
CMB2ConditionalsInit('.cmb2-options-page', '.cmb2-options-page .cmb-field-list');
And by adding the cmb2-conditional.js enqueu manually in the plugins. Now adding the enqueue is easy, but the JS code should exist in cmb2-conditionals.js by default so it doesn't have to be modified.
The text was updated successfully, but these errors were encountered: