Any reason not to support option pages?
asadkn opened this issue · comments
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.
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 <
notifications@github.com>:
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