Skip to content

[wpmlpb-878] Stop managing the WPBakery custom CSS fields - #561

Merged
dgwatkins merged 1 commit into
masterfrom
chai/wpmlpb-878
Aug 12, 2026
Merged

[wpmlpb-878] Stop managing the WPBakery custom CSS fields#561
dgwatkins merged 1 commit into
masterfrom
chai/wpmlpb-878

Conversation

@dgwatkins

Copy link
Copy Markdown
Collaborator

WPML integration will handle it directly.

https://onthegosystems.myjetbrains.com/youtrack/issue/wpmlpb-878/

WPML copies `_wpb_shortcodes_custom_css` to every translation, but a page
translated with the native editor has to keep its own CSS, so the WPML Page
Builders integration has been overriding this to "copy once" in memory on every
request since 2022 — the change these files were always meant to carry.

Re-asserting that preference per request is what makes WPML compose the whole
custom-field preference map on WPBakery sites (wpmldev-7467). Declaring the
fields as ignored removes the conflict at the source: the integration owns the
copy for both flows — refreshing a translation-editor translation on every save,
and giving a natively translated page one copy that it keeps afterwards.

`_wpb_post_custom_css` is added because the integration handles it the same way
and it was never declared here.

This has to reach live sites before WPML Page Builders 3.0 ships. The current
builds are unaffected: their in-memory override still wins.

https://onthegosystems.myjetbrains.com/youtrack/issue/wpmlpb-878/

Co-authored-by: Chai <david.gw@onthegosystems.com>
@dgwatkins
dgwatkins merged commit c12752d into master Aug 12, 2026
1 check passed
@dgwatkins
dgwatkins deleted the chai/wpmlpb-878 branch August 12, 2026 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant