(210) 346-0848hello@datacram.com

Theme repair · Astra

Astra Theme Problems: How to Fix a Site That Stopped Behaving

Astra is rarely the part that broke. It is a light frame with three other systems leaning on it: a page builder, the Customizer and a Pro add-on. Each has an opinion about how wide your page should be, and repair starts by finding out which opinion won.

Sort out my Astra siteWhy it happens
wp-admin · astra settings
Layout audit
Three settings, one page width
Audit
Astra global containerBoxed · 1200px
Page layout overrideFull width
Builder section widthBoxed · 1140px
Additional CSS lines418
Mobile header layoutNever set
Astra Pro licenseLapsed
Width rules in conflict3
Illustrative — one page, three width settings disagreeingfixable in place

Signs the trouble sits in Astra's settings

  • Pages lost their width or sidebar after an update
  • Customizer changes save, then quietly revert
  • The header looks right on desktop and wrong on a phone
  • A starter template import stopped halfway through
  • The same setting lives in Astra and in the builder, with different values
  • Pro features vanished and nobody knows when the license lapsed

Why Astra sites drift out of shape

Most common first, each with a way to check it yourself.

  1. 1

    Astra and the page builder both set the layout

    Astra has a global container width, a per-page layout override in the editor sidebar and its own spacing rules. Elementor or another builder adds a second set on top. When they disagree, the browser settles the argument with CSS nobody chose on purpose, and an update can change the outcome overnight.

    Check it: Open a broken page, read the Astra settings panel in the editor sidebar, then check the builder's section width. If they name different widths, start here.

  2. 2

    Customizer saves that fail or look ignored

    Astra keeps its Customizer choices together in the database, and a large site sends a lot of them in a single save. A low server input limit or an overeager security plugin can make the save fail. A cache serving the old stylesheet can make a good save look like it never happened.

    Check it: Save a change, then load the site in a private window. If the change shows there, it was cache. If it is missing when you reopen the Customizer, the save itself failed.

  3. 3

    A header built for one screen size

    Astra's header and footer builder keeps separate desktop and mobile layouts. Owners perfect the desktop header and never open the mobile one. On other sites a Pro custom layout or a builder's own header template sits over Astra's and hides it entirely.

    Check it: In the Customizer, switch the preview to mobile while the header builder is open. If it looks nothing like what you set, the mobile layout was never built.

  4. 4

    Starter template imports that half-finished

    A Starter Templates import installs plugins, downloads images, writes Customizer settings and creates pages in one long run. Budget hosting often times out partway, leaving placeholder pages, missing images and a Customizer that belongs to a different demo.

    Check it: Look in Pages for drafts and duplicates you did not create, and in the Media Library for broken thumbnails dated the day of the import.

  5. 5

    The Pro add-on stopped updating

    Astra Pro is a separate plugin with its own license. When the license lapses, the free theme keeps updating and Pro does not, so the two slowly fall out of step. Features built on Pro modules, such as mega menus and custom layouts, are the first to misbehave.

    Check it: In Plugins, see whether Astra Pro shows an update it cannot install. A license prompt in place of an update link means the key has lapsed.

  6. 6

    Custom CSS scattered across four homes

    Some rules sit in Additional CSS, some in the builder's custom CSS box, some in a child theme and some in a snippets plugin installed for one fix and never mentioned again. When a rule stops working, nobody knows where to look.

    Check it: Count the places your site holds custom CSS: Additional CSS, the builder's settings, the child theme and any code-snippet plugin. More than two is part of the problem.

Do this today

Take a full backup, then write down the versions of Astra, Astra Pro and your builder from the Themes and Plugins screens. Half of any diagnosis is knowing what changed, and those three numbers usually point at it.

How we untangle an Astra site

  1. 1

    Map who controls what

    We list every setting that touches layout, from Astra's global container to per-page overrides and the builder's own widths, and note which one actually wins on each template.

  2. 2

    Work on a staging copy

    Every change happens on a copy of the live site, with a fresh backup behind it, so a repair cannot turn into an outage.

  3. 3

    Pick one source of truth

    Astra owns the frame and the builder owns the content, or the reverse. We choose deliberately, then remove the duplicate settings that fight the choice.

  4. 4

    Update in order and test

    Theme, Pro add-on, builder and plugins go one at a time, with the key templates checked on desktop and phone after each.

What an Astra repair covers

Layout and width reconciled

Global container, page overrides and builder sections brought into agreement, so a new page looks right without hand-tuning.

Headers and footers for every screen

Desktop and mobile layouts set on purpose, with any competing header template removed.

Settings backed up, licenses current

A copy of the Customizer settings kept outside the site, and Astra Pro and builder licenses renewed or retired cleanly.

CSS gathered into one place

Scattered rules moved into a child theme or a single stylesheet, with dead rules deleted rather than overridden.

Repair it, or start over?

The honest answer depends on the site, not on what we would rather sell.

Repair it when

  • The site runs the free theme plus one builder and is a few years old at most
  • Problems began after a specific update or template import
  • The design still suits the business and only the behavior is off
  • Your team edits it comfortably once it works

Rebuild it when

  • Two page builders are active and nobody remembers why
  • Every page was hand-tuned because the global settings never held
  • Speed stays poor even after the layout conflicts are cleared
  • You pay for Pro, a builder and add-ons to get what a custom site includes

When to bring someone in

Call when a fix in one place keeps breaking something in another. That pattern means two systems share a job, and patching either one alone will not end it. Call as well before importing a new starter template over a live site, because an import writes over settings and undoing it by hand is slow.

Sort out my Astra siteCall (210) 346-0848
Free · No obligation

Is it Astra, the builder or both?

Tell us what changed and what the site does now. We will name the layer at fault and tell you whether it is a quick repair or a bigger conversation.

Which of these sounds like you? (pick any)

Frequently asked

No. Astra is a theme: it sets the header, footer, container and typography. The layouts inside each page usually come from the block editor, Elementor or another builder. That split is why an Astra problem is so often a handoff problem between two tools.

Only if you use what it adds, such as mega menus, extra header options or custom layouts on chosen pages. Plenty of sites bought it once and never switched on a Pro module. If Pro features are in use, keep the license active so it updates alongside the free theme.

Usually a changed default, a page override that stopped applying, or cached CSS from the previous version. Clear caches first. If the layout is still wrong, compare the page's Astra settings panel with the global container setting; our guide to a theme that broke after an update covers the recovery.

You can, but treat it as a redesign rather than a refresh. A full import changes Customizer settings, adds pages and may install plugins. Run it on a staging copy, keep a backup and move your content across deliberately.

Not because of a bug. Astra is actively maintained and light on its own. On a builder site most of the weight lives in the builder and the plugins, so swapping the theme rarely fixes much. If the foundation is going to change, rethink the whole stack at once.

A settings conflict or a header problem is often sorted within a few days. A site with a half-finished import, two builders and years of scattered CSS takes longer, and after the first look we will tell you whether repairing it is worth the time.

Keep reading

CallGet a quote