- 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
Hello TagDiv Support,
The submenus on my website (cbirt.net) are not working, but when I disable the TagDiv Composer plugin, they do.
Please help me resolve this issue.
Regards
Tamanna
Hi,
The above version differs and includes a fix for the search problem. Just make sure you have the Newspaper v12.7.3 and use the composr from this link
https://cdn.tagdiv.com/wp-content/uploads/2025/11/td-composerfix.zip
Hi,
If you can let us know the elements you want to set nofollow? If is related to social icons – https://i.imgur.com/mma1Ofy.png then you can use tagDiv Composer and set the rel attribute.
Hi,
You just need to have the last theme version, 12.7.3, when replacing the tagDiv Composer with the one provided by me, do not downgrade or do anything else.
https://cdn.tagdiv.com/wp-content/uploads/2025/11/td-composerfix.zip
Thank you!
Hello,
I think that you are referring to a section like this one – https://i.imgur.com/R0PqMNO.png if so then use tagDiv Composer to edit the template https://i.imgur.com/mTazwVh.jpeg, after that use the right click on the element you want to remove – https://i.imgur.com/wBvzQz9.png
Thank you!
Hi,
If you download the theme package, then you’ll get the WPBakery plugin inside it under the path Newspaper-tf\code\other_plugins\js_composer.zip
Thank you!
Will you be introducing any AI-powered features into the TagDiv Composer soon? For example, do you plan to add an AI-based template builder or other smart tools to make designing easier?
So, long story short. And when I say long…
Anyway, turns out. Host was able to fix the problem. Although everything pointed to it being Newspaper issue. An amazing support rep at Rocket figured it out.
Posting here in case anyone ever has a similar issue, so a potential solution may be documented
They I added this on htaccess
Header always set Content-Security-Policy “frame-ancestors ‘self’;”
And that seemed to fix it
The CSP rule was just too strict after the restore. It blocked the page from loading inside the TagDiv Composer’s iframe.
Once the rule was adjusted to allow framing from your own domain, everything clicked back into place.
The server itself was working fine; it was just the browser being told “don’t show this page inside another page.”
Hi Calin, i also get warnings from my hosting provider about : WordPress tagDiv Composer Plugin <= 5.4.1 is vulnerable to Cross Site Scripting (XSS)
Are there any updates yet?
UPDATE: Sorta…
unable to edit any templates (e.g., post or category templates). When I attempt to open a template for editing, the Composer editor either fails to load, displays a blank screen, or encounters an error, preventing any modifications.
Crucially, the TagDiv Composer seems to work for editing regular pages and posts. I’m guessing the problem is specifically localized to the template editing functionality?
I’ve already done many troubleshooting steps, including:
WordPress & Theme/Composer Versions:
– My WordPress core is up-to-date. 6.8.3
– Dashboard says WP, Themes and Plugins are all up to date. but on the Newspaper updates page it shows I need to update to 12.7.3
– Newspaper theme currently updated to 12.6.9, can’t upto to 12.7.3
Theme Reinstallation Attempts:
– I’ve tried a significant process to ensure theme integrity: I manually downloadeed 12.7.3 from ThemeForest and then performed a fresh, clean update to the current latest version of the Newspaper theme and its associated plugins. This was done to rule out any corrupted files. It wont et me update though, it doesnt complete it.
Site Restore:
– I performed a full site restore from a recent working backup, but the template editing issue persists.
Caching Management:
– I have thoroughly cleared all levels of caching: my WordPress caching plugins (e.g., [mention specific plugin if you use one]), server-side cache via my hosting provider, CDN cache (Cloudflare, etc.), and my browser cache (including incognito mode).
PHP Environment Configuration:
– I have verified my server’s PHP version (currently running 8.3.22)
– I have also manually increased critical PHP limits in my php.ini and wp-config.php, including:
– memory_limit 1024M
– post_max_size 1024M
– upload_max_filesize 1024M
– max_execution_time 600
– max_input_vars 5000
WordPress Core Diagnostics:
– I’ve checked the WordPress Site Health tool, and it reports no issues
– I’ve re-saved permalinks from the WordPress settings.
– I’ve tested editing in different browsers, ccomputers and incognito/private windows.
Plugin Conflicts:
– While pages/posts edit fine, I have also systematically deactivated non-TagDiv plugins that might interact with editors or custom content types to check for conflicts, but the template editing issue remained.
My leading hypothesis is that the problem may be tied to a version mismatch or conflict? My current system is detecting Newspaper Theme 12.6.9, while it seems certain theme components or template assets might have been created or are expecting an environment compatible with Newspaper Theme 12.7.3? This discrepancy appears to specifically affect the way TagDiv Library interacts with or loads template files, as all other Composer functionalities for pages and posts appear to be working correctly.
Could you please provide guidance on this specific issue? I can provide screenshots, access to the browser console, or temporary admin access if needed.
Thank you for your urgent attention to this matter.
-
This reply was modified 9 months by
mikeshecky.
Hi tagDiv Support Team,
I hope this message finds you well.
I’m currently working with the Newspaper theme on the site redesign, stage with newspaper and live with my old theme.
My situation:
I’ve completed a complete site redesign on my staging environment using Newspaper theme’s template system. Now I need to push these templates to my live/production site without migrating all the posts/data (as the production site already has all the content).
What I need to transfer:
Custom templates (single post, category, homepage, etc.)
tagDiv Composer blocks and layouts
Theme settings and customizations
Any template configurations
What I want to keep on production:
All existing posts and content
Database data
Media files
My question:
What is the best way to export/import only the Newspaper theme templates and settings from staging to production? I want to avoid a full database migration since both sites have the same content, and I only need to update the design/templates.
Are there any built-in Newspaper theme tools or recommended methods for this specific scenario?
Thank you for your assistance!
Hi,
Related to the search problem, it will be need to replace the current theme plugn tagDiv Composr with the one from here – https://cdn.tagdiv.com/wp-content/uploads/2025/11/td-composerfix.zip
Also, we’ll prepare a theme update that will include the fix.
Thank you!
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/
Hey there,
I have an issue with my website where whenever I try to save a page via the composer, it just keeps spinning and nothing happens. I read some things in the forum but nothing described helped. I deinstalled and installed TagDiv Composer, I set my security plugin to learning, I checked CloudFlare and so on. I guess I might be missing something I don’t know what it is.
I made an image of my network tab – https://postimg.cc/LgpLCf6N
I get to a 10 second time out and it just crashes there.
Please help me finding a way to fix this.
Best regards!
Hi,
Please make sure that the thene plugins you used before the update are installed. Those can be installed from Newspaper > plugins. You should have installed and activated tagDiv Composer, cloud library and possible tagdiv standard pack.
Thank you!
Hi,
This is because some theme plugins are no longer installed. Go to Newspaper > plugins and make sure that tagDiv Composer, cloud Library, and tagDiv Standard Pack are installed.
Thank you!
Hi, my website’s main page content disappeared after the update.
It is currently empty.
I can see all the content in the TagDiv Composer!. I tried to save, but still all content are not their
Hi,
Related to the search problem, it will be need to replace the current theme plugn tagDiv Composr with the one from here – https://cdn.tagdiv.com/wp-content/uploads/2025/10/td-composer-fix.zip
Also, we’ll prepare a theme update that will include the fix.
Thank you!
Hi,
Normally, if is only a font, even if it’s in different versions, if you set it in the theme panel, it should not create problems, but in case you want to load it only in a few pages and those pages are create with tagDiv Composer, then use the html element (set it as first element in content) and add the font there. For more detsils you can check this guide https://www.wpbeginner.com/wp-tutorials/how-to-host-local-fonts-in-wordpress-for-a-faster-website/
Thank you!
Hi,
Ok, so the code is working for the desktop and responsive version, this is good because you can use the responsive version.
Now the question is, are you facing the problem using the tagDiv Mobile theme plugin or using the mobile page template?
If is the mobile page template, it should be working without any extra code, but in case you are using the tagdiv mobile theme plugin then the code should be set in mobile functions.php too wp-content/plugins/td-composer/mobile/functions.php
Thank you!
Hi andrea.turco,
All our Newsletter plugin does is provide some designs for the newsletter you will be using, in this case, MailerLite, so what you can do is set the embed code provided by MailerLite with the tagDiv Composer in the column text or title text https://imgur.com/DSSni9j, and the newsletter will display.
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,
What I will recommend is to create your own blog page using tagDiv Composer, set a flex block that you like the most and adjust it according to your needs.
If you want to use the blog option provided by wordpress – https://i.imgur.com/14YPlku.png, then you’ll need to install tagDiv Standard Pack from Newsapper > plugins and select from the theme panel the module layout you want for your blog – https://i.imgur.com/LyzqlLB.png
Thank you!