WPBakery’s settings screen decides a lot that is easy to forget: which of its loading modes (hybrid, optimized or legacy) its CSS and JS use, whether Google Fonts come from Google or your own server, and which sitewide CSS gets added on top of every page. When a speed test or a privacy review raises one of these, you want the current value in front of you first.
This prompt reads the settings and changes only what you name.
Read this site's WPBakery settings with wpbakery-get-settings. Show mecss_loading, js_loading, local_google_fonts, google_fonts_subsets, the posttypes WPBakery's editor is on for, and whether any global custom CSS is set.Change nothing yet, and tell me which settings have no stored value.
I want [local_google_fonts on] and [css_loading set to optimized]. Show meeach current value beside the new one and wait for my go. Then write onlythose two with wpbakery-update-settings, and give me the previous values fromthe response so I can switch them back.Why this is safe to run
The read covers a fixed list of settings, and the global header and footer JS come back only for a user who may post unfiltered HTML. The license code is never returned.
The write runs each value through WPBakery’s own sanitize callback for that field and refuses a value the callback would change, so what you approved is what gets stored. The global custom_css is checked separately: CSS holding markup, or a < followed by another character where WPBakery would cut custom.css off, is refused. A value equal to what is stored is left alone.
These settings apply to the whole site at once, which is why the update starts off and is marked destructive. The previous values in the response are the undo. It needs the manage-options capability, so a limited agent user never reaches it, and the call is in the Activity Log.
Already connected? From an admin connection, ask your agent for the “review and change WPBakery settings” recipe, say which settings you want changed, and it runs the same read-first flow on your own site.