Search Results for 'composer'

Hello,
How do I insert and edit an FAQ section on my pages with the Tagdiv Composer?

I havent been able to find one in the cloud, except for 4 different ones that I was not able to modify to make more “steps”. So can you guys please guide me in the right direction, for where I can build a FAQ section on my websites page?

hi, i had this message in my wordpress:

tagDiv Composer has a known vulnerability that may be affecting your installed version.

Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’) vulnerability in tagDiv tagDiv Composer td-composer allows Reflected XSS.This issue affects tagDiv Composer: from n/a through <= 5.4.3.
Esta vulnerabilidad no parece tener parche. Presta atención a las próximas actualizaciones del plugin.

I recently noticed that Newspaper no longer recognizes my license. The dashboard shows that the theme is not registered, even though the license was correctly activated before. How can I fix this issue?

Dear tagDiv Support,

I am using the Newsmag theme purchased through ThemeForest.

My ESET antivirus detects one of the tagDiv plugins as a potential threat. I would like to know whether this is a known false positive or if there is an updated version of the plugin that resolves this issue.

The detected plugin is: tagDiv Composer.

The antivirus reports the following threat:
HTML/Scinject.B trojan.

Could you please investigate this issue and let me know how I can safely resolve it?

If necessary, I can provide screenshots of the ESET warning and any additional information you may need.

Thank you for your assistance.

Kind regards,

WordFence is warning of a “critical vulnerability” with the TagDiv composer plugin. Is there a patch or update expected soon?

Hi, I’m using tagDiv Composer on a page-type entry. When I add a “Column text” module inside a column and click the “Edit Content” button to open the text editor (WP Editor), the popup opens but stays stuck loading indefinitely with a spinning icon, never actually showing the WordPress editor.
Steps to reproduce:

Open the tagDiv Composer editor on an entry/page.
Add a Row with columns.
Drag the “Column text” module into an empty column.
Click “Edit Content” in the module’s settings panel.
The “WP Editor” popup opens but the content never finishes loading (infinite spinner).

Expected behavior: the WordPress text editor (WP Editor) should open so I can write/paste content, including shortcodes.
Actual behavior: the popup stays loading forever and doesn’t let me edit the module’s content.
Additional context: I specifically need this module because the “Raw HTML” module doesn’t execute WordPress shortcodes (it displays them as plain text on the frontend), and “Column text” should process them correctly.
Environment: WordPress with Newspaper theme / tagDiv Composer. Relevant active plugins: Advanced Ads, WP Fastest Cache, WPCode, Popup Maker, SEO plugin (Yoast or similar), among others.
Could you let me know if this is a known bug, or if there might be a plugin/cache conflict causing the editor not to load?

Hello tagDiv team,

I’m working on a WordPress website using the Newspaper theme and tagDiv Composer.

I have an issue with one page where some old text content is still visible on the frontend/editor, but I cannot find or remove it.

The page was previously created/edited with Elementor, before switching to Newspaper/tagDiv Composer. Now I’m editing the page with tagDiv Composer, but old text sections are still displayed on the page, for example:

“Allenamenti in casa”
“Allenamenti in palestra”
“Obiettivi: massa, definizione, resistenza”

The problem is:

When I open the page with tagDiv Composer, these texts are visible, but I cannot select them as tagDiv elements.
If I click on them, no editable element is selected.
When I open the page in the normal WordPress editor, I only see a large shortcode/tagDiv content block, but searching with CTRL+F does not find those text strings.
I also checked the normal page content, but I cannot locate where this old Elementor content is stored.
I need to completely remove these old text sections from the page.

Could you please tell me where this content may be coming from?

Could it be stored in old Elementor meta fields, a Newspaper/tagDiv template, page custom fields, category description, or another theme setting?

What is the safest way to remove this old content without breaking the current tagDiv layout?

If needed, we can provide temporary WordPress admin access so you can check the page directly.

Thank you in advance for your help.

Best regards,
Sara

Hello TagDiv Support Team,

I’m using the Newspaper theme with tagDiv Composer on my WordPress website MyBody.it.

I changed the WordPress language to Italian, but many parts of the theme/interface are still not translated. From what I can see, there are more than 500 strings/phrases that would need to be translated manually.

Before proceeding manually, I would like to understand if there is a faster and official way to translate all these theme strings into Italian.

Could you please let me know:

Is there an automatic or recommended method to translate all Newspaper/tagDiv strings into Italian?
Is there an Italian language file available for the theme?
Can this be handled through the theme panel, Loco Translate, WPML, TranslatePress, or another recommended plugin?
Is there a way to import a ready-made Italian translation file instead of translating every single string manually?
Are tagDiv Composer blocks and theme elements supposed to translate automatically when WordPress is set to Italian?

At the moment, translating more than 500 strings manually would be extremely time-consuming and not really acceptable for a premium theme. If there is no faster solution, this would be quite disappointing from a usability point of view.

If needed, we can provide temporary WordPress admin access so you can check the issue directly.

Thank you in advance for your help.
Best regards,
Sara

Hello,

I am getting repeated PHP warnings inside TagDiv Composer:

Warning: Undefined array key "location" in
/wp-content/plugins/td-cloud-library/includes/tdb_config.php
on line 63782

The warnings appear across the Composer interface and make it difficult to edit my templates. I am also unable to save changes in TagDiv Composer.

Could you please advise what could cause this and how to fix it? Could it be a compatibility issue between my PHP version, Newspaper theme, TagDiv Composer, and TagDiv Cloud Library?

I have attached a screenshot. Thank you for your help.

If the img doesn’t appear : https://ibb.co/vxyNVKS3

This seems to be happening a lot lately, what are our options going forward?

https://patchstack.com/database/wordpress/plugin/td-composer/vulnerability/wordpress-tagdiv-composer-plugin-5-4-3-reflected-cross-site-scripting-xss-vulnerability

After updating our website from the previous WordPress version to WordPress 7.0.1, we encountered several critical issues with the Newspaper theme.

Environment
Theme: Newspaper
WordPress: 7.0.1
PHP: (please fill in your PHP version)
Website: https://suckhoemoi.com
Issues
Frontend displays raw shortcode/JSON instead of rendering the page properly.
Pages show raw tagDiv content instead of the designed layout.

Gutenberg editor reports:

“This block has encountered an error and cannot be previewed.”

Eventually, the entire WordPress admin became inaccessible with a “There has been a critical error on this website” message.
Troubleshooting

We investigated the issue and found that the problem is caused by td-composer.

Renaming the td-composer plugin folder immediately restored access to the WordPress admin.
After disabling td-composer, the critical error disappeared.
This strongly suggests that the current version of td-composer is not compatible with WordPress 7.0.1.
Expected behavior

The Newspaper theme and td-composer should work correctly with WordPress 7.0.1 without causing:

Critical PHP errors
Gutenberg block errors
Frontend rendering issues

Could you please confirm:

Is WordPress 7.0.1 officially supported?
Is there an updated version of td-composer compatible with WordPress 7.0.1?
If not, when will a compatible update be released?

Thank you for your support.

Best regards.

Hello, I received a notification regarding the “WordPress tagDiv Composer plugin <= 5.4.3 – Reflected Cross-Site Scripting (XSS) vulnerability (CVE-2026-57734).” I can’t dismiss the notification, but is a fix expected? I also have this link: https://patchstack.com/database/wordpress/plugin/td-composer/vulnerability/wordpress-tagdiv-composer-plugin-5-4-3-reflected-cross-site-scripting-xss-vulnerability

Hello tagDiv Support,

I recently purchased a new Regular License for Newsmag and downloaded the current full package directly from ThemeForest.

The package is Newsmag 5.4.3.6, and the bundled file:

Newsmag-tf/plugins/js_composer.zip

contains WPBakery Page Builder 8.7.2.

Our website currently uses WPBakery 6.13.0, and the homepage depends directly on WPBakery shortcodes. We need to update it securely without breaking compatibility with Newsmag, tagDiv Composer, or the existing homepage layout.

WPBakery’s official changelog lists version 8.7.3 with an additional security-related fix involving capability and nonce verification for frontend preview requests.

Could you please confirm:

1. Whether you can provide a Newsmag-tested WPBakery 8.7.3 package;
2. Whether WPBakery 8.7.3 is officially compatible with Newsmag 5.4.3.6 and may be installed manually;
3. Or whether you recommend installing the bundled WPBakery 8.7.2 version while waiting for a future Newsmag update.

Please also confirm whether an updated ThemeForest package is planned.

Thank you.