Hi TagDiv Team,
Like some other users, I’m consistently getting the following error when editing new pages or the homepage (but not posts): Error at zones: 6(models): 0(dom) “The model does not match the content. Current state has involved an issue.”
This even happens immediately after I download one of your pre-built templates—even before adding any shortcodes.
What I discovered:
After some testing, I found that if I use the “Post Type Switcher” plugin to change the page type (in the Classic Editor) from Page → Cloud Template, the error in Composer disappears completely!
Once I do that:
I can edit the page in Composer without any errors.
The layout works as expected.
However:
The page is then removed from the Cloud Template list, since it’s technically no longer a “Page” it is a Cloud Template type.
It only displays properly if I access it through a URL like
https://example.com/tdb_templates/news
If I try to access it normally at https://example.com/news, I either get a blank page or a critical error.
My theory
It seems that posts don’t trigger this error because the Theme Panel → Templates section includes a redirect or link definition for posts and single templates. That likely ensures TagDiv Composer initializes the correct “zone” mapping.
For pages and the homepage, there’s no equivalent setting in the Theme Panel, so Composer may be loading the wrong internal model—hence the zone mismatch.
The problem
At the moment, I can’t create or edit any new pages or homepage layouts without this error.
Only posts work normally.
Possible solution idea
If my guess is right, perhaps the Composer needs a way to assign a Cloud Template mapping (like the Post templates) for Pages and Homepage in the Theme Panel. That might resolve the zone mismatch entirely.
Do you have any other workaround or insight on this?
It’s currently blocking all new page and homepage creation.
Thanks for your help!
I would add that I don’t get the problem in the 404 template. Changing its type doesn’t erase it from the Cloud Templates list, like it does for the Page Templates.
So something in how you are processing the template (and template list) for Pages is different.
After all that, the site had the Brizy plugin installed.
I deactivated it, and this problem may have gone away!
Hello,
I’m glad that the cause of the problems was finally found and the situation was resolved.
Thank you!
I am also getting the “Error at zones: 6(models) : 1(dom). The model does not match the content Current state has involved an issue.” error. What’s the best way to solve this problem?
Hi,
Most of the time, this issue is caused by a shortcode that isn’t compatible with our theme or by a plugin conflict. As a result, after you configure the page or cloud template with tagDiv Composer and save it, you may encounter this error the next time you try to edit it.
If the problem occurs on only one page or cloud template (including header or footer templates), it’s likely due to specific settings or shortcodes used there. You can test this by temporarily switching the header or footer to see if the issue persists. In many cases, the problem can be resolved by restoring a previous version of the page using the revision feature: https://wordpress.com/support/page-post-revisions/
Thank you!
In my case, the problem was caused by a WP Super Cache plugin. When you turn it off, the error disappears and everything works as it should.
