Search Results for 'td composer'

Hello tagDiv Support Team,

I need to restrict access to Cloud Templates for users with the Editor role on my Newspaper theme website. Currently, editors can still see and edit Cloud Templates in the backend, which I need to prevent.

What I’ve tried:
– Installed “User Role Editor” plugin and adjusted capabilities
– Added custom code to functions.php to remove menu items and capabilities
– None of these solutions have successfully hidden or blocked access to Cloud Templates

What I need:
– Only Administrators should be able to access, view, and edit Cloud Templates
– Editors should be completely blocked from accessing Cloud Templates (both in the admin menu and via direct URL access)
– Editors should still be able to create and edit regular posts and pages

Questions:
1. Is there a built-in setting in Newspaper theme to restrict Cloud Templates access by user role?
2. What is the correct capability or hook to use to prevent editors from accessing the Cloud Templates custom post type (tdb_templates)?
3. Can you provide the recommended code solution to implement this restriction?

Theme Details:
– Theme: Newspaper
– Plugins: tagDiv Composer, tagDiv Cloud Library (both active)
– WordPress Version: 6.8.3
– Theme Version: 12.7.3

Thank you for your assistance!

Best regards

Hi TagDiv, my site didgeproject.com is experiencing some theme issues. Here’s a report found by wordfence. Can you help? https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/td-composer/tagdiv-composer-541-unauthenticated-stored-cross-site-scripting

thanks in advance for your help

Hi, since the very last update last week, the search buttons are no longer working. I can do a live search and items do show up but when I hit the button, the search results page wont open and a fatal error page will pop up instead. I have enabled debug and this is what I get:

Fatal error: Uncaught TypeError: Cannot access offset of type array on string in /var/www/html/news/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php:1196 Stack trace: #0 /var/www/html/news/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php(340): td_util::get_template_id() #1 /var/www/html/news/wp-content/plugins/td-composer/legacy/common/wp_booster/td_wp_booster_functions.php(513): td_util::check_header() #2 /var/www/html/news/wp-includes/class-wp-hook.php(324): td_load_css_fonts() #3 /var/www/html/news/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #4 /var/www/html/news/wp-includes/plugin.php(517): WP_Hook->do_action() #5 /var/www/html/news/wp-includes/script-loader.php(2299): do_action() #6 /var/www/html/news/wp-includes/class-wp-hook.php(324): wp_enqueue_scripts() #7 /var/www/html/news/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #8 /var/www/html/news/wp-includes/plugin.php(517): WP_Hook->do_action() #9 /var/www/html/news/wp-includes/general-template.php(3192): do_action() #10 /var/www/html/news/wp-content/plugins/td-composer/legacy/Newspaper/header.php(8): wp_head() #11 /var/www/html/news/wp-content/plugins/td-composer/td-composer.php(254): require_once(‘…’) #12 /var/www/html/news/wp-includes/class-wp-hook.php(324): {closure:/var/www/html/news/wp-content/plugins/td-composer/td-composer.php:249}() #13 /var/www/html/news/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #14 /var/www/html/news/wp-includes/plugin.php(517): WP_Hook->do_action() #15 /var/www/html/news/wp-content/themes/Newspaper/header.php(2): do_action() #16 /var/www/html/news/wp-includes/template.php(810): require_once(‘…’) #17 /var/www/html/news/wp-includes/template.php(745): load_template() #18 /var/www/html/news/wp-includes/general-template.php(48): locate_template() #19 /var/www/html/news/wp-content/plugins/td-cloud-library/wp_templates/tdb_view_search.php(8): get_header() #20 /var/www/html/news/wp-includes/template-loader.php(106): include(‘…’) #21 /var/www/html/news/wp-blog-header.php(19): require_once(‘…’) #22 /var/www/html/news/index.php(17): require(‘…’) #23 {main} thrown in /var/www/html/news/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php on line 1196

I have tried to use another cloud template for the search page, I have tried editing the existing one and saving… but nothing helps same error all the time.

Any clues on what is going on?

Thanks in advance,
Jose

After the last update, I noticed that some features on my website are not working, such as tagDiv Composer blocks, page loading, post templates have disappeared and do not open. I ran some tests by disabling the plugins and noticed that the tagDiv Composer plugin itself is causing this. I need help, as it is affecting the functioning of my website and part of the content cannot be accessed due to the following error:

wp_booster error:
td_api_base::mark_used_on_page : a component with the ID: single_template_2 is not set.
/home1/matine35/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Blocks also do not appear on the home page and only display the code:
[td_block_16 m16_tl=”20″ category_id=”7772″ limit=”6″]
Other blocks and grids simply disappeared.

Here are two links to view the problems:
Home: https://matinecinetv.com.br/

Content: https://matinecinetv.com.br/2022/08/16/nosso-trabalho-e-unir-entretenimento-com-pertinencia-diz-raphael-montes-sobre-2o-temporada-de-bom-dia-veronica/

greenwoodcalendar.com
When I deactivate the built-in social counter, my site returns. Is there a way I can use the social counter with my new Newspaper 12 theme. Here is the code I received:

Uncaught Error: number_format(): Argument #1 ($num) must be of type int|float, string given
in /home/greenwx6/public_html/wp-content/plugins/td-social-counter/shortcode/td_block_social_counter.php on line 1176

Call stack:

number_format()
wp-content/plugins/td-social-counter/shortcode/td_block_social_counter.php:1176
td_block_social_counter::render()
wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php:27
td_global_blocks::proxy_function()
wp-includes/shortcodes.php:434
do_shortcode_tag()
preg_replace_callback()
wp-includes/shortcodes.php:273
do_shortcode()
wp-content/plugins/td-composer/includes/tdc_composer_block.php:222
tdc_composer_block::do_shortcode()
wp-content/plugins/td-composer/includes/shortcodes/vc_column.php:440
vc_column::render()
wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php:27
td_global_blocks::proxy_function()
wp-includes/shortcodes.php:434
do_shortcode_tag()
preg_replace_callback()
wp-includes/shortcodes.php:273
do_shortcode()
wp-content/plugins/td-composer/includes/tdc_composer_block.php:222
tdc_composer_block::do_shortcode()
wp-content/plugins/td-composer/includes/shortcodes/vc_row.php:1204
vc_row::render()
wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php:27
td_global_blocks::proxy_function()
wp-includes/shortcodes.php:434
do_shortcode_tag()
preg_replace_callback()
wp-includes/shortcodes.php:273
do_shortcode()
wp-content/plugins/td-composer/includes/tdc_composer_block.php:222
tdc_composer_block::do_shortcode()
wp-content/plugins/td-composer/includes/shortcodes/tdc_zone.php:806
tdc_zone::render()
wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php:27
td_global_blocks::proxy_function()
wp-includes/shortcodes.php:434
do_shortcode_tag()
preg_replace_callback()
wp-includes/shortcodes.php:273
do_shortcode()
wp-includes/class-wp-hook.php:324
WP_Hook::apply_filters()
wp-includes/plugin.php:205
apply_filters()
wp-includes/post-template.php:256
the_content()
wp-content/plugins/td-composer/legacy/Newspaper/page.php:51
include(‘/home/greenwx6/publi…y/Newspaper/page.php’)
wp-includes/template-loader.php:106
require_once(‘/home/greenwx6/publi…/template-loader.php’)
wp-blog-header.php:19
require(‘/home/greenwx6/public_html/wp-blog-header.php’)
index.php:17

Query Monitor

Hi TagDiv Team,

Like some other users, I’m consistently getting the following error when editing new pages or the homepage (but not posts): Error at zones: 6(models): 0(dom) “The model does not match the content. Current state has involved an issue.”

This even happens immediately after I download one of your pre-built templates—even before adding any shortcodes.

What I discovered:

After some testing, I found that if I use the “Post Type Switcher” plugin to change the page type (in the Classic Editor) from Page → Cloud Template, the error in Composer disappears completely!

Once I do that:

I can edit the page in Composer without any errors.

The layout works as expected.

However:

The page is then removed from the Cloud Template list, since it’s technically no longer a “Page” it is a Cloud Template type.

It only displays properly if I access it through a URL like
https://example.com/tdb_templates/news
If I try to access it normally at https://example.com/news, I either get a blank page or a critical error.

My theory

It seems that posts don’t trigger this error because the Theme Panel → Templates section includes a redirect or link definition for posts and single templates. That likely ensures TagDiv Composer initializes the correct “zone” mapping.

For pages and the homepage, there’s no equivalent setting in the Theme Panel, so Composer may be loading the wrong internal model—hence the zone mismatch.

The problem

At the moment, I can’t create or edit any new pages or homepage layouts without this error.
Only posts work normally.

Possible solution idea

If my guess is right, perhaps the Composer needs a way to assign a Cloud Template mapping (like the Post templates) for Pages and Homepage in the Theme Panel. That might resolve the zone mismatch entirely.

Do you have any other workaround or insight on this?
It’s currently blocking all new page and homepage creation.

Thanks for your help!

Hi, I have a problem on the results page after using the “search” function.
Both the plugin and the template are up to date, and this behavior is new.
From the homepage: click on the magnifying glass “search” icon, and you can try typing something like “Bhutan” and pressing Enter.
When the search results page loads, these two error lines appear:

Warning: Illegal offset type in /home/mhd-01/www.trolleygirl.it/htdocs/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php on line 1196

Warning: Illegal offset type in /home/mhd-01/www.trolleygirl.it/htdocs/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php on line 1196

I found the corresponding file, but I don’t know what I need to modify.

I emailed the Sql support, but they told me that the errors clearly refer to the **td-composer** plugin. We don’t know whether this might be due to an incompatibility with other plugins, with the active PHP version, or with the theme you are using in WordPress.

In any case, the **td-composer** plugin is not working properly.

Could you please help me?

Thank you,
Stefania

Issue Summary
A fatal TypeError occurs in TagDiv Composer’s td_util.php file when performing search queries on sites using the Newspaper theme. The error prevents pages from loading and disrupts user experience.

Error Details
Perform a search query (e.g., /?s=term).
Error triggers during template loading.

Root Cause
In the get_template_id method, the code assumes td_cpt option is always an array:


$td_cpt = td_util::get_option('td_cpt');
if ( !empty( $td_cpt[$post_type]['search_tpl'] ) ) {
// ...
}

However, get_option may return a string in some cases, causing the TypeError when using array syntax.

Suggested Fix
Add an array type check before access:


$td_cpt = td_util::get_option('td_cpt');
if ( is_array($td_cpt) && !empty( $td_cpt[$post_type]['search_tpl'] ) ) {
$cpt_search_template_id = $td_cpt[$post_type]['search_tpl'];
}

This affects sites with CPT searches, leading to broken search functionality. We recommend implementing this fix in future plugin updates to ensure compatibility and stability.

The “edit with tagdiv composer” is not working: The side menu to enable editing doesnt load but gives 404 error page. Have cleared cache, have tried to uninstal theme and reinstal it. Have also tried o uninstal tagdiv composer plugin and reinstal it and activate it but still geting this error message

Please help. Been on this for days now.

Thank you.