Error at rows: 7(models) : 1(dom). The model does not match the content

Dear TagDiv,

We are encountering this issue too on our test environement, but not on the production environement because they are essentially clones of one another… Both settings & securitywise they are identical, yet on the test environement, things go awry.

We have already disabled all other plugins and checked our security settings. Still the problem persists. We also encounter the problem on brand new pages without any form of content/shortcodes.

Error at zones: 6(models) : 0(dom). The model does not match the content Current state has involved an issue.

Sadly, due to security reasons, we are not able to provide access to external parties, which makes this problem all the more difficult to solve.

Do you have any suggestions how we can debug this matter further?
Could you also inform us what the ‘zones’ in this error refer to?

Thank you in advance
Kind regards

• This reply was modified 4 years by CarolienBovyn.

Hey, I get the Same Errors, but I had a solution for it.

I never got the error when editing the template in “Draft” status.

I brought templates that had already been published back into draft status for editing and was then able to use the TD Composer. Everything was fine then.

Since the last update, however, I can no longer return the templates to the draft status. The only option I have in the status dropdown is “Published”. However, I can return posts and pages to draft mode as normal, except for templates.

Is that a bug or is it intentional?

Any update regarding this?

• This reply was modified 3 years by themes10.

Hello Everyone,

I was experiencing the same issue and found a solution after monitoring the browser’s console and making changes to my webserver’s configuration.

The following error appeared whenever I went to edit a page with the tagDiv Composer:

Error at zones: 6(models) : 0(dom). The model does not match the content Current state has involved an issue. You could try an UNDO operation (CTRL+Z / CTRL+SHIFT+Z)

I decided to look at the browser’s console while the tagDiv composer page was loaded to see if I could find out what was causing the problem. I saw the following error in the console:

The loading of “https://www.mywebsite.com/tdb_templates/404-template-week-pro/?td_action=tdc_edit&post_id=89&tdbTemplateType=404” in a frame is denied by “X-Frame-Options“ directive set to “DENY“.

Apparently the tagdiv editor uses an xframe and my webserver (Nginx) was configured to deny all xframes. After visiting https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options and following the instructions I was able to get the editor working.

The specific configuration line in NGINX’s server configuration that was causing the problem was:

add_header X-Frame-Options “DENY”;

I deleted this line and replaced it with:

add_header X-Frame-Options SAMEORIGIN always;

After doing this I restarted NGINX and the tagdiv editor proceeded to work as normal.

• This reply was modified 3 years by mediagod.

Hi,

How i can edit the page with TagDiv Composer, i have this error when i try to edit the page ( https://prnt.sc/CC7CFE6sw9y0 ). ” Errors at inner columns: 1(models) : 0(dom). The model does not match the content Current state has involved an issue. You could try an UNDO operation (CTRL+Z / CTRL+SHIFT+Z) “. I deactivated all the plugin one by one and nothing, error persist.

Regards,
Bobby

any solution to this? getting similar error 🙁
Error at zones: 6(models) : 0(dom). The model does not match the content Current state has involved an issue. You could try an UNDO operation (CTRL+Z / CTRL+SHIFT+Z)

Nespaper 12.6、PHP 7.4.7

the same tagDiv Composer not working,

Errors at columns elements: 4(models) : 3(dom). The model does not match the content Current state has involved an issue. You could try an UNDO operation (CTRL+Z / CTRL+SHIFT+Z)

plz tell me how to fix it, thanks.