Identify whether the stale representation is the document, stylesheet or selected template before regenerating anything.
Create a meaningful comparison
On staging, change a visible test heading and one style, then publish. Compare the editor, a logged-in frontend visit and a clean logged-out visit. Use the same final URL and viewport. The editor canvas is not the delivered public document. Record both the heading text and the style so the experiment distinguishes stale content from stale presentation.
Inspect HTML before visual styling
Open the guest document response and search for the test heading. If the text remains old, investigate the page response or publication state. If the text is current but its style is old, inspect the applied rule and stylesheet request. Also confirm that the expected template is assigned. A fresh editor view cannot establish that guests receive the same template or asset.
Trace generated-file ownership
Identify the stylesheet that contains the changed rule and record its response URL, status and content. Use Elementor’s documented file/data clearing tool for your installed version when regeneration is appropriate. Preserve the test baseline first. Do not delete generated directories manually or treat a cache-busting query parameter as a guaranteed bypass; provider cache rules differ.
Invalidate the affected delivery path
After generated output is correct, clear affected entries through the cache owners’ supported controls. Check application, host and CDN layers separately. An old document can reference an old stylesheet even while the new file exists. Ask the owner about automatic invalidation after edits rather than making global purges the permanent editorial workflow.
Verify another edit without manual rescue
Repeat the heading/style experiment after the proposed correction. Test a clean guest visit, normal repeat navigation and a second page sharing the template. Restore the test content and check that restoration propagates too. Save the URL, edit timestamp, generated file and cache signals for support if the problem recurs.
Symptom-to-cause worksheet
| What you observe | What to investigate | Next check |
|---|---|---|
| Guest HTML old | Document cache or publication issue | Search response for the changed heading |
| HTML new, style old | Generated or delivered CSS stale | Inspect the applied rule’s source |
| Only one page differs | Template assignment or per-page asset | Compare its template and asset URL |
Worked investigation scenario
Illustrative investigation, not a measured Velonic result. Imagine the guest response contains the new heading but the old color. Regenerating HTML repeatedly cannot resolve a stylesheet that still contains the previous rule. Verify the generated CSS first, then its delivered copy, and repeat the edit. The acceptance test includes a second normal publication without a manual full-site purge; that establishes whether the ongoing edit workflow is repaired.
Put it into practice
- Compare content and style separately.
- Use documented builder regeneration controls.
- Repeat publication without a global purge.
AI-assisted educational content prepared for the Velonic resource library. How these guides are prepared.