- NewspapertagDiv Composer – Website Manager
- NewspaperWhen tagDiv Composer is Not Working
- NewspapertagDiv Composer Tutorial
- NewspaperScroll Animation
- NewspaperSingle External Shortcode and External Shortcode
- NewspaperCredit System
- NewspaperBookmark – Save For Later
- NewspaperFlex Block Builder and Flex Loop Builder
- NewspaperModules Builder in Newspaper Theme
- NewspaperIntroduction to CPT and ACF with Newspaper Theme
- NewspaperCreate a frontend submission form
- NewspaperHow to Use the Tabbed Content shortcode
- NewspaperCreate a form contact page
- NewspaperFilters and sorting for taxonomies
- NewspaperUser review system
- NewspaperCustom Fields Support
- NewspaperWooCommerce: Happy “Add to Favorites!”
- NewspaperWoo Brands
- NewspaperModal Popup
- NewspaperShortcodes
Hi,
That is possible.
Please edit the homepage with the composer -> https://prnt.sc/4aGMrsdBYYO1
Then scroll down to the footer and click on this row -> https://prnt.sc/zP_iAizgWhjm
In the CSS tab of the row settings the image can be removed or replaced.
Please try it. Let me know if you have more questions.
Thank you!
Actually that demo uses two headers. They should both appear in the cloud library dashboard, for example -> https://prnt.sc/ai3_p1GizDYY I should have mentioned this before.
There’s an overlay header, used just for the homepage I believe, and a regular header used for the rest of the website.
An overlay header means it is displayed over part of the content, and it’s usually transparent.
You could use just one header if you want or if it’s better for your website. To make the homepage use the global header instead of the special overlay header, while editing the homepage with the composer please set the global template here -> https://prnt.sc/I2g_blW_UFSd
To explain how that works, you can have different headers if you want, per page. A page can either use the global header, or a specific header if it’s set here -> https://prnt.sc/mcE-54JaWjw_
Please let me know in case there are further issues.
Thank you!
Hi,
I will need more details.
Why are you not able to edit the content withy the composer? Are there perhaps errors?
And what fonts are showing different, or where?
If there are errors when editing pages with the composer, I suggest sending us an email at contact@tagdiv.com and providing admin access (user and pass) for the website, so I can check them directly on the website. I’ll also check the font issues, but I’ll need examples. This way it will be faster, let me know.
Thank you!
Hi,
The logo can be changed in the composer -> https://forum.tagdiv.com/add-logo-newspaper/
I see you changed it on mobile -> https://prnt.sc/jHYMc8MuNbP8 It can be changed on desktop as well.
Simply edit for example the homepage with the composer -> https://prnt.sc/6EK8SlCc16LT then click on the logo and set your own logo image -> https://prnt.sc/njJIT90Gx2NZ
In case there is a problem, or if you have more questions, let me know.
Thank you!
Hi tagDiv team,
I want to set my content width to 1200px (modern news-site layout: full-bleed bars, centered 1200px content column) on zzpnieuws.nl, running Newspaper 12.7.6 with a child theme.
In this forum, your staff has described the solution as follows:
– Simion C. (Sep 2025, topic “How to customize the page width”): “So for a page like your homepage, you must edit it with the composer, click on the rows and stretch them to 1200px, it takes very little time.”
– Calin (Aug 2025, topic “banner in my header”): “you can adjust the row width using tagDiv Composer […] the row to be stretched to 1200px instead of the default.”
However, this stretch control does not appear anywhere in my tagDiv Composer:
1. When I select a Row (both on a regular Composer page and in my header Cloud Template), hovering over the left/right edges of the row in the preview shows no drag handles and no resize cursor.
2. The Row settings panel (tabs General / Divider / Layout / Css) contains no stretch or row-width dropdown. The Layout tab only has column layout, alignment, order and “occupy remaining space”. The Css tab only has a manual pixel Width field.
3. Theme Panel → Template Settings has no global site/content width setting either.
My questions:
– Where exactly is the “stretch row to 1200px” control in Newspaper 12.7.6? Is it a drag interaction in the preview, a setting, or something that must be enabled first?
– Is this feature version-, license- or configuration-dependent?
– If it is genuinely unavailable in my setup: what is your recommended, update-safe way to achieve a 1200px content width site-wide (including the default single post and category templates) without breaking the responsive grid and thumbnail calculations?
Setup: Newspaper 12.7.6 (deploy mode: deploy), child theme (originally generated on Newspaper 9), tagDiv Composer + Cloud Library active, header built as a Cloud Template, LiteSpeed Cache, hosting at Cloud86.
Screenshots attached: (1) the Row settings panel showing the four tabs without a width option, (2) a selected row in the preview where no drag handles appear on the edges. See images here: https://postimg.cc/gallery/3xm1fCyimages
Thanks,
Marco — zzpnieuws.nl
My site is https://techchannel.news/. I am not able to edit the content page using Tagdiv Composer. The fonts are showing different to what I have set. How to rectify it.
Thanks
Hello guys,
When I create a new page or post, I use the SureRank Pro to optimze my SEO. It has worked fine on other themes, but since pages and posts are created in TagDiv Composer, the WordPress Editor is full of Tagdiv codes, to provide the expected layout on the frontend.
But this gives me an issue with my SEO plugin, as it cant find relevant keywords and more when trying to optimize the content, due to the code in the editor.
– So how can I optimze the content, using this plugin to ensure the relevant SEO optimizations?
Please see this screenshot:
https://e.pcloud.link/publink/show?code=XZ3kicZufVz5AbanefmuDPmu0YVjkjQLbRk
Cheers!
Hi
Please whenever I activate theme and plugins on my site NaijaVibe.net, loads really slow and my site goes down 504.
tagDiv Cloud Library
tagDiv Composer
tagDiv Opt-In Builder
Please advise what I need to do to resolve this
Thanks
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
Hi,
Thank you for your previous reply.
I made a controlled test on copied homepage pages, not on the live homepage.
Test pages:
– Desktop copy: https://bokanews.me/boka-news-2/
– Mobile copy: https://bokanews.me/boka-news-2-mobile/
WP Super Cache settings:
– Caching On
– Simple mode
– Disable caching for logged-in visitors
– Compress pages
– Cache rebuild
– 304 browser caching
– Mobile device support enabled
– Late init enabled
I also limited WP Super Cache to cache only these two test URLs, so the rest of the website is not cached.
Current test result:
1. The desktop copy is cached successfully:
wp-content/cache/supercache/bokanews.me/boka-news-2/index-https.html
2. The mobile copy is cached successfully as a separate mobile cache file:
wp-content/cache/supercache/bokanews.me/boka-news-2-mobile/index-https-mobile.html
3. When I open the mobile copy directly on a phone:
https://bokanews.me/boka-news-2-mobile/
it displays correctly.
4. But when I open the desktop copy URL on a real mobile phone:
https://bokanews.me/boka-news-2/
it opens the desktop copy and displays incorrectly. It does not switch to the mobile layout/page.
On the real homepage I also tested WP Super Cache with Mobile device support enabled. WP Super Cache created only:
wp-content/cache/supercache/bokanews.me/index-https.html
but it did not create:
wp-content/cache/supercache/bokanews.me/index-https-mobile.html
As a result, mobile visitors received the same cached homepage as desktop visitors, and the mobile homepage displayed incorrectly.
So the issue seems to be with the Newspaper/tagDiv Composer dedicated mobile homepage and WP Super Cache: even with Mobile device support enabled, the real homepage does not reliably generate and serve a separate mobile cache file.
Thank you.
Hi TagDiv Support Team,
I am experiencing a persistent error with TagDiv Composer on my website (hosted on SiteGround). Every time I try to edit or create a page—even a completely fresh, empty page—I get the following error:
“Layout sync error in Content. The editor expects 6 zones but the page is rendering 5.”
Here is what I have already checked and verified to isolate the issue:
PHP Version: The server is running on PHP 8.2.31.
Memory Limits: I have already increased limits in wp-config.php (WP_MEMORY_LIMIT set to 512M).
Plugins & Cache: The issue persists even on blank pages, with no third-party caching/minification conflicts.
System Status: In my Newspaper System Status panel, I noticed a warning regarding mod_substitute being active on Apache (“may cause a timeout error on TD Composer”). I tried tweaking the .htaccess file with SubstituteMaxLineLength and SubstituteEngine Off, but the error remains.
Since it happens even on blank pages, it’s definitely not an unclosed HTML tag in the content. Could you please let me know how to fix this rendering/sync conflict on PHP 8.2 / SiteGround?
Thank you,
Sara
Hi,
If you are using dedicated mobile content, such as the mobile theme plugin or mobile pages built with the composer, then please make sure that this setting is active -> https://prnt.sc/NKWqk2qeG5yd Or else the desktop/mobile version can get mixed up.
If that setting is active then the problem should be solved, assuming the super cache is the only cache used on the website.
Or is the problem different perhaps?
Thank you!
I suggest excluding this script from the optimization if possible:
https://www.thehinh.com/wp-content/plugins/td-composer/legacy/Newspaper/js/tdSmartSidebar.js
If it still doesn’t work, also exclude this script:
https://www.thehinh.com/wp-content/plugins/td-cloud-library/assets/js/js_files_for_front.min.js
Then it should work.
Thank you!
Hello. I am suddenly having trouble editing my Single post templates. I have 3 set up and have edited them with no problem up until this point. Now when I click on “Edit With TagDiv Composer” for any of the 3, it pulls up the default 404 page, and also gives this error: “Layout sync error in Content
The editor expects 6 rows but the page is rendering 3. Usually caused by an unclosed HTML tag in a text block (e.g. <div> without </div>). View page Undo (Ctrl+Z / Ctrl+Shift+Z) to restore.” I haven’t installed any new plugins. I am using Newspaper version 12.7.6 and I am on PHP version 8.2.31. Thanks!
Hi,
Are you also using GoDaddy? Then it’s more than just a coincidence. In both cases from above, the websites were hosted by GoDaddy. The first test I made was to deactivate all the non-theme plugins, the composer functioned much better after doing this, and no freezes.
So I suspected that a plugin was causing the issue, but then it didn’t matter which plugins I activated because the issue started happening again.
My suggestion was to increase the wp memory -> https://www.godaddy.com/en-ph/help/increase-the-wordpress-memory-limit-40246 But if that didn’t help, I’ll investigate it further. Could you please try this as well? Let me know if it solves the problem.
Thank you!
Hi,
No problem, I’ll help with what I can.
1. I’ll need more details about what’s not working exactly.
The account element is for logging in or registering -> https://prnt.sc/CfKMNGhSj7ux Which is required if you offer subscriptions for the website visitors, through the plans page here -> https://product-wiki.com/switching-plans-wizard/
The Subscribe button opens a popup, which contains some text and a leads element -> https://forum.tagdiv.com/leads/
2. That’s the same theme leads element, it’s purpose is to gather emails, which you can then export and use in your newsletter services. It isn’t required to use this leads element. If you are using Mailchimp, you could use the form provided by Mailchimp instead -> https://mailchimp.com/help/add-a-signup-form-to-your-website/ That embed code can be loaded in a Raw HTML element from the composer.
3. The theme already has frontend submission capabilities, we added these features some time ago -> https://tagdiv.com/newspaper-theme-12-update-is-live-explore-the-new-features/
All you have to do is to create a page from where the subscribers can submit content -> https://forum.tagdiv.com/create-frontend-submission-form/ You can also set limits based on the plans the users subscribe to -> https://forum.tagdiv.com/subscriptions/ -> https://prnt.sc/fUyrJR_WCnW9
So if your purpose is to provide subscription plans for the website visitors, and based on the subscription plans the subscribers can submit content on your website, this is possible with the theme features, no extra plugins needed. I’ll help as well. I suggest starting by building the content submission page, the guide I provided should be helpful. Then let me know if you have any questions.
Thank you!
Hi,
While I’m not quite sure what’s happening exactly, I do see a mobile menu and a search inside the content of the homepage, not in the header -> https://prnt.sc/SNrqVyfjCB0K
In the post pages after I refresh the page I also see a mobile menu and search, but still inside the content, not the header, the header is this one -> https://prnt.sc/zhqYSFNarOYn
I believe you added the mobile menu and search inside the content not the header. This can be seen while clicking on the elements in the composer, for example if you click on something you can see the zone it’s in, like this -> https://prnt.sc/BbpWRHinTxxu or like this -> https://prnt.sc/0yslOal_Ohva
And I think you are also using mobile templates perhaps, which complicates things a bit.
I can help fix these things, the fastest way would be send an email at contact@tagdiv.com and provide admin access (user and pass) for the website, so I can check how the header is built and make adjustments where needed.
Thank you!
Hi,
Thank you for your previous guidance.
I’m following up because I already completed the recommended update process, but the issue still persists.
What has already been done:
WordPress was updated.
The Newspaper theme was updated from the old version 7 to the current version 12.
WPBakery / Visual Composer was updated.
The bundled Newspaper/tagDiv plugins were reviewed and updated.
The site files and database were backed up before making changes.
PHP/server compatibility was also reviewed.
After completing those updates, the main issue remains:
The frontend still displays the WPBakery / Visual Composer shortcodes as plain text instead of rendering the page content properly.
For example, the page still shows code like:
[vc_row][vc_column]…[/vc_column][/vc_row]
Also, when activating tagDiv Composer, the website shows an error, so the builder functionality is still not working correctly.
At this point, since the recommended update process has already been completed, could you please help us investigate the remaining issue directly?
It seems that one of these problems may still be happening:
WPBakery shortcodes are not being parsed correctly.
tagDiv Composer is failing during activation.
A required Newspaper/tagDiv component is missing or corrupted.
The old page content from Newspaper 7 / WPBakery is not being processed correctly after the migration.
The page content may need to be repaired, but we need confirmation before rebuilding anything.
For security reasons, I will not post credentials publicly here. I can send fresh temporary WordPress admin and cPanel access privately through email or the proper support channel.
Could you please confirm where I should send the access details so you can review the activation error and shortcode rendering issue?
Thank you.
Best regards,
Adalberto Larios
Hi Simion,
Thanks for the quick reply and for confirming the Standard Pack structure. That clears things up on my end.
I took another pass through the Composer elements and everything is behaving as expected. The three video shortcodes you pointed out match exactly what I’m seeing, so there’s no issue after all.
Appreciate the clarification and the help.
“Hello, I am here to report the same issue. Since updating to WordPress 7.0, the Gutenberg editor is severely bugged, very slow, and the layout/styles are completely broken.
I have done some troubleshooting on my end:
I tested other WP 7.0 sites without the Newspaper theme, and the editor works perfectly.
I disabled all third-party plugins, and the issue persists. It is definitively tied to the theme and the tagDiv Composer.
Checking the browser console, there are conflicts with the new WP 7.0 iframe structure. The console throws errors such as: td-guten-blocks-editor-css-css was added to the iframe incorrectly and fails to load load-scripts.php.
Is there an ETA for a full compatibility patch for WordPress 7.0?”
“Chrome Console”
load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-dom-ready,wp-hooks&ver=7.0:5 JQMIGRATE: Migrate is installed, version 3.4.1
v833ccba57c9e4d2798f2e76cebdd09a11778172276447:1 Failed to load resource: net::ERR_ADDRESS_INVALID
deprecated.min.js?ver=990e85f234fee8f7d446:1 Block with API version 2 or lower is deprecated since version 6.9. See: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/block-migration-for-iframe-editor-compatibility/ Note: The block “mpp/user-profile” is registered with API version 1. This means that the post editor may work as a non-iframe editor. Since all editors are planned to work as iframes in the future, set the apiVersion field to 3 and test the block inside the iframe editor.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 Block with API version 2 or lower is deprecated since version 6.9. See: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/block-migration-for-iframe-editor-compatibility/ Note: The block “mpp/user-profile-enhanced” is registered with API version 1. This means that the post editor may work as a non-iframe editor. Since all editors are planned to work as iframes in the future, set the apiVersion field to 3 and test the block inside the iframe editor.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 wp.compose.withState is deprecated since version 5.8. Please use wp.element.useState instead.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 Block with API version 2 or lower is deprecated since version 6.9. See: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/block-migration-for-iframe-editor-compatibility/ Note: The block “advads/gblock” is registered with API version 2. This means that the post editor may work as a non-iframe editor. Since all editors are planned to work as iframes in the future, set the apiVersion field to 3 and test the block inside the iframe editor.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 36px default size for wp.components.SelectControl is deprecated since version 6.8 and will be removed in version 7.1. Note: Set the __next40pxDefaultSize prop to true to start opting into the new default size, which will become the default in a future version.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 36px default size for wp.components.RangeControl is deprecated since version 6.8 and will be removed in version 7.1. Note: Set the __next40pxDefaultSize prop to true to start opting into the new default size, which will become the default in a future version.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 wp.editor.RichTextToolbarButton is deprecated since version 5.3 and will be removed in version 6.2. Please use wp.blockEditor.RichTextToolbarButton instead.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
load-scripts.php:1 Failed to load resource: the server responded with a status of 404 ()
Hi,
That looks correct and it is what the standard pack plugin should contain. The modules, shortcodes and other folders and files are inside that Newspaper folder from the plugin -> https://prnt.sc/bA4Jqmbdkpp4 I see no problem with what you described.
But I’m not quite sure what you are trying to do exactly. There are 3 video shortcodes in the composer -> https://prnt.sc/rN85UZYXaPJG Is there a problem with them? Please let me know how I can help exactly.
Thank you!
Hi,
That isn’t a known issue. But I do have a pretty good idea about what’s happening.
Does the page maybe look like this when it happens? -> https://prnt.sc/hyCp9Ek6hrrs
That’s the mobile theme version, meaning the mobile theme plugin is active on the website. The mobile theme doesn’t load composer or cloud library resources and classes.
Normally the mobile theme is displayed on mobile. But sometimes due to the caching used on the website or provided by the hosting, it can get displayed on desktop as well. It usually depends on how the homepage is visited after the cache is cleared. If someone visits it with a mobile, then the mobile version is cached and server to everyone. By updating the page in the composer you are basically clearing the cache, and if you check with a desktop next then the problem is solved. Until by coincidence it will happen again.
I see you use litespeed, if this is the only caching used on the website, I suggest activating this option -> https://prnt.sc/gSi7feVctFPh If it’s already active and it’s still happening, then it means there is another cache active.
Or, you could deactivate the mobile theme plugin. It’s an optional plugin.
I believe that this is what’s happening, because it fits the description of the problem. I could be wrong however.
Let me know.
Thank you!
Hi,
I’m having an issue with the tagDiv Standard Pack plugin on Newspaper 12.7.6.
When I install it from the Newspaper → Plugins panel, the installation completes successfully, but the plugin folder only contains:
common/
Newspaper/
td-standard-pack.php
tdsp_version_check.php
There are no module folders such as:
modules/
shortcodes/
templates/
assets/
includes/
As a result, TagDiv Composer only shows the legacy video blocks.
I also downloaded the ZIP directly from the URL shown during installation, and it contains the same minimal stub files.
My Newspaper license is active and assigned to adultswimcentral.com, and all system status checks are OK.
Could you please push the full Standard Pack module bundle to my domain or provide a direct download link?
Thanks!
Hello,
I run the Newspaper theme (version 12.7.6, registered) with tagDiv Composer on a WordPress site hosted at WP Engine. The homepage intermittently breaks: the hero/feature grid renders as gray bands with no background images and the layout collapses. It happens every several days, with no edit or publish that I can tie to it.
I have diagnosed this fairly precisely and want to share the evidence, because it points to the Composer template failing to compose rather than a caching or browser issue.
WHAT THE BROKEN VS HEALTHY HTML SHOWS
I captured the HTML of the same homepage URL (page ID 370) in both states.
Broken state (~59 KB):
body class is MISSING: wp-theme-Newspaper, global-block-template-1, tdb-template, td-full-layout
4 td_block instances
6 style blocks, about 9.8 KB of inline CSS
0 background-image rules (which is why no hero imagery paints)
Healthy state (~899 KB):
body class INCLUDES: wp-theme-Newspaper, global-block-template-1, tdb-template, td-full-layout
324 td_block instances
41 style blocks, about 53 KB of inline CSS
about 200 background-image rules
So in the broken state the tagDiv block-builder template for the page is not composing at all. The tdb-template / global-block-template-1 output and inline CSS never generate.
WHAT FIXES IT AND WHAT DOES NOT
Purging the host cache does NOT fix it. The broken render is served even on a forced cache miss and on hard refresh, so it is not stale cache.
Re-saving the homepage in tagDiv Composer (Save, with the green Header/Footer/Content Successfully Saved confirmations) DOES fix it immediately, every time. This is now reproduced twice.
So a fresh Composer composition produces the correct page, and something later causes the page to revert to the un-composed render.
PATTERN
It stays healthy for several days, then suddenly reverts to the broken render.
One stable stretch lasted about 9 days before recurring.
A re-save fixes it for another multi-day stretch.
ONE POSSIBLY RELATED DETAIL
When the broken version was being served, the host cache had bucketed a desktop request into the mobile/iphone cache group. I mention it only in case Composer mobile/desktop template variant handling is relevant to why an incomplete render gets produced.
QUESTIONS
Is there a known issue where the Composer block-builder template fails to compose on a page regeneration, producing output without the tdb-template / global-block-template-1 body classes and without the inline CSS?
Could a periodic Composer cloud-library sync, a theme/Composer background process, or a license re-check trigger a re-render that lands in this un-composed state?
Is there a setting or maintenance step that forces the template to always fully compose, so I do not have to manually re-save in Composer every few days?
Is there a current recommended compatible pairing of Newspaper theme version and tagDiv Composer plugin version I should confirm I am on?
I can provide both full HTML captures (healthy and broken) on request.
Site: https://alstonhomes.com
Hello,
I run the Newspaper theme (version 12.7.6, registered) with tagDiv Composer on a WordPress site hosted at WP Engine. The homepage intermittently breaks: the hero/feature grid renders as gray bands with no background images and the layout collapses. It happens every several days, with no edit or publish that I can tie to it.
I have diagnosed this fairly precisely and want to share the evidence, because it points to the Composer template failing to compose rather than a caching or browser issue.
WHAT THE BROKEN VS HEALTHY HTML SHOWS
I captured the HTML of the same homepage URL (page ID 370) in both states.
Broken state (~59 KB):
body class is MISSING: wp-theme-Newspaper, global-block-template-1, tdb-template, td-full-layout
4 td_block instances
6 style blocks, about 9.8 KB of inline CSS
0 background-image rules (which is why no hero imagery paints)
Healthy state (~899 KB):
body class INCLUDES: wp-theme-Newspaper, global-block-template-1, tdb-template, td-full-layout
324 td_block instances
41 style blocks, about 53 KB of inline CSS
about 200 background-image rules
So in the broken state the tagDiv block-builder template for the page is not composing at all. The tdb-template / global-block-template-1 output and inline CSS never generate.
WHAT FIXES IT AND WHAT DOES NOT
Purging the host cache does NOT fix it. The broken render is served even on a forced cache miss and on hard refresh, so it is not stale cache.
Re-saving the homepage in tagDiv Composer (Save, with the green Header/Footer/Content Successfully Saved confirmations) DOES fix it immediately, every time. This is now reproduced twice.
So a fresh Composer composition produces the correct page, and something later causes the page to revert to the un-composed render.
PATTERN
It stays healthy for several days, then suddenly reverts to the broken render.
One stable stretch lasted about 9 days before recurring.
A re-save fixes it for another multi-day stretch.
ONE POSSIBLY RELATED DETAIL
When the broken version was being served, the host cache had bucketed a desktop request into the mobile/iphone cache group. I mention it only in case Composer mobile/desktop template variant handling is relevant to why an incomplete render gets produced.
QUESTIONS
Is there a known issue where the Composer block-builder template fails to compose on a page regeneration, producing output without the tdb-template / global-block-template-1 body classes and without the inline CSS?
Could a periodic Composer cloud-library sync, a theme/Composer background process, or a license re-check trigger a re-render that lands in this un-composed state?
Is there a setting or maintenance step that forces the template to always fully compose, so I do not have to manually re-save in Composer every few days?
Is there a current recommended compatible pairing of Newspaper theme version and tagDiv Composer plugin version I should confirm I am on?
I can provide both full HTML captures (healthy and broken) on request.
