You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding the following code "breaks" the custom field suite plugin... any custom fields added with CFS disappear on that particular page editor (pages using the "landing.php" template) and you can't save new ones. Removing the following code makes the CFS fields visible again.
$featured_post_ids = new WPAlchemy_MetaBox(array
(
'id' => '_featured_posts',
'title' => 'Featured Blog Posts',
'context' => 'normal', // same as above, defaults to "normal"
'priority' => 'high', // same as above, defaults to "high"
'template' => get_stylesheet_directory() . '/metaboxes/full-meta.php',
'include_template' => array('landing.php')
));
The text was updated successfully, but these errors were encountered:
The issue was with the WP Alchemy repeating fields. Removing the the "foreach" loop solved the problem (but obviously took away the repeating fields). I set the "priority" to low and it solved the problem.
Although if I were to drag and drop the WP Alchemy meta box above the custom field suite boxes, the CFS boxes would break again.
So it appears there is a problem with the foreach() statement here: ( I also tried adding wp_reset_query() and rewind_posts() and no luck)
Adding the following code "breaks" the custom field suite plugin... any custom fields added with CFS disappear on that particular page editor (pages using the "landing.php" template) and you can't save new ones. Removing the following code makes the CFS fields visible again.
$featured_post_ids = new WPAlchemy_MetaBox(array
(
'id' => '_featured_posts',
'title' => 'Featured Blog Posts',
'context' => 'normal', // same as above, defaults to "normal"
'priority' => 'high', // same as above, defaults to "high"
'template' => get_stylesheet_directory() . '/metaboxes/full-meta.php',
'include_template' => array('landing.php')
));
The text was updated successfully, but these errors were encountered: