- NewspapertagDiv Composer Tutorial
- NewspaperCredit System
- 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
- NewspaperModal Popup
- NewspaperFlex Block Settings Guide
- NewspaperSocial Sharing
- NewspaperSingle Post Shortcodes
- NewspaperInfinite Loading for Single Posts
- NewspaperThe Newspaper Mobile Theme: Introduction
- NewspaperHow to Add a Logo in Newspaper
- NewspaperCustom Post Type Support
- NewspaperCloud Library Templates
- NewspaperDesign your Post Pages using the Cloud Library Templates
- NewspaperHeader Builder
- NewspapertagDiv Cloud Library Plugin
- NewspaperAd Box Element and Ads Overview
Hello!
Whenever I try to edit the start page of my site with tagdiv composer I get this error:
This site can’t be reached
The webpage at https://fontan.nu/wp-admin/post.php?post_id=1123&td_action=tdc&tdbTemplateType=page might be temporarily down or it may have moved permanently to a new web address.
ERR_HTTP2_PROTOCOL_ERROR
This happens both when I try to do it from the WordPress interface and if I go to the site and press the bar at the top.
What am I doing wrong?
Thank you inadvance
Best regards
Amanda at Lunds Fontänhus
Hello. We recently found out that we have a huge wp_options table (over 70 GB!!!) and over 12 000 000 rows are filled with td transients. I am attaching you a screenshot here: https://prnt.sc/E806MILYD0T0
We started to delete them batch by batch because, even if we have a cutting edge webserver, it is impossible to run a query to delete 12 M rows.
Can you help us in preventing this situation since, in the past few days, we had few server dropdown because of this?
We are using TagDiv Newspaper 12.7.1, which is the latest version, with tagDiv Composer, tagDiv Cloud Library, tagDiv Mobile Theme, Official AMP for WP and tagDiv Standard Pack plugins activated and updated to the latest build.
Also, we using WordPress LiteSpeed Cache plugin with Litespeed Webserver.
I just installed Newspaper and this is my first experience with the theme.
I want to update Header and I noticed it is using a Cloud template.
When using Cloud templates, I go to Header templates, try to Edit with TD Composer the template “Header Template – Gourmet PRO” and I get page that says:
“Sorry, this page doesn’t exist.
Please check the URL or go back a page.
404 Error. Page Not Found.”
Then I close that and go back to Cloud templates, and click the “+” symbol to see if it will let me add a new template, and it show blank page with “Invalid reply from server endpoint.”
I basically can’t do anything with header. I want to use the Header of the sample website, but add my logo to it. That is all I wanted to do.
What is going on with this theme?
Good morning,
Please resolve the following error so that I can update TAG DV COMPOSER on my blog:
[02-Oct-2025 07:33:51 UTC] PHP Fatal error: Cannot redeclare function tdc_on_remove_core_updates() (previously declared in /home2/yscrepmo/public_html/wp-content/plugins/td-composer/includes/tdc_main.php:344) in /home2/yscrepmo/public_html/wp-content/plugins/td-composer/includes/tdc_main.php on line 344
Hi,
I’m really into for support.
URL: https://dekarperhoeve.com/
I’ve followed every documentation steps, I’ve been working with ChatGPT for the last 48 hours on this menu, nothing seems to work.
On the webpage, the menu looks amazing. But when I browse via browser on phone, it’s a struggle to work on it. Somehow it’s a Cloud template and I tried so many steps with TD Composer I lost track. On the mobile version the menu I see the signin option and the social media buttons. I want these to dissapear. I can’t find it. Also when I select background color I don’t see this option.
Please Please assist me in this matter, thank you so much.
Hi,
That might not work. The subtitle is kept in the wp_postmeta table under the meta key td_post_theme_settings, and the data is serialized. And it’s not just the subtitle, everything from the theme that is related to a post is kept there, for example https://prnt.sc/dGC2FVO-28bK Doing it through sql is risky, and I don’t think there’s a plugin that could do something like this. Maybe its possible through a php script but I can’t say for sure. Unfortunately even if its possible somehow, it may not be so easy. Doing it wrong may damage the rest of the theme post meta.
I would actually suggest something different. You could just import the subtitles in a custom field and display that instead of the theme subtitle. A custom field can be created with the ACF plugin and attached to posts https://www.wpallimport.com/import-advanced-custom-fields-acf-csv/ Then you can display it in the post page with the theme, the composer has a custom field element https://prnt.sc/sVivXW1izpSr This method would be easier and it should work fine.
Thanks.
Hi,
Actually we had a few other reports concerning this file wp-content/plugins/td-composer/legacy/common/common.php
Its a security module called CPGuard which flags a part of the code from that file from the composer. It’s a false positive however, we checked those cases and the code in the file was as it should be. The solution was to whitelist the file or path https://opsshield.com/help/cpguard/whitelist-files/ We will however check more to see if we can modify the code in the file so it doesn’t trigger security rules.
I’m not sure about WPBakery however. You could install the latest version for it https://cdn.tagdiv.com/wp-content/uploads/2025/10/js-composer-8.6.1.zip Seems they made security improvements in a recent update https://kb.wpbakery.com/docs/preface/release-notes/
Thanks.
My service provider has notified me that I have these vulnerabilities on my site.
Could you provide an update?
Thank you.
wp-content/plugins/td-composer/legacy/common/common.php {HEX}Malware.Expert.php.base64.decode.UNOFFICIAL
wp-content/plugins/js_composer/assets/lib/vendor/node_modules/bootstrap3/dist/js/bootstrap.min.js SecuriteInfo.com.End-Of-Life-found-in-Bootstrap.UNOFFICIAL
Hi,
We’re still working on a few more fixes we would like to include in the update.
The fix for the issue with editors not being able to use the composer is included in the next update. In the meantime please use this composer version which contains the fix https://cdn.tagdiv.com/wp-content/uploads/2025/05/td-composer.zip The problem should be solved after installing it.
We are very sorry for this situation and inconvenience. Hopefully next week an update will be released.
Thanks.
I have asked for TagDiv support for help with an issue with the header logo image on the Front Page of my Newspaper themed website, https://www.thethinkingconservative.com/. TagDiv’s support person, Bettina, did something to make the logo fit in a larger space on my Front Page which I wanted done, but did not explain how she did it although I asked. There is an issue with what she did however, the larger header logo shows up larger in the Brave browser, but not in the Chrome browser.
I have no idea what Bettina did and a different support person did not know either and told me to upload a larger image in the TagDiv editor for the Front Page. When I attempted to upload a larger logo image like your support recommended, it literally broke the Front Page of my website and now it won’t open in TagDiv Composer no matter how long I wait, so I can no longer edit the Front Page in TagDiv Composer and the Front Page is no longer showing correctly on the website. The header area, menu etc. is missing from the entire website.
This code can be seen at the bottom of the broken Front Page
[td_flex_block_1 modules_on_row=”” image_size=”” image_floated=”hidden” image_width=”eyJwaG9uZSI6IjMwIn0=” image_height=”eyJwaG9uZSI6IjExMCJ9″ show_btn=”none” show_excerpt=”eyJwaG9uZSI6Im5vbmU
I have checked and everything is correct with the templates, menus etc. and it is not a plugin issue, but because I can’t open the homepage to edit it there is nothing I can do. I deleted the larger image I had uploaded from the library, but the image didn’t show up in uploads in File Manager in cPanel which I thought was strange.
I do not want to upload a new Front Page template as it took so much work to get the Front Page correct and I can’t just upload the header template because I can’t open the Front Page with the TagDiv editor.
Please look at the Front Page of the website and you will see the issues.
How do I fix this?
Description:
Hello TagDiv Support,
After enabling CSP on my site, the browser shows this error:
Content Security Policy blocks the use of ‘eval’ in JavaScript.
It looks like td-composer or some Newspaper JS files are still using eval() or new Function(). To make the site work, I would need to add ‘unsafe-eval’ in the CSP header, but this is not secure.
Can you please confirm if there is an update or patch that removes the dependency on eval() in the Newspaper theme / tagDiv Composer plugin?
I am currently using:
• Newspaper theme version: [insert version]
• tagDiv Composer version: [insert version]
I would like to know if there is a safer solution than enabling ‘unsafe-eval’ in CSP.
Thank you!
Hi,
Normally each element has its own default CSS, which is replaced if the element is customized in the composer. However, it’s strange that CSS used by the column title element affects other headings. The CSS is applied via a unique class, not targeting headings. Like in the code you provided, the unique class is .tdi_51, and unless this class is set on a heading then the CSS should not apply to it.
Could you provide a link to where I can see this issue? If you can’t provide a link in the forum, please send us an email at contact@tagdiv.com and we can continue there.
Let me know.
Thanks.
I apologize for butting in, but our host is reporting the same problem on two separate sites: the file …/td-composer/legacy/common/common.php has been quarantined because it was detected as an infected file.
They suggest it “entered” through a WordPress, theme, or plugin vulnerability, but since the same file is on two different sites that share no plugins, it’s either WordPress or the theme, but my Newspaper installations are working very fine.
Please, Calin, confirm us if you can, or as soon as you can, that this is a “false positive” to give us peace of mind.
We’re always very grateful.
Mattia
The homepage I designed was completely new with Elementor, not using TD Composer, I only used it to design the interface for the Post, Category and Tag pages, the Homepage completely used Elementor.
I tried all the ways you listed before but they didn’t work, it only stopped when I turned off the TD Composer Plug in
Sehr geehrtes Support-Team,
bei meinen Seiten tritt immer wieder folgendes Problem auf:
Das Theme (TagDiv Composer/Newspaper) wendet automatisch Standard-CSS auf meine Überschriften (H1–H6) an. Beispiel:
H1 | .tdi_51{padding-bottom:55px!important}.tdm_block_column_title_simplified_2{display:flex;flex-direction:column;margin:0;transform:translateZ(0);font-size:28px;line-height:1.3;font-weight:400;color:#111}.tdm_block_column_title_simplified_2>.td-element-style{z-index:-1}.tdm_block_column_title_simplified_2 .tdm-title-s-text{text-align:left}.tdm_block_column_title_simplified_2:after{content:”;order:2;position:relative;display:block;margin:14px auto 0 0;height:1px;background-color:var(–td_theme_color,#4db2ec);transition:all 0.2s ease}.tdi_51 .tdm-title-s-text,.tdi_51 .tdm-title-s-subtitle{text-align:center}.tdi_51:after{margin-left:auto;margin-right:auto;width:30%;background:var(–mm-custom-color-4)}.tdi_51{color:var(–mm-custom-color-1);font-family:var(–global-1)!important;font-size:56px!important}.tdi_51:hover:after{width:60%}Datenschutzerklärung
Dadurch erhalten auch rechtliche Texte wie meine Datenschutzerklärung unerwünschte Formatierungen (z. B. Linien unter den Überschriften, veränderte Textausrichtung, falsche Schriftgrößen).
Meine Fragen:
Warum werden diese Styles immer wieder automatisch eingebunden, selbst wenn ich eigene Formatierungen setze?
Gibt es eine Möglichkeit, diese globalen Stile für bestimmte Seiten (z. B. Datenschutzerklärung) zu deaktivieren?
Kann man die automatische Anwendung der Klasse .tdm_block_column_title_simplified_2 generell abschalten?
Vielen Dank im Voraus für Ihre Unterstützung.
Mit freundlichen Grüßen
I also did not want to use 2 Builders but TD Composer is not as feature-rich and easy to use as Elementor, and I found it difficult to control as I wanted and did not have many additional add-ons, so I had to use both. I used it on a few of my previous websites and it was fine until I used it on my latest website. It worked fine at first but after importing some interfaces from TD Composer Cloud, it had problems.
When adding a new event, a fatal error appears.
Notice: Function register_uninstall_hook was called incorrectly. Only a static class method or function can be used in an uninstall hook. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-includes/functions.php on line 6121
Notice: Funkcja _load_textdomain_just_in_time została wywołana nieprawidłowo. Ładowanie tłumaczenia dla domeny td-cloud-library zostało uruchomione zbyt wcześnie. Zwykle jest to wskaźnik, że jakiś kod we wtyczce lub motywie działa zbyt wcześnie. Tłumaczenia powinny zostać załadowane podczas akcji init lub później. Dowiedz się więcej: Debugowanie w WordPressie. (Ten komunikat został dodany w wersji 6.7.0.) in /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-includes/functions.php on line 6121
Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-includes/functions.php on line 7360
Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-includes/functions.php on line 2195
Fatal error: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, null given in /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-content/plugins/td-subscription/includes/td_subscription.php:3276 Stack trace: #0 /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-includes/class-wp-hook.php(324): td_subscription::td_post_theme_settings_mb_save_filter(NULL, ‘1975’) #1 /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters(NULL, Array) #2 /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/external/wpalchemy/MetaBox.php(880): apply_filters(‘wpalchemy_filte…’, NULL, ‘1975’) #3 /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/external/wpalchemy/MetaBox.php(2081): WPAlchemy_MetaBox->apply_filters(‘save’, NULL, ‘1975’) #4 /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-includes/class-wp-hook.php(326): WPAlchemy_MetaBox->_save(1975) #5 /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #6 /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #7 /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-includes/post.php(5110): do_action(‘save_post’, 1975, Object(WP_Post), true) #8 /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-includes/post.php(5212): wp_insert_post(Array, false, true) #9 /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-admin/includes/post.php(453): wp_update_post(Array) #10 /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-admin/post.php(227): edit_post() #11 {main} thrown in /home/fdwhhmkcar/domains/spokorumia.pl/public_html/wp-content/plugins/td-subscription/includes/td_subscription.php on line 3276
Hello
I use Elementor to build the homepage interface, at first everything was fine, however after I finished the homepage interface and switched to using Newpaper templates for blog interfaces, the homepage can no longer be edited with Elementor in the Elementor Full Width template. The content created by Elementor is completely hidden. I can only switch to the Elementor Canvas template to edit.
When I turn off TD Composer, it works normally again, so I think that TD Composer caused some error during the process of importing interfaces from the cloud, which hindered Elementor editing in the Elementor Full Width template.
Please check for me
Thanks
Hi,
Yes this can be done using a special css, like this one:
.td-post-content a {
position: relative;
display: inline-block;
text-decoration: none;
color: #000;
}
.td-post-content a::after {
content: "";
position: absolute;
left: 0;
bottom: -2px;
width: 50%;
height: 2px;
background-color: currentColor;
transition: width 0.3s ease;
}
.td-post-content a:hover::after {
width: 100%;
}
The css can be set global in theme panel > custom code> custom css, or locally in single post template, edit it with tagDiv Composer and drag a raw css element and set the css in it.
Hi,
You need to use the tagDiv Composer, not the Customizer to add the “Buy Me a Coffee” Widget – https://i.imgur.com/4eIYJcT.png https://i.imgur.com/PEtDRyh.png the widgets can be set here – https://i.imgur.com/3rHte0d.png
Hi,
A part of the settings can be done using tagDiv Composer and setting the padding on meta – https://i.imgur.com/AlIrzhL.png, another one is related to this css
.cls-wpb .td-module-meta-info{
border-radius: 0 0 10px 10px;
min-height: 210px;
}
That is making a height of at least 210px for the meta (section holding the text information for the product).
Hello,
It is possible to have a security scanner that detects the base64 and sees it as a possible threat. Can you let me know the tool use to scan the /td-composer/legacy/common/common.php and get the results you got?
Thank you!
Yesterday I changed the files, and it started working again. As I explained in the email.
Today the same error appeared again:
[15-Sep-2025 13:17:07 UTC] PHP Warning: require_once(legacy/common/common.php): failed to open stream: No such file or directory in /home/lacuarta/public_html/wp-content/plugins/td-composer/td-composer.php on line 146
[15-Sep-2025 13:17:07 UTC] PHP Fatal error: require_once(): Failed opening required ‘legacy/common/common.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in /home/lacuarta/public_html/wp-content/plugins/td-composer/td-composer.php on line 146
So I did the same thing again: I disabled the td-composer and td-cloud-library plugins, went into WordPress, and uploaded them again manually.
It started working again, but what intrigues me is that after a while the same error comes back.
These codes are coming from the /td-composer/legacy/common/common.php
common.php php.base64.decode
common.php php.base64.decode
common.php php.base64.decode
Hi,
You just need to add to that button the class:
tdm-pmh-close
– https://i.imgur.com/24OlVXc.png
To have the pop-up on all devices, you should set it in the footer, not in the header. Also, you can check each viewport in the part from the tagDiv Composer to see how it is looking.
Thank you!
