[BUG] Group skin with Elementor V4 (atomic) elements renders without styles
Support › MB Elementor Integrator › [BUG] Group skin with Elementor V4 (atomic) elements renders without styles
- This topic has 1 reply, 2 voices, and was last updated 1 day, 8 hours ago by
Peter.
-
AuthorPosts
-
November 16, 2026 at 4:26 PM #50284
Hello Dolly
ParticipantDescription
A group skin (
metabox_group_template) whose layout uses Elementor V4 atomic elements (for example ane-flexbox) renders on the front end without the styles of those elements: no background, no padding, nothing that was set on them in the editor. V3 widgets inside the same skin keep their styles.Cause
Elementor enqueues the styles of atomic elements (
uploads/elementor/css/local-{post id}-frontend-*.css) only for the documents announced through theelementor/post/renderaction before it enqueues the page's styles (Atomic_Styles_Manager, onelementor/frontend/after_enqueue_post_styles).Elementor Pro announces the templates nested in a rendered document in
ElementorPro\Modules\AtomicWidgets\Template_Styles, but it looks only for the settingstemplate_idandalternate_templates. The Meta Box Group widget keeps its skin inmb_skin_template, so the skin is never announced and its atomic styles are never enqueued. The skin is rendered later, inside the widget, throughget_builder_content_for_display(), when the styles have already been enqueued.Display conditions on the skin do not help: the Theme Builder announces one document per location (
single), and that is the single template containing the Group widget.Steps to reproduce
- Create a group skin, put an
e-flexboxin it with a background colour and some padding, and put the Meta Box dynamic widgets inside it. - Use the skin in a Meta Box Group widget on a single template.
- Open a post that uses that single template: the group items render, but the flexbox has no background and no padding, and the page links no
local-{skin id}-frontend-*.css.
Workaround
Announce the skins ourselves, the way Elementor Pro does for
template_id:add_action( 'elementor/post/render', function ( $post_id ) { static $seen = []; if ( isset( $seen[ $post_id ] ) ) { return; } $seen[ $post_id ] = true; $data = get_post_meta( $post_id, '_elementor_data', true ); if ( ! is_string( $data ) || false === strpos( $data, 'mb_skin_template' ) ) { return; } preg_match_all( '/"mb_skin_template":"(\d+)"/', $data, $matches ); foreach ( array_unique( $matches[1] ) as $skin_id ) { do_action( 'elementor/post/render', (int) $skin_id ); } }, 20 );With it the page links
local-{skin id}-frontend-*.cssand the skin renders as in the editor. It would be better in the plugin itself, possibly also through theelementor/document/related_postsfilter, which Elementor uses for the global classes and the cache invalidation of nested documents.Environment
MB Elementor Integrator 2.2.7 (the relevant code is unchanged in 2.2.8), Meta Box 5.15.2, Meta Box Group 1.4.7, Elementor 4.3.5, Elementor Pro 4.3.2.
November 16, 2026 at 11:22 PM #50287Peter
ModeratorHello,
Thanks for the detailed report.
I can reproduce it with MB Elementor Integrator 2.2.8, Elementor 4.4.0 and Elementor Pro 4.4.0, so newer Elementor versions don't fix it.
Your analysis is correct. When Elementor Pro looks for nested templates, it only checks
template_id,additional_template_selectandalternate_templates. Our Group widget stores the skin inmb_skin_template, so the skin never reacheselementor/post/renderbefore the styles are enqueued.I also tested your snippet. With it, the skin's CSS file loads and the flexbox renders as it does in the editor, so it's safe to keep using until we release a fix.
I've passed this to our development team to fix in the plugin, along with your note about the
elementor/document/related_postsfilter. I'll update you here when it's done. - Create a group skin, put an
-
AuthorPosts
- You must be logged in to reply to this topic.