Avada MCP: Global Options, AWB colour and type tokens, Fusion Slider

Swapping a Fusion Slider campaign without opening the builder

The most frequent Avada request on an established site is seasonal: new headline, new button link, new background on the home slider, and back again when the sale ends. Through GoBuildWP that is slider work, not page work. avada-list-sliders gives each slider's slug and slide count, avada-get-slider shows its settings and the slides assigned to it, and avada-get-slide returns one slide's full _fusion bag along with the featured image that serves as its background.

Slide text and links are writable keys: heading and caption as plain text, their sizes and colours, link_type as button, image or none, slide_link and slide_target. Media routing is a key too, so a slide can switch between an image and a YouTube, Vimeo or MP4 background. The background image itself is the slide post's featured image, so replacing it is a set-featured-image call on the slide rather than an Avada setting. Because avada-edit-slide rejects the whole batch when any key is unknown or any value fails its type, a typo never leaves a slide half-updated.

• Read every slide you will change first and keep the output; that is the record for putting the campaign back.
• Slide edits restore from the ledger. Slider settings such as autoplay, slideshow_speed and animation do not, because they live in term meta.
• Check the slider on a phone as well, since aspect ratio and font sizes behave differently there.

Which Global Options the Avada writer accepts

avada-set-theme-options is deliberately narrow. Its allowlist covers the scalar settings people actually ask to change: primary and secondary colour, body text, link and hover colours, separator and border colours, site layout and width, main padding, header position, layout and sticky behaviour, footer columns and display, and switches such as the lightbox, Google Maps, the to-top button and the preloader. Everything else in fusion_options is readable through avada-get-theme-options, tab by tab, but not writable here.

That split is useful when scoping a job. If a request maps onto the allowlist and the AWB colour and typography presets, an agent can do it and the ledger can restore the row. If it needs anything else, such as custom CSS, a specific header element or a Template Builder layout, plan for it to be done in Avada's own screens. The response's written and unchanged lists also show when a requested value was already in place, which is common on sites where the client is describing something they already set months ago.

Multilingual Avada sites and the options row

On WPML or Polylang installs Avada keeps a separate options row per language, suffixed with the language code. GoBuildWP's Avada abilities read and write the unsuffixed fusion_options row; per-language rows are not part of the ability surface, because which language is active depends on the request. Reading them is an execute-php job, and any change made through the abilities should be checked on each language version of the site before you call it done. A colour that changed in English and not in German usually means the second row was never touched, not that the cache is stale.

Portfolio and FAQ inventories

avada-list-portfolio-items and avada-list-faqs are inventory tools: ids, titles, slugs, status, modified dates and, for portfolio items, the first portfolio category. They answer audit questions such as which FAQs are still drafts or which portfolio entries have not been touched in years. Full content comes from get-content, and it is often Avada Builder markup, so edits to those bodies belong in the builder unless the change is plain text the agent can locate exactly.