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

Hi Simon,

When I added page empty, and them select it on page template – still I have an error 🙁

Regards

Hi Simion,

this did the job, it works great …. however: HEADER MANAGER doesn’t work on Safari for MacOS, it’s not ‘orange’ and when pressing nothing happens. If I use Chrome for MacOS it does work.

Is this a known issue or am I doing something wrong?

Kind regards,

Marcel.

I’ve got this error too: Errors at columns: 1(models) : 14(dom). The model does not match the content.

The tagdiv editor does not open at all at my homepage. What to do?

Simon,

It is very important, because i not to be able to change anything on existing page or create new page with tagdiv composer

• This reply was modified 7 years by Rafiki23.

In my case it is not due to an updated theme, because I am still running 9.2.2
But I came across this page here: https://forum.tagdiv.com/tagdiv-composer-not-working/
There it says: “This error appears in the tagDiv Composer page builder screen when you are trying to edit a page that contains unsupported shortcodes. The most frequent cases are: the page was modified in the backend by adding code or scripts directly through the TinyMCE editor or if you’ve inserted HTML code with missing tags. ”

This is what I was thinking when I saw that error. The error message to me sounded like an inconsistecy of parsed data that doesn’t match an expected syntax.

Just that I don’t think I edited the content manually outside the Composer.

But just as a suggestion: If the Composer really encounters an unexpected element, then it would be helpful to have a message like ‘Illegal tag xyz found’ or ‘Parsing error at position 232’ or something that can help me track down the error.
Maybe you could consider that for future versions.

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

getting the same error. I am not even using any child theme. Any work around for this ?

Now I was able to solve the issue on my own:
I just recreated the page from scratch. Now I will never know what the actual problem was, but what matters to me is that I now edit my page again 🙂

But again: My suggestion to the development team is to please improve the error messages. Errors can always happen (nobody is perfect) but if we get more explicit error messages it will be alot easier to track down and fix issues.

Hi,

I was having the same problem after inserting some HTML into a page, just to test an idea I had.

However, the Error at rows: N(models) : N(dom) error only showed up after some time. I was able to close and open the same page multiple times over a considerable length of time before I encountered the error. Despite this, I could still view the page in a browser without error, open it up to edit but not switch over to tagDiv Composer. Does, the tagDiv Composer parser not work in real time?

In the referenced article. Solution 1, reads – “Clean the code. Recreate the element with the tagDiv Composer. If you need to add other items that are not present in the tagDiv Composer elements list, please use a “Column text” element”

So,
1. I created a blank page
2. Switched to tagDiv Composer and added a Column Text element to the column.
3. Did nothing else and viewed the page in a browser.
4. Viewed the source code and validated the HTML at https://validator.w3.org/#validate_by_input

The generated HTML gave the following errors.

Error 20: Error: Saw ” when expecting an attribute name. Probable cause: = missing immediately before.
At line 702, column 228
5c87fc6780fc6″ “><div class=”t

Error 21: Warning: Attribute ” is not serializable as XML 1.0.
From line 702, column 34; to line 702, column 229
_wrapper”><div class=”wpb_wrapper wpb_text_column td_block_wrap td_block_wrap vc_column_text td_uid_5_5c87fc6780fc6_rand td-pb-border-top td_block_template_1″ data-td-block-uid=”td_uid_5_5c87fc6780fc6″ “><div c

Error 22: Error: Attribute ” not allowed on element div at this point.
From line 702, column 34; to line 702, column 229
_wrapper”><div class=”wpb_wrapper wpb_text_column td_block_wrap td_block_wrap vc_column_text td_uid_5_5c87fc6780fc6_rand td-pb-border-top td_block_template_1″ data-td-block-uid=”td_uid_5_5c87fc6780fc6″ “><div c
Attributes for element div:
Global attributes

The snippet of generated HTML that contains the extra double quotes is below:

1. <div class="vc_column td_uid_3_5c86d993cbb42_rand wpb_column vc_column_container tdc-column td-pb-span12">
2. <div class="wpb_wrapper">
3. <div class="wpb_wrapper wpb_text_column td_block_wrap td_block_wrap vc_column_text td_uid_4_5c86d993cbc72_rand td-pb-border-top td_block_template_1" data-td-block-uid="td_uid_4_5c86d993cbc72" ">
4. <div class="td-block-title-wrap"></div>
5. <div class="td-fix-index">
6. <p>Html code here! Replace this with any non empty text and that's it.</p>
7. </div>
8. </div>
9. </div>
10. </div>
11.

Could the generated double quote ” at line 3 above be a cause for the Error at rows: N(models) : N(dom) as my HTML text editor is unable to match up the opening and closing div tags correctly until I remove it.

Also, have you designed tagDiv Composer so that inserted HTML fragments appear b/w the <p></p> tags?

Thanks. I understand that browsers are considerably lenient. The question was more to do with tagDiv Composer as it is the thing that seems to be throwing the error. Would the single double quote in combination with inserted HTML fragment cause it to throw a wobbly?

The HTML I had inserted was small and was just copied from one your dynamically created pages – so, it was pure and well formed.

Also, what I cant understand is why it works for a while and then ceases to work after some time? By work here I mean switching in and out of tagDiv Composer.

Hello,

I added the Header manager to make a landing page.
Since I am using this header manager I am getting these kinds of message.
Error at zones: 5(models) : 4(dom). The model does not match the content

I will not use this header manager because make to much trouble.

– How can I delete the header manager function from Tagdiv composer?

(I want to delete it to make sure in the future I don’t use it so long it is not fixed.)
In the future, next theme update could you please make a kind of landing page to the theme without menu?
You could save a lot of time to yourself because lot of people have an issue with it.
Nowadays everybody need a landing page and will try to do it somehow…

Thanks
Br
Adam

I copied to the .htacces file and got 500 error on my webpage.
This was the code
<IfModule mod_substitute.c> SubstituteMaxLineLength 10M </IfModule
What did I make wrong?

Thanks

I suppose copied somehow wrong. Tried again did not get the 500 error but still have the same issue.
Php is 7.3 Memory is 256 MB.
Webhosting should be also ok, the most populat in hungary S11 tarhely.

Any idea?
Thanks

Maybe I am tired… The page was not on visible because now I edit it. I made to visible and now looks ok…
Sorry I am not IT enginer. I do my best in the future.

Br
Adam

Hi,
Now it doesn’t work again!
I am getting the same error! Why? I changed nothing! I opened two days later and this come up again in tagdiv Error at zones: 5(models) : 4(dom).

If I make it as a draft can see the page. If I change the published cannot see the content. Why?
Just one page is not working but this would be my cornerstone site.

Thanks
BR
Adam

Please provide me a solution.

I had this problem after updating from v9.1 to v9.6.1, but we also experienced it after editing a page in 9.1 before updating — we’d edited the About page probably ~100 times, and after a routine edit, the page became broken and would no longer load in TD Composer. TagDiv really needs to include better error messaging for this sort of thing. Why are you showing an error message if no one, including your developers, can say for certain what it means or where the problem is?

The problem we had after updating came from our custom child theme code — We updated our child header.php based on the newest header.php in Newspaper but still had the super helpful “Error at zones: 5 (models) : 1 (dom)” message when opening a brand new Page in TD Composer. Turns out the existence of <div class="tdc-content-wrap"> in our custom footer template was enough to break Composer. Oops. Changing that to <div class="td-container td-footer-bottom-full"> fixed the problem and we could edit Pages again.

The About page problem was even more fun to track down. Long story short, my manager had edited a raw HTML section and not closed off a <div> with a matching </div> and saved the page. TD Composer then started throwing the “Error at zones” error and the page was no longer editable. The fix? Take the offending raw HTML string from the text editor, base64_decode() it, rawurldecode() it, fix the markup, rawurlencode() it, base64_encode() it, paste it back in the text editor, and save. Now the page is editable again. Seems like maybe not the greatest system.

I also have this kind error, all pages crashed without any change. I send emails to contact@tagdiv.com, please take a look. Thank you

My site https://toponlineshopping.com is showing same error, Errors at columns elements: 1(models) : 2(dom). The model does not match the content. Please help me resolve it, I am unable to edit Home Page Menu with Tag Div composer.

I don’t have any clue why it’s happening. It was working fine previously. I not a professional so please rectify the issue at the soonest, I have not updated the latest version which was released few days back.

Error at rows: 8(models) : 7(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)

Home Page at: NoPrep.Com