Review and change Avada Global Options

MaintenanceAdvanced~15 min

Before you start

Plugin version 1.12.0 or newer with the Avada theme active, from an administrator connection: both tools need the manage-options capability, even where Avada's Role Manager opens Global Options to other roles. Update Avada Global Options is a destructive write and starts off, so switch it on only for the change. If a page cache plugin is active, plan to purge it afterwards.

Global Options is where an Avada site’s look lives: the width of the content, the brand colors, the heading fonts, the footer line with last year’s copyright. It is also a long screen of tabs, and changing one color means finding the right panel first. An agent can read the relevant options in one call and change just the ones you name.

These settings apply to the whole site at once, so this recipe always shows the current value next to the proposed one before anything is written.

The prompt
Read this site's Avada Global Options with avada-get-global-options and show
me the current site width, primary color, color palette, body and H1 to H3
typography, and the footer text (footer_text). Change nothing yet. If an option is
in not_set, say so, because Avada's built-in default applies there.
I want these changes: [primary color to #1d4ed8], [H2 font size to 32px],
[footer_text to "© 2026 Example Co"]. For each, show me the current
value beside the exact value you would send, in the form Avada stores it (a
typography change as only the sub-values that change). Wait for my go.
Then write them in one avada-update-global-options call. Give me the previous
values from the response and anything listed in not_restorable. Remind me to
purge the page cache if one is active.

Why this is safe to run

The read returns only the options on a fixed list, so a credential or code field cannot come back into the chat. You see every current value before a change is proposed, and options with no stored value are named in not_set so a blank is never mistaken for a setting.

The write is checked per value. A color must be a hex, rgba, hsla or an Avada color variable, site_width a number with px or %, the choice options one of their stored choices, the logo an image attachment id, and footer text HTML that a user without unfiltered HTML may only send when WordPress would not filter it. A value that fits no rule is refused and nothing is written, and every option you did not name is kept.

The change is site-wide the moment it saves, which is why the update is marked destructive and starts off. The previous values it returns are the way back: keep them until you have looked at the site. It needs the manage-options capability, so it never runs from a limited agent user, and the call lands in the Activity Log.

Already connected? From an admin connection, ask your agent for the “review and change Avada Global Options” recipe, name the options you want changed, and it runs the same read-first flow on your own site.

How it works

  1. Read the Global Options on the fixed list and show the current values.
  2. Draft each change in the form Avada stores it and wait for approval.
  3. Write only the approved options in one call.
  4. Keep the previous values the response returns, and any listed in not_restorable.
  5. Remind you to purge a page cache so visitors see the change.

Questions

Which options can it reach?
A fixed list: site width, layout, the primary, palette and link colors, body and heading typography, header position and layout, logo, page title bar, footer widgets, the footer text (footer_text; footer_copyright only switches the copyright bar on or off), responsive and maintenance mode. Maintenance mode can be read but not written. API keys, passwords, custom CSS and the head and body code fields are never returned or written.
How do I undo it?
The write returns the old value of every option that changed as previous, null where none was stored. Send that back as set to undo. A typography option stored as an empty array cannot be written back, and the response lists it under not_restorable. Global Options changes are not in the Changes tab.
Why does the site still look the same after the change?
Avada rebuilds its compiled CSS on the write, but a page cache plugin keeps serving its cached pages until you purge it.