Page Builder Block error

Hello Will, thanks for choosing Bento! Does the warning appear right after entering edit mode for a new page (i.e. “ages -> Add New” admin section), or after a sequence of specific steps? In case the latter, could you please describe those steps? Thank you!

Hey, Even if I add new page or try to edit one that has PB block on it, the block doesn’t appear, as for error. Now the PHP error points to CMB2 plugin directory. Maybe is something wrong with my server(or apache config). I’ts hard to replicate because the error stands after fresh install of wp core, on two instances(two different websites with their own database). Still CMB2 doesn’t complain about running on other themes. Thank you!

Thanks for the details! I can’t seem to be able to reproduce the error, so since you’re currently on a localhost I can only suggest some directions for troubleshooting the situation:

– First, try commenting out line 46 in the theme’s main functions.php file like so:
// add_filter( 'cmb2_admin_init', 'bento_metaboxes' );

– If this removes the warning message, you can go to the /includes/admin/post-settings.php file which contains all CMB settings used by the theme, and try removing blocks one by one which look like this:

$bento_xxxx_xxxx->add_field(
// an array inside
);

This can help find the specific part of the code which produces the warning.

Alternatively, if your WP_DEBUG is currently set to ‘true’, you can always just set it to false to temporarily hide all php notices and warnings ??

Well, I’ll try that tomorrow, meanwhile, the debug stays :). I find that error triggers when I open the editor. The list for debug is long: `WARNING: wp-content/themes/bento/includes/metaboxes/includes/CMB2_Base.php:315 – date() expects at most 2 parameters, 3 given
include(‘wp-admin/edit-form-blocks.php’), the_block_editor_meta_boxes, do_meta_boxes, CMB2_hookup->metabox_callback, CMB2->show_form, CMB2->render_field, CMB2_Field->render_field, CMB2_Base->peform_param_callback, CMB2_Base->get_param_callback_result, CMB2_Base->do_callback, CMB2_Field->render_field_callback, CMB2_Types->render, CMB2_Types->_render, CMB2_Types->select, CMB2_Type_Select->render, CMB2_Type_Base->rendered, CMB2_Field->register_js_data, CMB2_JS::add_field_data, CMB2_Field->js_data, CMB2_Field->get_default, CMB2_Base->get_param_callback_result, CMB2_Base->do_callback, date’ . Still think that the server background causing the problem, had some outdated packages when I first installed wp and theme, also found a thread about SiteOrigin’s plugins that causes same error on a outdated php5.4. My was php7.0 at the time I get that. I also find some strange behavior of footer widgets that happen when switching themes and a error for this, but I will open another thread for it if I can replicate again. I’m not rushing, maybe I’ll try another server next week. Keep in touch, thanks.

Hi again. I guess, I need to answer. The error persist on a new server. It occurs when the page/ editor is opened. First I’ve installed classic editor which let me work with PageBuilder, the default don’t. Next, the debug, I found the block in “/bento/includes/admin/post-settings.php” “// Grid page settings” exactly the field ‘Order grid items by’ has a ‘date’ option. I’ve modified line 590 from 'default_cb' => 'date' to 'default_cb' => 'modified'
I do not know what this implies when u realy need to make the ordering because I do not know where to look. But for the moment error disappear. If you think about a better solution, let me know. Maybe parameters passed to ‘date’ are more than 2. Thanks!

Thank you very much for the update, Will! I will make sure the fix is added to the next version update of Bento.

My issue is when using the block editor to create or edit a page I can not use the SiteOrigin tool when adding a block.
When I try and add it I get this error:
“The block has encountered an error and cannot be previewed”
I have deactivated all SiteOrigin plug-ins and re-activated them with no change.
I tried two different themes and did not have this error, so I am thinking the ball is in your court.

Hello @craigthill, thanks for choosing Bento! The new Gutenberg editor which has been introduced into the WordPress core since version 5.0 is still quite raw, error like yours are commonly reported in various cases (see e.g. here and here). Since Gutenberg essentially serves the same purpose as Bento’s bundled content builder, we highly recommend using just one of them at a given time; you can force the classical editor with Bento’s Content Builder blocks by ticking the “Use Classic Editor for new posts” checkbox in the “Settings -> Page Builder” admin panel section.

Not sure why I want to go back to the classic editor as it is being dropped. Bento was my choice for the new block editor, but now you are saying go back ???

This from SiteOrigin:
When you get a moment, please could you reach out to Bento and let them know about this problem. The issue might be related to admin-scripts.js. If I prevent that file from being enqueued in Bento, the SiteOrigin Layout Block works. They can perhaps look there first. I’m sure they’ll be able to resolve quickly once they know about the issue.

I know very little about web design, just trying to use the tools available and moving forward, not backward.

Thank you for the details! My apologies, it’s indeed a bug on our end. We’ve fixed the issue and added some extra styles to the settings boxes in the post/page editing interface. The changes have already been submitted as a Bento theme update (version 2.1), which should go live shortly. You will be able to update via the “Appearance -> Themes” section in your WP admin. Cheers!

Hi, Thanks for the update. Anyway, the classic editor works better. The issue for which I opened the topic is resolved.

Oh, Great.. I look forward to the upgrade. I like the Bento Theme.

A slightly different question…
I know how to size the fonts that are the menu, but how can I make the fonts in the drop-down menus larger. They are a bit hard to read on mobile devices.

Thanks again.

@craigthill, @wylydoicu the update is now live ??

@craigthill regarding your question: the sub-menu font size is set in the theme’s CSS code, so you can override it by adding this snippet:
.primary-menu li .sub-menu { font-size: 14px; }

Yes, that worked fine. Thank you

Seems my old error is back… from 4 months ago. Cant edit in WP Gutenberg wit Site Origin… back then Site origin responded:

This from SiteOrigin:
When you get a moment, please could you reach out to Bento and let them know about this problem. The issue might be related to admin-scripts.js. If I prevent that file from being enqueued in Bento, the SiteOrigin Layout Block works. They can perhaps look there first. I’m sure they’ll be able to resolve quickly once they know about the issue.

Then you guys fixed the problem… noe its back. ???