Expected Behavior:
When creating an options page using \new_cmb2_box() give ability to define the autoloader, so devs could define that those options should NOT be autoloaded.
As a developer, you know the drawbacks of autoload=yes.
Actual Behavior:
currently it defaults to yes
Steps to reproduce (I have confirmed I can reproduce this issue on the trunk branch):
Use the https://github.com/CMB2/CMB2-Snippet-Library/blob/master/options-and-settings-pages/options-pages-with-tabs-and-submenus.php snippet and save options.
Expected Behavior:
When creating an options page using
\new_cmb2_box()give ability to define theautoloader, so devs could define that those options should NOT be autoloaded.As a developer, you know the drawbacks of
autoload=yes.Actual Behavior:
currently it defaults to
yesSteps to reproduce (I have confirmed I can reproduce this issue on the trunk branch):
Use the https://github.com/CMB2/CMB2-Snippet-Library/blob/master/options-and-settings-pages/options-pages-with-tabs-and-submenus.php snippet and save options.