Search Results for 'td composer'

Hi. According to patchstack, there is a vulnerability for tagDiv Composer Plugin <= 5.4.1 (This vulnerability is moderately dangerous and expected to become exploited. CVSS severity 7.1).

I suppose your team is already aware of this security vulnerability.
I am using the last version 5.4.3.3 of Newsmag theme.

When will the updated version be released?

Thank you.
George

Hello TagDiv Support,

I am using the Newspaper theme (latest version) on my WordPress site, and am experiencing critical issues with missing frontend JavaScript files and related mobile performance problems.

Description of the Problem:

On my live site, the following critical theme JS files are returning 404 errors:

/wp-content/themes/Newspaper/js/tagdiv_theme.min.js

/wp-content/themes/Newspaper/js/tdb-site.js

This results in:

Broken frontend features (menus, blocks, theme interactivity).

Console errors such as “wp is not defined” and failures for any code dependent on the wp JS object.

Failed scripts when trying to use or customize TagDiv Composer, blocks, or advanced layouts.

File/Folder Structure Verified:

My Newspaper theme is installed at: /wp-content/themes/Newspaper/

The only theme folders present are: css, images, includes, translation, woocommerce (see attached screenshot).

No top-level /js/ directory is present in the parent Newspaper theme folder.

I checked within /includes/, where there’s a separate js folder, but it contains only backend/admin scripts, not the required frontend ones.

I have unzipped the original theme package from your download. There is still no /js/ directory at the theme root with the two required JS files.

Steps Taken:

Searched and extracted all folders in the downloaded Newspaper theme package, but could not find tagdiv_theme.min.js or tdb-site.js anywhere.

Cleared all WordPress, server, and browser caches, rechecked file system and browser console—issue persists.

Verified the problem recurs with a freshly installed, untouched Newspaper theme (not a child theme or plugin conflict).

Impact:

Site is not functioning properly for end users due to missing JavaScript.

Mobile Lighthouse audits show increased load times (LCP 5.6s+), slow visual completion, and warnings about render-blocking JS/CSS, many of which are worsened by missing or broken theme scripts.

Fundamental site features and performance are degraded on mobile and desktop.

Expected Resolution:

Please provide the correct /js/ directory and the latest versions of:

tagdiv_theme.min.js

tdb-site.js
so I can properly restore these to /wp-content/themes/Newspaper/js/.

If the theme package download I received is incomplete or missing files, please advise and provide a new download link or updated theme zip.

Advise if there may be a packaging, deployment, or installation issue on your end that affects the inclusion of essential JS files.

Optional/Additionally:

Please share a recommended method to ensure all critical JS assets are retained through future theme updates and can be verified after installation.

Any additional suggestions for resolving mobile loading/Lighthouse issues when all scripts are present and loading correctly.

Thank you for your help. Screenshots of my folder structure and file audits are attached for your reference.

Best regards,
Ameet
Newspatron.com

Console error screenshot
https://drive.google.com/file/d/1WisGWNru277WMt6d0twc0EvxeIVW0XkF/view?usp=sharing

Lighthouse screenshot
https://drive.google.com/file/d/1iAFtFb6z26XJdPg4myLTj0KlIoa4qnuS/view?usp=sharing

Hi,
suddendly in every article page I just see this and all the contents are hidden!
Example: https://www.trolleygirl.it/visitare-il-louvre-in-poche-ore/

wp_booster error:
td_api_base::mark_used_on_page : a component with the ID: single_template_6 is not set.
/home/mhd-01/www.trolleygirl.it/htdocs/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php

Please help!

Hi Guys,

Any idea when 5.4.2 will be available?

https://patchstack.com/database/wordpress/plugin/td-composer/vulnerability/wordpress-tagdiv-composer-plugin-5-4-1-cross-site-scripting-xss-vulnerability?_a_id=350

When I go to the search page gives me this error

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

Hello! When I enter a search term, the live ajax is working but if I press enter it returns a fatal error.
How can I reset this function on the theme?

The site is nordsip.com and here is the error returned by Query Monitor:

Uncaught Error: Illegal offset type
in /home/nordsipc/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php on line 1196

Call stack:

td_util::get_template_id(WP_Post)
wp-content/plugins/td-composer/legacy/common/wp_booster/td_util.php:340
td_util::check_header()
wp-content/plugins/td-composer/legacy/common/wp_booster/td_wp_booster_functions.php:513
td_load_css_fonts(”)
wp-includes/class-wp-hook.php:324
WP_Hook::apply_filters(NULL, array)
wp-includes/class-wp-hook.php:348
WP_Hook::do_action(array)
wp-includes/plugin.php:517
do_action(‘wp_enqueue_scripts’)
wp-includes/script-loader.php:2299
wp_enqueue_scripts(”)
wp-includes/class-wp-hook.php:324
WP_Hook::apply_filters(NULL, array)
wp-includes/class-wp-hook.php:348
WP_Hook::do_action(array)
wp-includes/plugin.php:517
do_action(‘wp_head’)
wp-includes/general-template.php:3192
wp_head()
wp-content/plugins/td-composer/legacy/Newspaper/header.php:8
require_once(‘/home/nordsipc/publi…Newspaper/header.php’)
wp-content/plugins/td-composer/td-composer.php:254
{closure}(”)
wp-includes/class-wp-hook.php:324
WP_Hook::apply_filters(”, array)
wp-includes/class-wp-hook.php:348
WP_Hook::do_action(array)
wp-includes/plugin.php:517
do_action(‘tdc_header’)
wp-content/themes/Newspaper/header.php:2
require_once(‘/home/nordsipc/publi…Newspaper/header.php’)
wp-includes/template.php:810
load_template(‘/home/nordsipc/publi…Newspaper/header.php’, true, array)
wp-includes/template.php:745
locate_template(array, true, true, array)
wp-includes/general-template.php:48
get_header()
wp-content/plugins/td-cloud-library/wp_templates/tdb_view_search.php:8
include(‘/home/nordsipc/publi…/tdb_view_search.php’)
wp-includes/template-loader.php:106
require_once(‘/home/nordsipc/publi…/template-loader.php’)
wp-blog-header.php:19
require(‘/home/nordsipc/public_html/wp-blog-header.php’)
index.php:17

Critical Bug in td_util.php Line 1196 – Search Functionality Broken (Array to String Conversion)

Description:

I’ve encountered a critical bug in the Newspaper theme that completely breaks the WordPress search functionality. The issue is located in /wp-content/plugins/td-composer/legacy/common/td_util.php at line 1196.

Symptoms:

• Search returns “Critical Error” message
• Site becomes inaccessible when performing searches
• Error occurs both on frontend search and AJAX search
• Debug log shows: PHP Fatal error: Uncaught TypeError: implode(): Argument #2 ($array) must be of type ?array, string given

Root Cause:

Line 1196 in td_util.php contains:

$buffer .= implode(' ', $value);

The function implode() expects $value to be an array, but in some cases (particularly with custom post meta or complex search queries), $value can be a string, causing a fatal TypeError.

Temporary Fix/Workaround:

Replace line 1196 with proper type checking:


// Line 1196 - Fixed version with type checking
if (is_array($value)) {
$buffer .= implode(' ', $value);
} else {
$buffer .= (string)$value;
}


This fix checks if $value is an array before using implode(), and converts it to a string if it’s not an array.

Steps to Reproduce:

1. Install Newspaper theme with td-composer plugin
2. Use WordPress search with complex queries or custom post meta
3. Search function triggers fatal error

Environment:

• Newspaper Theme (latest version)
• td-composer plugin (included with theme)
• PHP 8.0+
• WordPress 6.x

Request:

Could you please include this fix in the next update of td-composer? This is a critical bug that breaks essential site functionality. The type checking ensures compatibility with all data types that might be passed to this function.

Affected File:
/wp-content/plugins/td-composer/legacy/common/td_util.php – Line 1196

Thank you for your attention to this matter!

Hello,

I have a valid license yet I have not received notification of an available update from 12.7.1. My concern are the xxs vulnerabilities related to td-cloud-library and td-composer.

Please advise.
Thank you.

https://patchstack.com/database/wordpress/plugin/td-composer/vulnerability/wordpress-tagdiv-composer-plugin-5-4-1-cross-site-scripting-xss-vulnerability?_a_id=473

can you urgently advice how we can download 5.4.2 as in the recent update the 5.4.1 was only available?

Thanks

TD composer is sending so many unneeded internal queries to the site that even if having a powerful cloud server, it blocks the access and get tons of 500 and 429 errors

Hello,

I am currently using Newspaper version 11.5.1 and I’m experiencing an issue with the sticky mobile menu.
On inner pages the sticky header disappears and the browser console shows this error:

Uncaught TypeError: Cannot read properties of undefined (reading ‘top’)
at tagdiv_theme.min.js

Could you please provide me with the correct tagdiv_theme.min.js file from the fixed build (v11.5.2 or newer) so that I can replace it in:

/wp-content/plugins/td-composer/legacy/Newspaper/js/

I only need the patched file, not a full theme update, as everything else on the site is working fine.
Thank you very much for your support!

Best regards

Hello tagDiv team,

I’m contacting you regarding a serious security issue I’ve been investigating on a WordPress website using the tagDiv Composer plugin.

After noticing a large number of fake user registrations, I performed a full audit of the system, including blocking the REST API, disabling XML-RPC, and adding multiple CAPTCHA layers (Cloudflare Turnstile + image CAPTCHA).
Despite all these protections, fake users were still being created automatically.

🔍 Findings

After enabling detailed logging on the user_register hook, I discovered that all unauthorized user creations originate from this file:

/wp-content/plugins/td-composer/legacy/common/wp_booster/td_ajax.php

The log entries clearly show that the wp_insert_user() call (or an equivalent function) is being triggered from inside that file, even when public registration is disabled in WordPress.

I verified that:

The file path is valid and part of tagDiv Composer.

tagDiv Composer PLUGIN Version 5.4.1 | built on 29.04.2025 10:27

The site is running the latest version of tagDiv Composer and the Newspaper theme.

After reinstalling a fresh copy of the plugin, the issue still persists (which suggests either a persistent injection or an unprotected AJAX endpoint).

THX
RAINA

Just got this error message from WordPress during configuring a plugin:
—
WordPress versie 6.8.3
Active theme: Newspaper (versie 12.7.1)
Current plugin: tagDiv Opt-In Builder (versie 1.7.1 | built on 29.04.2025 10:50)
PHP version 8.3.26

Error Details
=============
An error type E_ERROR was caused in linenumber 3276 of file /var/www/vhosts/xxx.xxx/httpdocs/wp-content/plugins/td-subscription/includes/td_subscription.php.
Message: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, null given in /var/www/vhosts/xxx.xxx/httpdocs/wp-content/plugins/td-subscription/includes/td_subscription.php:3276
Stack trace:
#0 /var/www/vhosts/xxx.xxx/httpdocs/wp-includes/class-wp-hook.php(324): td_subscription::td_post_theme_settings_mb_save_filter()
#1 /var/www/vhosts/xxx.xxx/httpdocs/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#2 /var/www/vhosts/xxx.xxx/httpdocs/wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/external/wpalchemy/MetaBox.php(880): apply_filters()
#3 /var/www/vhosts/xxx.xxx/httpdocs/wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/external/wpalchemy/MetaBox.php(2081): WPAlchemy_MetaBox->apply_filters()
#4 /var/www/vhosts/xxx.xxx/httpdocs/wp-includes/class-wp-hook.php(326): WPAlchemy_MetaBox->_save()
#5 /var/www/vhosts/xxx.xxx/httpdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#6 /var/www/vhosts/xxx.xxx/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
#7 /var/www/vhosts/xxx.xxx/httpdocs/wp-includes/post.php(5110): do_action()
#8 /var/www/vhosts/xxx.xxx/httpdocs/wp-includes/post.php(5212): wp_insert_post()
#9 /var/www/vhosts/xxx.xxx/httpdocs/wp-admin/includes/post.php(453): wp_update_post()
#10 /var/www/vhosts/xxx.xxx/httpdocs/wp-admin/post.php(227): edit_post()
#11 {main}
thrown
—

Might this be caused by a lack of memory (php,SQL,kernel)?
Thank you,
Jos