Astra fix

Astra Customizer Not Saving, or Settings Keep Resetting?

Three different failures hide behind 'the Customizer will not save'. The save was refused, the save worked and something is showing you the old result, or the settings were replaced by an import, a reset or a theme switch. Each leaves different evidence, and Astra makes them easy to tell apart once you know where it keeps things.

wp-admin · customize · astra
Save check
The save is refused before it lands
Blocked
  • FailPublish request403 refused
  • FailHeader HTML elementcontains script
  • WarnSecurity plugin firewallactive
  • WarnSettings export on filenever taken
  • PassPending draftsnone
  • PassEditing locknone
Illustrative — one blocked request, no error on screen2 failing

What you are seeing

  • The Publish button spins and never turns to Published
  • A change shows in the preview and is gone after a reload
  • Colors and fonts held, but the logo and menus disappeared
  • Everything returned to Astra's defaults overnight
  • A message says someone else is already customizing the site

Why it happens on Astra

Most common first.

  1. 1

    The save request was blocked on the way in

    Publishing sends every pending change to admin-ajax.php in a single request. A web application firewall or a security plugin can reject it, most often when an HTML element in the header builder or a script field contains code that resembles an attack. The Customizer has no good way to report this, so the button simply spins.

  2. 2

    The change is sitting in a draft or an autosave

    The gear beside Publish lets a set of changes be saved as a draft or scheduled for later. WordPress also keeps an autosaved copy and offers to restore it on the next visit. In both cases the work exists and the public site never received it, and the next person to open the Customizer may throw it away.

  3. 3

    The save worked and an older stylesheet is in circulation

    Astra turns Customizer choices into CSS, printed into the page or, with Astra Pro's file generation switched on, written to a file in the uploads folder. A page cache holding the earlier page, or a generated file that was never refreshed, keeps the old look alive. On hosts with a persistent object cache, a stale copy of the settings themselves can linger too.

  4. 4

    A child theme was activated and some settings stayed behind

    Astra keeps its own options, such as colors, typography and header layout, in one database record that parent and child share. WordPress stores the logo, the menu locations and Additional CSS per theme. Activate a child theme and the Astra options carry over while those three appear to vanish. They are still attached to the parent.

  5. 5

    An import or a reset replaced them

    A Starter Templates import writes the template's Customizer settings over yours. A reset plugin, or a database cleanup that deletes Astra's settings record, returns the theme to defaults in one stroke. Neither leaves a note. The clue is that everything changed at once, on a date somebody can usually recall.

How to fix it, in order

Least invasive first. Stop at the step that fixes it.

  1. 1

    Export what you have before testing anything

    Brainstorm Force publishes a free plugin, Import / Export Customizer Settings, that saves Astra's options to a file. Run an export now, even if the settings are partly wrong, and take an ordinary backup beside it. Every later step is safer with a copy to return to.

  2. 2

    Work out which failure you have

    Change one obvious thing, such as a theme color under Appearance, Customize, Global, Colors, and click Publish. Close the Customizer and open it again. If your new color is still set, saving works and the fault is in what gets displayed. If it reverted, the save never landed.

  3. 3

    Watch the save request

    Open the browser's developer tools on the Network tab, click Publish and find the admin-ajax.php request. A 403 means a firewall or security plugin refused it. A 500 or a timeout points at the server. A 200 that carries an error in its response usually names the setting that failed validation.

  4. 4

    Remove what the firewall objects to

    If the request is refused, pause the security plugin and try once more. If that cures it, look at HTML elements in the header and footer builder, since embedded code there is the usual trigger. Move tracking scripts to a tag manager, and ask the host to allow the Customizer save if the block sits at server level.

  5. 5

    Publish drafts and settle autosaves

    Click the gear beside the Publish button and check whether the action reads Save Draft or Schedule. Set it to Publish. If WordPress offers to restore an autosave, restore it, review it and publish, or dismiss it on purpose. If a colleague holds the Customizer, agree who is editing before anyone takes over.

  6. 6

    Refresh generated CSS and reunite split settings

    For a save that worked and does not show, purge caches and refresh Astra Pro's CSS File Generation where it is enabled. After a child theme switch, reassign menus under Appearance, Menus, Manage Locations, set the logo again in the Customizer and copy Additional CSS across from the parent.

Keep it from coming back

  • Export Astra's settings before imports, theme switches and redesigns
  • Keep scripts out of header HTML elements and in a tag manager
  • Let one person edit the Customizer at a time
  • Activate the child theme on day one, before settings pile up

The permanent fix

A faster Next.js build, with a CMS made for your business

If the Customizer holds hundreds of settings and nobody presses Publish without an export in hand, the design lives in a database record instead of anything a person can read. That is workable, and it is fragile. In a Next.js build the design is code under version control, so every change is recorded and reversible, and the custom CMS your team logs into edits content only.

On Astra todayOn Next.js with a custom CMS
What you keep updatedWordPress, the theme, its builder and every bundled plugin, all in stepNothing on a schedule. There is no theme or plugin stack to fall out of step
How a page is servedBuilt from the database on each visit, through the theme and its builderBuilt ahead of time and served as finished files from servers near the visitor
How you edit itA general-purpose builder with every option the theme shipsA CMS built around what your business actually changes: services, prices, photos, posts
What can break itAn update to any one of those parts, or a license that lapsesA change someone makes on purpose, tested before it goes live

Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.

Free · No obligation

Want this fixed on your Astra site?

Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.

Which of these sounds like you? (pick any)

Frequently asked

Astra's own options sit together in one record in the WordPress options table, shared by the parent theme and any child theme. A few items belong to WordPress instead and are stored per theme: the logo, menu locations and Additional CSS. That split explains most cases where some settings survive a change and others do not.

Most of them did not. Colors, typography and layout carry over because parent and child read the same Astra record. The logo, the menus assigned to each location and Additional CSS are tied to the theme that was active when you set them. Reassign those and the site is whole again.

Yes. Firewalls inspect what is being submitted, and a Customizer save carrying HTML or script from a header element can look like an injection attempt. The save is refused with a 403 that only appears in the browser's network panel. Pausing the plugin for one test confirms it.

Use an export. Brainstorm Force's Import / Export Customizer Settings plugin writes Astra's options to a file you can keep off the site and import later. A full site backup covers them too, but an export is quicker to restore when the design settings are the only thing that went wrong.

Keep reading

CallGet a quote