How To Fix The “Content Error” Message In The Builder
When you open a page in the Builder you may see a window titled Content Error with the text “Your page content could not be displayed as an Tirenoa Builder layout. Most likely that means, there is some invalid markup or shortcode in it.”
The message means that the Builder read the saved content of the page and could not turn it into containers, columns and elements. Your content is not deleted. It is still stored exactly as it was, and the page on the front end is not changed by the message. This guide is more technical than the others, because the repair happens in the raw content of the page.
In this article: What Happens When the Error Appears · Common Causes · Fix 1: Restore an Earlier Version · Fix 2: Repair the Content by Hand · If It Is the Unknown Error · How to Avoid It · Related
What Happens When the Error Appears
A Builder page is saved as text. Every container, column and element is written as a tag in square brackets with an opening part such as [tiaro_text] and a closing part such as [/tiaro_text], nested inside each other. To show the layout, the Builder has to read this text from top to bottom. If the structure is damaged, it stops.
- In the back-end Builder, the Content Error window opens and the page switches back to the default WordPress editor, so you can see the raw content.
- In the live editor, the window opens and the layout stays empty. A problem the Builder cannot name is shown as Unknown Error Occurred instead, with a link Click here to copy the full error message.
Note: Do not click Update or Publish while the layout is empty. Close the page without saving, or repair the content first. Saving an empty layout would overwrite the stored content.
Common Causes
- Content was edited by hand in the text view of the WordPress editor and a tag lost its closing part, a bracket or a quotation mark.
- Content was pasted from another site, a document or an email and brought broken or half-copied tags with it.
- A value that was changed by hand contains a character that breaks the structure, typically a square bracket or a straight double quote inside a tag.
- The page is very old and still contains a container tag named
[fullwidth]. This old format is not converted any more and always triggers the error.
Fix 1: Restore an Earlier Version
This is the fastest and safest way when the page worked before.
- Open the page in the WordPress editor (not the live editor).
- Open the Revisions of the page and step back to the last version from before the problem.
- Restore that revision.
- Open the Builder again. If the layout shows, redo the changes that were lost.
If the page has no revisions, a backup of the site is the next source. Contact Tiaro at https://tiaro.eu/contact/ and name the page and the day it last worked.
Fix 2: Repair the Content by Hand
- Before anything else, copy the complete raw content into a text file on your computer. This is your safety copy.
- In the back-end editor, make sure the Builder is switched off for the moment: the button at the top reads Back-end Builder when you are in the default editor. Switch the editor to its text view so you see the tags, not the formatted text.
- Check that every opening tag has its closing tag and that they close in the right order: element inside column, column inside row, row inside container.
- Look at the place you edited last. Most errors sit there: a missing
], a missing closing quote, or a tag cut in half. - If you cannot find the place, work by halves. Remove the lower half of the containers, save, and open the Builder. If it loads, the fault is in the part you removed; if not, it is in the part that is left. Put the content back from your safety copy and repeat with a smaller part until one container is left.
- Rebuild that one container in the Builder and delete the broken one.
Text that sits outside any container is not a fault. The Builder wraps loose text in a container, a column and a Text Block by itself when it opens the page.
If It Is the Unknown Error
The Unknown Error Occurred window in the live editor means the editor stopped for a reason it could not identify as a content error. Click the link to copy the full error message, try the page in the back-end Builder and in a private browser window, and send the copied message to Tiaro support at https://tiaro.eu/contact/ together with the address of the page.
How to Avoid It
- Edit Builder pages in the Builder, not in the text view of the WordPress editor.
- Paste foreign text as plain text into a Text Block, not into the raw content.
- Put code and unusual characters into the Code Block element, which stores them in a safe form.
