Errors at columns: 1(models) : 0(dom). The model does not match the content Curr

Hello,

Website is https://capsulenz.com/

I have updted to 10.4 and the Single Post Cloud Template is showing this error when I try to edit the template:

Errors at 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 have read this https://forum.tagdiv.com/tagdiv-composer-not-working/
and understand it’s an HTML error.

What I don’t know is how to locate where the problem code is because I can’t use the tagdiv composer to look at the template.

Can you please assist me to troubleshoot this? How can I fix this problem so I can edit the template again?

Thank you.

Thank you. I have completed those steps but still see the same error.

No cache plugin installed. WP and all plugins up to date.

What are the next steps to resolve please?

That brings me back to my original question. How do I check/remove the problem HTML?

I think I might have found it but I can’t get access to it because the error makes the elements unclickable.

Do I have to recreate the template? (without the HTML?)

Hello!
I have same issues,.. any fix yet?
I did all bellow steps
1. disable TagDiv Composer
2. uninstall(delete) TagDiv Composer
3. clear cache (if cache plugin exists)
4. install TagDiv Composer
5. activate TagDiv Composer
6. clear cache (if cache plugin exists)

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

Im abble to download new “Header templates” but cant edit with “TagDiv Composer”

Hello, I’ve same issues, and followed all steps, but not fixed yet

I’m experiencing the problem Error at zones: 6(models) : 7(dom) that I’m convinced began after the most recent update. I use the Newspaper theme on several websites, but this issue has only appeared on one of them. The error is present on every page, and persists even when I create a new page to test it.

I’ve spent considerable time searching for a solution and have tried deactivating and testing each plugin to identify the source of the problem, but to no avail. I have also attempted uninstalling and reinstalling the composer, a step that resolved the issue in the past, but it hasn’t been effective this time.

I reviewed the WP logs and couldn’t find any related entries that could potentially be causing this problem. I distinctly remember editing my site not too long ago without encountering any issues, which leads me to believe that something in the latest Newspaper update might be the culprit.

In my search for a solution, I came across several threads at the end suggesting to contact support with admin credentials, but there hasn’t been any update on that front. If anyone has encountered this issue and found a resolution, could you please share your insights? Your assistance would be greatly appreciated as I am eager to resolve this persisting problem.

• This reply was modified 2 years by elvisfrog.

I want to share an update on resolving an issue I encountered, hoping it can assist others who might face a similar challenge and spend a considerable amount of time troubleshooting it. Although it is essential to first consider the recommended steps provided by the TagDiv support team, my solution might be an additional resource.

I discovered that a modal popup embedded in my footer was the culprit. I suspect that something went awry during a recent upgrade. This embed consisted of custom code, replicated from a text on a composer page. I had a Gravity Forms embedded on this page for a newsletter signup. Initially, I created the modal popup page using the Gravity Form shortcode and copied the composer code. However, it is crucial to note that I copied this code via the “edit” option, not “edit in composer,” into the custom code box for my modal popup in the footer.

For reasons I couldn’t initially understand, this was generating an error: Error at zones: 6(models) : 7(dom). I resolved the issue by manually entering the footer and deleting the text in the custom-code=”” field, then saving the file. This allowed me to access the footer via composer and make the necessary adjustments to the pages.

Interestingly, I pinpointed the error to the footer through a process of elimination. While in composer, I first changed the header to “no header” but still encountered the same error. It was only when I selected “no footer” that the error disappeared. This revelation led me to the conclusion that the error originated in the footer.

I believe the modal pop-up custom code triggered this issue. I’m sharing this experience in the hope that it might streamline the troubleshooting process for others facing similar challenges.

Lastly, I want to express my gratitude to the TagDiv staff. Their diligent support in navigating the intricacies of a complex yet powerful theme like Newspaper, which I consider to be one of the best available, is immensely appreciated.

I have the same issue.
I even deleted the WordPress application, I started with fresh and clean WP applciation, no plugin, no post, zero, I isntalled the Theme, the plugin with the theme and the demo site.
Same problem, no possibility to go ahead and to implement the site.
Waiting fro support from the team, let’s see.

Hello, morning,

When I try to update or make some modification, it does not allow me to do so, that is,

it does not take the changes.

I can’t edit through TagDivComposer Does not save changes.

I sent the credentials days ago

Thank you!

• This reply was modified 1 year by NAIVY BOLIVAR.

I have the same issue. I was sent email to contact@tagdiv.com. waiting for your feedback.

Thanks