Confirmed TagDiv Composer serialization drift (tdc_content out of sync with post

Hi there!

Confirmed TagDiv Composer serialization drift (tdc_content out of sync with post_content) – supported recovery procedure?

We have isolated what appears to be a TagDiv Composer synchronization problem on our homepage and would like to know the supported recovery procedure.

We are not asking for general troubleshooting. We believe we have already identified the root cause and would like confirmation of the proper recovery method.

Environment
Newspaper Theme
TagDiv Composer
WordPress
Staging site
Homepage

The frontend renders correctly.

The homepage content is intact.

Only TagDiv Composer cannot load the page correctly.

Composer displays:

Layout sync error in Content, row 1. The editor expects 1 element but the page is rendering 5.

Investigation

We performed a read-only investigation and found:

post_id: 338024

tdc_dirty_content

1

tdc_content

[tdc_zone type=”tdc_content”][vc_row][vc_column][/vc_column][/vc_row][/tdc_zone]

The stored post_content contains the complete homepage layout with five vc_row_inner sections, while tdc_content contains only the minimal empty scaffold.

The frontend renders correctly because post_content is intact.

Composer appears to be comparing:

the serialized editor model (tdc_content)
against the current post_content

and reporting:

“expects 1 element but the page is rendering 5.”

Our question

Is this a known TagDiv Composer synchronization state?

If so, what is the supported method to regenerate or synchronize tdc_content from the existing post_content?

We are specifically looking for the supported recovery procedure.

We are not looking for workarounds such as rebuilding the homepage manually unless that is officially required.

Thanks your for help with this. Please let me know if any other information is required.

https://okobserverorg.staging.wpmudev.host/wp-admin
contact@wpmudev.org
(password sent via email to: contact@wpmudev.org)

Bob

• This topic was modified 1 month by bob@mrrogersweborhood.com. Reason: Add'l info

Hey Simion.

I just resent the credentials to contact@tagdiv.com.

Thanks again.

Bob