- NewsmagtagDiv Composer Tutorial
- NewsmagHow to use the Visual Composer plugin
- NewsmagHow to update a plugin
- NewsmagWhat’s included in Newsmag theme package
- NewsmagRequirements for Newsmag
- NewsmagInstall via WordPress
- NewsmagInstall via FTP
- NewsmagBlock settings tutorial
- NewsmagtagDiv Social Counter tutorial
- NewsmagHow to update the WPBakery plugin
- NewsmagPage Menu
- NewsmagCustom ad spots
- NewsmagSmart sidebar
- NewsmagVideo playlist
- NewsmagPage templates
- NewsmagHomepage – How to build and set it
Hello tagDiv Support Team,
I am building a generic Taxonomy Archive Template using the tagDiv Cloud Library/Composer. This template is assigned to a Custom Taxonomy (e.g., prompts) and needs to load correctly for all terms within that taxonomy (e.g., /prompts/term-A, /prompts/term-B, etc.).
My goal is to display content in two separate Flex Blocks, each filtered by the current taxonomy term AND a specific Category ID.
1. Goal (Desired Query Logic):
I need to enforce the following AND logic within each Flex Block, dynamically, without hardcoding the current Taxonomy Term ID:
Section 1 (Text Posts): Posts must belong to (Current Taxonomy Term) AND (Category ID 87).
Section 2 (Image Posts): Posts must belong to (Current Taxonomy Term) AND (Category ID 88).
2. Current Setup (Flex Block Filter Settings):
I am using a Flex Block and configuring the Filter tab as follows (for Section 1, Category ID 87):
Category filter: Taxonomy – Current (Used to inherit the current term)
Multiple terms filter: 87 (Hardcoded ID of the specific category)
Posts(cpts) must belong to all terms: Checked (Intended to force the AND logic)
3. Issue/Failure Point:
Despite setting the Posts(cpts) must belong to all terms checkbox, the Flex Block query is incorrectly executed.
Observed Result: The block is showing posts that belong to Category ID 87 but are associated with OTHER, unrelated taxonomies or terms outside of the current archive page.
Example: When viewing /prompts/term-A, the block is showing posts tagged with Category ID 87, but whose main taxonomy term is from a different, unrelated taxonomy (e.g., from the guides taxonomy or another custom taxonomy).
4. Request:
Could you please advise on the correct combination of settings within the tagDiv Flex Block or provide a precise workaround to generate a strict, generic WP_Query that enforces the dynamic (Current Taxonomy Term) AND (Specific Category ID) relationship?
If this combination is not possible via the standard UI, please provide a filter or shortcode parameter that achieves this specific tax_query requirement.
Thank you for your time and assistance!
Hello,
After last update of newspaper wordpress theme, our website crashed, and some error is displayed on front page, I beleive it is problem with tagdiv composer. There is no response in Theme panel, E.g. when image for new logo is selected, and saved, nothing happense.

Hello after updating toNewspaper to 12.7.3 my whole Template including header background image and logo an all settings where crasht. My Site came up with a complete new lauyout and I did not find my old settings in my Theme Panel.
Is it the intention that only cloud templates are available? I actually use a child theme to prevent this, but it probably has something to do with the Tagdiv Composer settings.In any case, my homepage became just a news list without all the layouts and texts selected in the TAGDiv Composer and using tagdiv Standard Pack
Hello,
How can I limit access to the composer and the theme panel to administrators only?
thank you very much
Hi,
This is strange; the tagDiv Composer should not have any effects on the admin dashboard. Can you please make a test using only tagDiv plugins to see if the problem is resolved? Can you provide some screenshots of the problem? If not can you contact us via mail at contact@tagdiv.com and provide there wp-admin access and some screenshots related to teh problem.
Thank you!
Hi there – I’m currently migrating my site away from Optin Builder to a different membership plugin, but will still be using the Newspaper theme. I have uninstalled the Optin Builder and am noticing that the ‘Display Restrictions’ is still showing in Composer.
Does this setting mean you can restrict display for any logged in user, or just for subscriber without using Optin Builder?
If its any logged in user, would it be possible to alter this to make it ‘subscriber’ only?
I have an extremely large site (30k pages that had been using this functionality to create a partial paywall) so being able to continue to do this would save me many weeks of work.
Thanks in advance.
Hello,
I’m experiencing a display issue in the WordPress admin area. When the tagDiv Composer plugin is active, the post titles under Posts → All Posts appear vertically (each letter stacked one below another), making it very hard to read.
I have already confirmed that this behavior disappears when I temporarily deactivate tagDiv Composer, so it seems the plugin’s CSS is affecting the admin table layout.
However, since I need the Composer active for my theme design, I can’t disable it permanently.
Could you please help me with a fix or provide a small CSS snippet to prevent tagDiv Composer’s styles from affecting the admin dashboard (specifically the post list table)?
Thank you very much 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
Hi,
This can be resolved by stretching the row, This can be done using tagDiv Composer; for this, you can use this guide – https://forum.tagdiv.com/tagdiv-composer-tutorial/ https://i.imgur.com/PmtUBYn.png
Thank you!
Hi,
Usually, this situation appears when the elements are set in the header zone and not in the content zone. You can verify this by editing the page using tagDiv Composer, selecting the element and checking in the sidebar the zone mentioned – https://i.imgur.com/VgB4uyN.png https://i.imgur.com/7ZKyiSp.png
Thank you!
PHP Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, non-static method workbox_ga::show_js() cannot be called statically in /home2/egzostiv/public_html/wp-includes/class-wp-hook.php:324 Stack trace: #0 /home2/egzostiv/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #1 /home2/egzostiv/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #2 /home2/egzostiv/public_html/wp-includes/general-template.php(3192): do_action(‘wp_head’) #3 /home2/egzostiv/public_html/wp-content/plugins/td-standard-pack/Newspaper/header.php(11): wp_head() #4 /home2/egzostiv/public_html/wp-content/plugins/td-composer/td-composer.php(254): require_once(‘/home2/egzostiv…’) #5 /home2/egzostiv/public_html/wp-includes/class-wp-hook.php(324): {closure}(”) #6 /home2/egzostiv/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array) #7 /home2/egzostiv/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #8 /home2/egzostiv/public_html/wp-content/themes/Newspaper/header.php(2): do_action(‘tdc_header’) #9 /home2/egzostiv/public_html/wp-includes/template.php(810): require_once(‘/home2/egzostiv…’) #10 /home2/egzostiv/public_html/wp-includes/template.php(745): load_template(‘/home2/egzostiv…’, true, Array) #11 /home2/egzostiv/public_html/wp-includes/general-template.php(48): locate_template(Array, true, true, Array) #12 /home2/egzostiv/public_html/wp-content/plugins/td-standard-pack/Newspaper/attachment.php(6): get_header() #13 /home2/egzostiv/public_html/wp-includes/template-loader.php(106): include(‘/home2/egzostiv…’) #14 /home2/egzostiv/public_html/wp-blog-header.php(19): require_once(‘/home2/egzostiv…’) #15 /home2/egzostiv/public_html/index.php(17): require(‘/home2/egzostiv…’) #16 {main} thrown in /home2/egzostiv/public_html/wp-includes/class-wp-hook.php on line 324
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.
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
Hi,
The theme has only a single js file and that is on a different path:
wp-content/themes/Newspaper/includes/js/tagdiv-theme.min.js
The part for the mentioned js files is from the tagDiv Composer plugin
wp-content/plugins/td-composer/legacy/Newspaper/js/tagdiv_theme.min.js also, the theme do not have a file like tdb-site.js
My recommendation: make sure that you have the latest theme version 12.73, and in case you are using a child theme, set the main theme.
Check when you are logged in and no cache and minify code is applied to see if the same error appears.
For the mobile version, you need a very good cache plugin.
You can also use the tagDiv mobile theme plugin, which will change the layout but will provide very good results – https://forum.tagdiv.com/mobile-theme-introduction/
Hi,
Please see tagDiv Composer to add on single post template and view count element to make sure that the count will work as expected.
Also, the 7-day posts will display the most viewed articles in the last 7 days. This means that you can see articles from time to time, not articles published in the last 7 days, but those that were most viewed in the last 7 days.
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,
If you use the element option to hide it then you can use the theme option to see in tagDiv Composer the elements that are hidden. Open a page in tagDiv Composer and select the manager, select the settings and enable the option Show hidden elements https://i.imgur.com/q8YV2ll.png
I hope this will help you!
Sorry, file is in
/wp-content/plugins/td-composer/legacy/common/wp_booster/
Hello tagDiv team,
I have an update regarding the search functionality errors:
Status Update:
- ✅ FIXED: The original
implode()error has been resolved in the latest version - ❌ NEW ISSUE: A critical error has been discovered at a different location
New Error Details:
Error Message: Fatal error: Uncaught Error: Cannot access offset of type array on array in td_util.php on line 1196
Problem Description: The code in td_util.php at line 1196 assumes get_query_var('post_type') always returns a string. However, this function can return an array when multiple post types are being searched. This causes a fatal error when the array is used as an array key.
Current Problematic Code (Line ~1192-1196):
$post_type = get_query_var('post_type'); if ( !empty($post_type) && $post_type !== 'post' ) { $td_cpt = td_util::get_option('td_cpt'); if ( !empty( $td_cpt[$post_type]['search_tpl'] ) ) { // ← FATAL ERROR HERE $cpt_search_template_id = $td_cpt[$post_type]['search_tpl']; } }
Proposed Fix:
$post_type = get_query_var('post_type');
// Fix: get_query_var('post_type') can return an array, handle both cases if ( is_array($post_type) ) { $post_type = !empty($post_type) ? $post_type[0] : ''; }
if ( !empty($post_type) && $post_type !== 'post' ) { $td_cpt = td_util::get_option('td_cpt'); if ( !empty( $td_cpt[$post_type]['search_tpl'] ) ) { $cpt_search_template_id = $td_cpt[$post_type]['search_tpl']; } }
Environment:
- Newspaper Theme (latest version)
- td-composer plugin (included with theme)
- PHP 8.0+
- WordPress 6.x
Impact: Search functionality is completely broken. This is a critical bug that prevents users from using the search feature on the site.
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 array type checking ensures compatibility with all scenarios where get_query_var('post_type') might return different data types.
Affected File: /wp-content/plugins/td-composer/legacy/common/td_util.php – Line 1196
Thank you for your attention to this matter!
Best regards
-
This reply was modified 9 months by
be2name.
Hello,
Yes, just edit the page where the socials are with tagDiv Composer and select the icons element, then check this option https://i.imgur.com/xfToq7E.png
Unfortunately, if you are using standard templates and the theme panel option, then there is no option to enable the open in a new tab.
Thank you!
Hi,
I believe that when you updated the theme, the theme plugins were not updated. Please connect to the website and go to Newspaper > plugins and install from there the theme plugins you were using (I believe are tagDiv Composer, tagDiv Cloud Library, and maybe tagDiv Standard pack).
Thank you!
Hi,
It is possible to have a background color on your inner column or column. Please use tagDiv Composer, select the mobile version and check the inner columns and column if there is any background color in css tab – https://i.imgur.com/SXsB3nM.png
Hi,
You need to use tagDiv Composer, edit the homepage – https://i.imgur.com/dmtvhrL.png select the menu and in the style tab you can change the font style – https://i.imgur.com/tvR89Rp.png the background color from the menu can be in the css tab – https://i.imgur.com/EOousJP.png (this css tab is on all elements from tabDiv Composer), the pink color it can be on coulumn or row that is holding the menu, you can select them and check the css tab – https://i.imgur.com/M8xc5pM.png
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!