Search Results for 'composer'

We have a support contract and are seeing two issues we’d like your help resolving.

I can send further sensitive or confidential information to your contact email referencing this specific ticket.

— Issue 1: Layout sync error blocking front-page edits —

When attempting to edit the front page in tagDiv Composer, the editor displays:

“Layout sync error in Header, row 2. The editor expects 1 element but the page is rendering 0. 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.”
The error points to the header ad position in Header row 2, which renders as an “EMPTY INNER COLUMN” with a red outline in the editor.

The Undo shortcut (Ctrl+Z / Ctrl+Shift+Z) does not fix the problem.

This has been an ongoing issue for multiple months and is preventing front-page edits.

— Issue 2: Sidebar preview missing in post editor —

After updating our various web sites to 12.7.6, the post editor no longer shows the sidebar reservation area — the visual cue that previously showed the authors the actual rendered width of the post content with the sidebar reservation accounted for.

This affects both the production site and the dev site. Other sites we host using prior versions of the theme are not affected and continue to show the sidebar preview correctly.

Thanks — looking forward to getting this resolved.

Hi, can someone please guide how to create a FAQ drop-down box that can be connected to Yoast Schema at the end of the article? The authors can simply put those in while putting in the article on WP.

Also, any way to create a summary or quick answer box at the beginning of the article on the article page in a newspaper? I tried finding a function in TD Composer, but could not find it.

If not, then any third-party plugins you recommend.

These things have become increasingly important.
thanks in advance.

When I try to edit my website’s header page not loading. Pls help.

https://berwarnews.com/wp-content/uploads/2026/05/01.png
https://berwarnews.com/wp-content/uploads/2026/05/02.png

Hello tagDiv team,
We would like to report a recurring fatal error affecting a WordPress.com-hosted site using Newspaper and tagDiv Composer.

This issue seems to occur only when the site visibility is set to private on WordPress.com. We use the same Newspaper/tagDiv stack on other sites, but this is the only one where the WordPress.com private-site access flow is involved.

The fatal error is:
PHP Fatal error: Uncaught Error: Class “td_res_context” not found

The error is triggered from:
wp-content/plugins/td-composer/legacy/common/wp_booster/td_js_generator.php

From the stack trace, the issue happens during the wp_footer hook. In this specific WordPress.com private-site flow, WordPress.com serves an access-denied/private-site template and calls wp_footer(). At that point, tagDiv Composer runs its footer callback and tries to use the td_res_context class, but that class has not been loaded yet.

The class appears to be defined in:
wp-content/plugins/td-composer/legacy/common/wp_booster/td_css_res_compiler.php

So it looks like the Composer callback in td_js_generator.php assumes that td_res_context is already available when wp_footer runs. That assumption seems to fail in this WordPress.com private-site access-denied context.

Environment:
– Hosting: WordPress.com
– Site visibility: Private
– WordPress: 6.9.4
– PHP: 8.4.21
– Theme: Newspaper 12.7.6
– tagDiv Composer: 5.4.5
– tagDiv Cloud Library: 3.9.5
– tagDiv Standard Pack: 2.8, built on 05.05.2026 9:08

We kept this issue as a low-priority investigation for some time because, although the fatal error was recurring in the PHP logs, the site appeared to work correctly in normal usage. Both the front end and the back office were functioning as expected, and we did not observe any visible impact for regular users or administrators.
However, the error became very frequent in the PHP logs, so we investigated further.

As a temporary workaround, we added a defensive snippet that runs before the tagDiv Composer footer callback and loads the file containing td_res_context only if the class is not already available. After applying this workaround, the recurring fatal errors stopped.

This suggests that the issue could be fixed in the plugin by either:
1. Ensuring the required dependency is loaded before td_res_context is used; or
2. Adding a guard clause before calling td_res_context inside the wp_footer callback.

Could you please review this scenario and consider adding a compatibility fix for WordPress.com private sites or for cases where wp_footer is called outside the normal theme-rendering flow?

Thank you.
Best regards.

TD Composer is currently being flagged with my web host as containing security vulnerabilities. Particularly with version 5.4.5 is that the most current version as I am not seeing any version numbers at this time.

Hi
I have a site (now cloned to a staging server) which is currently using theme: NEWSMAG 5. But the site owner wants to use NEWSPAPER 12 theme to match his other sites.

So he has bought another licence and I am the developer working on it. but when I upload and try to activate it, it crashes the site with a fatal error.

So I have gone through the plugins activating.deactivating them, and it is being caused by some conflict with the TagDiv composer plugin. The NEWSPAPER 12 theme will activate when that plugin is not active

But obviously this is a problem, as the content is all configured by TagDiv composer, and NEWSPAPER 12 is supposed to support the TagDiv page builder.

All plugins are up-to-date, and the server has over 80GB free space – so it’s not a resources issue

Any suggestions?

Hello tagDiv Support,

We are currently migrating a large regional news platform to Cloud Templates and are running into a query/filtering limitation that we are unsure how to solve correctly within Newspaper / tagDiv Composer.

Our setup is somewhat unusual, so I will explain it carefully.

Current Site Structure

We operate a Dutch regional news platform with approximately 57 regional categories.

Examples:

Regio Gouda
Regio Rotterdam
Regio Drechtsteden
etc.

Articles are intentionally assigned to multiple categories simultaneously.

Example article structure:

Regio Gouda
Zuid-Holland Province Category
Sometimes Binnenland (National)
Sometimes another regional umbrella category

This multi-category structure is required editorially and for SEO/distribution purposes.

What We Are Trying To Achieve

We want to replace static regional landing pages with dynamic category archive pages using Cloud Templates.

Example:

Instead of:
https://regioonline.nl/regio-gouda/

We want to use:
https://regioonline.nl/category/regio-gouda/

with a Cloud Template assigned to the category.

The goal is:

show posts from the current region
ALSO show related province-level content
BUT still prioritize/display correct regional content
WITHOUT manually configuring 57 static pages
The Problem

Inside Flex Blocks / Big Grid Flex blocks, the queries behave differently between:

Static pages using manual “Multiple Terms Filter”
Dynamic category archive pages using Cloud Templates

Example:

On the static page:

the block correctly shows a Zuid-Holland province article

But on the Cloud Template category archive:

the same block instead shows another regional article

Even though both posts contain overlapping categories.

Important Technical Detail

We discovered that:

category_ids behaves differently from normal category archives
category__in and internal TagDiv query handling appear to override or merge unexpectedly
multi-category posts are handled differently inside Cloud Templates versus static pages

While inspecting the theme code, we also noticed references to _current_cat handling internally in td_block.php, but we could not find official documentation about whether this value is actually supported for Flex/Grid block filtering in Cloud Templates.

We also tested custom filters through:

td_shortcode_to_args
td_data_source_blocks_query_args

inside the child theme.

However, this caused unstable or inconsistent behavior, especially with:

Big Grid Flex blocks
Flex blocks
mixed category/province logic

We reverted these changes because we do not want to maintain custom query modifications that could break after theme updates.

Our Main Question

Is there an officially supported way in Newspaper / tagDiv Composer to achieve the following:

For a category Cloud Template:

dynamically use the CURRENT category
include additional province categories
optionally exclude national categories
while preserving predictable ordering and matching behavior in Flex/Grid blocks

WITHOUT custom core edits.

Example desired logic for “Regio Gouda”:

Include:

current category (Regio Gouda)
province category (Zuid-Holland)
national regional pool category

Exclude:

Binnenland

And this should work dynamically for all regional categories.

Additional Question

Does Newspaper internally prioritize:

category_ids
category__in
queried object
tax_query
current archive context

in a specific order inside Flex Blocks / Big Grid Flex blocks?

Because it appears that archive context may override manually configured multiple term filters.

Final Question

Would you recommend:

using Cloud Templates for this setup
OR
keeping static regional landing pages

given this multi-category architecture?

We would really appreciate technical guidance or best practices from your side before rebuilding all regional pages again.

Thank you very much.