Early in September, the front page of a client site we run sat for the better part of a day as nothing but lines of plain text. No banner, no layout — just the words. When we looked, a single flag marking the page as one built in Elementor (the design tool) had been wiped. That one flag was gone, and WordPress was ignoring the whole design and shipping only the text. The client had logged in, edited the page and hit save. A routine action had turned into something nobody expected.
The cause was simple. Saving from the default WordPress editing screen wiped the flag attached to that page. The design data was still sitting there untouched; the screen just had no reason to use it. This was not one site’s quirk — open an Elementor page in the default editor and save it, and the same thing can happen on any site.
Editing tools like WordPress and Elementor buy you convenience, and in exchange they lean on settings that are easy to disturb. That one save can erase a page’s design is not something the person who handed you the site has any reason to know. Knowing it, and closing the gap before it opens, is the job of the people who took it on. So we did two things. We built a guard that puts the flag straight back the moment a save strips it, and we rolled it out not just to this site but to every Elementor site we run. And when someone opens an Elementor page in the default editor, a notice now comes up first: edit this page in Elementor. We did not block the editor itself — when Elementor breaks, that screen is the last way in to fix a page.
There is no shortage of people who will take your site on. The difference shows up on a day like this one: whether you tell the client “only edit in Elementor” and leave it there, or change the structure so it cannot happen again. We chose the second, and this post is the record of it.