Four layers can change a page after an update
A page built with Elementor is the product of stored layout settings, generated style files, the theme and any add-ons that add widgets. The developer documentation explains that Elementor keeps style settings in the database and builds CSS files from them in a folder under the uploads directory. An update can change any layer without changing the others: the generated files may be stale, an add-on may output different markup, the theme may style a class differently, and a cache may serve an old copy. Treating the symptom ("it looks wrong") as a single cause is why people click every button and still cannot say what fixed it.
- Stored settings: what the editor shows.
- Generated files: what the live page loads.
- Theme and add-ons: markup and rules around the page.
- Caches: server, plugin and browser copies of all of it.
The clear-files tool and why its name keeps changing
The tool that deletes generated style files has had several names. Elementor's 3.28 beta announcement describes the button under Elementor, Tools, General labelled Regenerate CSS & Data being renamed Clear Cache, clearing CSS files, data from deleted post assets and element caching data, with a second button added to the admin bar. Help pages still use Clear files & data and Regenerate Files & Data, sometimes within one article, so look for the button on your own screen rather than for a fixed label. The command line equivalent is wp elementor flush-css, which by default only removes files and lets Elementor rebuild them when each page is next visited; adding --regenerate builds them immediately, and --network applies it across a multisite network.
- Clear the tool first, then your site cache, then hard-refresh the browser.
- Do this on staging while comparing against a baseline, so you know whether it changed anything.
Section and container layouts behave differently
Elementor's help notes that the container is now the default layout element. Columns always fill the full width of their section, so two columns at 50 percent each fill the row, whereas nested containers can be wider or narrower than their parent and can run vertically or horizontally. A page built from sections and columns can therefore look different if part of it is rebuilt with containers, or if an add-on changes which structure it emits. Phones add another rule: two-column container layouts stack vertically by default, and reversing the order is done with a Direction: Column Reversed setting in the Items section of the parent container's Layout tab. Hiding an element for a device is under Advanced, then Responsive.
- Compare the same section at desktop, tablet and phone width.
- A gap that appears only at one width points to a responsive setting, not to the update.
Requirements that quietly matter
Elementor's requirements page lists PHP 7.4 or greater and advises PHP 8.x, and a WordPress memory limit of 256 MB as the minimum, 512 MB recommended and 768 MB for best performance, adding that plugins such as WooCommerce can raise the need to 512 MB. An editor that loads slowly or a page that saves incompletely after an update can be a memory limit, not a layout fault. Memory limits are set by the host or the site configuration, so the fix is a hosting setting rather than a layout change.
- Read the PHP and memory values under Tools, Site Health, Info.
- If saving fails or stops partway, check the PHP log for memory messages.
What the paid job covers and how it is accepted
The layout job has a published test price of GBP 295 for up to eight pages and one header or footer template. It starts from a baseline you supply, compares each page at three widths, names the cause and restores the layout on a staging copy against a checklist of up to twelve visible items per page. It does not redesign pages, convert a whole site between layout types, fix an editor that will not open or tune speed. Prices are untested proposals and payment follows the agreed checks.
- Send page addresses, before screenshots, what was updated and when, never logins.
- If the editor will not load or a fatal error shows, use the conflict job instead.
Sources and limits
- Elementor developer docs: flush-css command Checked 2026-10-11.
- Elementor stores style settings in the database and builds CSS files in /wp-content/uploads/elementor/css/; wp elementor flush-css [--regenerate] [--network] removes the cached stylesheets, and without --regenerate Elementor creates the updated files when a page is next visited.
- Elementor 3.28 beta announcement Checked 2026-10-11.
- In Elementor 3.28 the button under Elementor, Tools, General labelled Regenerate CSS & Data was renamed Clear Cache; it clears CSS files, data left from deleted post assets and element caching data, and a second button was added to the admin bar.
- Elementor help: resolve common mobile layout issues Checked 2026-10-11.
- Two-column Flexbox Container layouts stack vertically on phones by default and can be reversed with the Direction: Column Reversed icon; elements can be hidden per device under Advanced, Responsive; the page uses both Regenerate Files & Data and Clear files & data as names for the clearing tool.
- Elementor help: transitioning from sections to containers Checked 2026-10-11.
- Columns always fill the full width of their section whereas nested containers can be wider or narrower than their parent; containers let you choose vertical or horizontal direction; the container is now Elementor's default layout element.
- Elementor help: system requirements Checked 2026-10-11.
- It lists PHP 7.4 or greater with PHP 8.x advised, and a WordPress memory limit of 256 MB minimum, 512 MB recommended and 768 MB for best performance; plugins such as WooCommerce can raise the need to 512 MB.