- 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
Hi,
The thing is that you can not create a page template, only pages, and if you like a page, what you need to do is to duplicate the page and edit it with tagDiv Composer to make it the way you like.
Thank you!
Fehler-Details
==============
Ein Fehler vom Typ E_ERROR wurde in der Zeile 3276 der Datei /home/expomaxt/public_html/gartenwoche_2024/wp-content/plugins/td-subscription/includes/td_subscription.php verursacht. Fehlermeldung: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, null given in /home/expomaxt/public_html/gartenwoche_2024/wp-content/plugins/td-subscription/includes/td_subscription.php:3276
Stack trace:
#0 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/class-wp-hook.php(324): td_subscription::td_post_theme_settings_mb_save_filter(NULL, ‘3213’)
#1 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/plugin.php(205): WP_Hook->apply_filters(NULL, Array)
#2 /home/expomaxt/public_html/gartenwoche_2024/wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/external/wpalchemy/MetaBox.php(880): apply_filters(‘wpalchemy_filte…’, NULL, ‘3213’)
#3 /home/expomaxt/public_html/gartenwoche_2024/wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/external/wpalchemy/MetaBox.php(2081): WPAlchemy_MetaBox->apply_filters(‘save’, NULL, ‘3213’)
#4 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/class-wp-hook.php(326): WPAlchemy_MetaBox->_save(8441)
#5 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#6 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#7 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/post.php(5110): do_action(‘save_post’, 8441, Object(WP_Post), true)
#8 /home/expomaxt/public_html/gartenwoche_2024/wp-includes/post.php(5212): wp_insert_post(Array, false, true)
#9 /home/expomaxt/public_html/gartenwoche_2024/wp-admin/includes/post.php(2003): wp_update_post(Array)
#10 /home/expomaxt/public_html/gartenwoche_2024/wp-admin/includes/post.php(2104): wp_create_post_autosave(Array)
#11 /home/expomaxt/public_html/gartenwoche_2024/wp-admin/post.php(336): post_preview()
#12 {main}
thrown
Issue Description:
When activating and using TagDiv Composer together with the TagDiv Standard Pack in the Newspaper theme, the MySQL/MariaDB database quickly reaches maximum resource usage.
The problem comes from the large number of queries containing the SQL_CALC_FOUND_ROWS clause, which is highly inefficient on large tables such as wp_posts.
As a result, read operations become very slow and the database consumes excessive CPU and memory, eventually leading to site performance degradation and database connection errors.
I’ve used newspaper for years, but am having a problem using an edited page template.
I’ve used the WP admin “Cloud templates” tab and have imported and edited a template, then saved and renamed it. It appears under “Page templates.” So far, so good.
Now I want to use that template to create a series of pages. I create a new page using TagDiv Composer and go to select my template under “Cloud”, but the dialog box does not show me my saved templates, only the canned Newspaper templates from the cloud.
Any ideas?
This only happends with the pages created with the TagDiv Composer.
Hi,
There isn’t unfortunately. There is no relation between our composer and elementor. You must either build the page with elementor or with the composer. Our composer is old if we refer to when it was released, so is elementor. We introduced it in Newspaper 8, but that doesn’t mean we haven’t improved it a lot. Please check the theme demos and the cloud library https://cloud.tagdiv.com/#/load/All Everything you see there is built with the composer. It’s quite a capable builder. You could consider building the page with it if you want to use blocks and grids from the theme. Let us know if you need help with it.
Thank you!
Hi,
That’s correct, the theme itself is about 3 MB. Only old versions of the theme were larger, before we had to make these modifications https://tagdiv.com/updating-the-core-of-tagdiv-themes/
So the bulk of the theme is in the composer plugin, which is required. Please install the theme normally, and then there should be a prompt to install the composer. Then the theme can be activated with the license key and that’s it. You can install a theme demo and begin customizing it with the composer.
Please let us know if you have more questions.
Thank you!
Hi,
Please let me know by email how you want the button to be aligned and mention a few details about the other customizations. All of these should be possible either in the composer or with some CSS. And please make the website account I used before an admin again, or provide a new one. I will help, let me know.
Thank you!
Hi,
That section has filter settings. In the composer the element can be selected by clicking like this below it https://prnt.sc/7lkzzWqLZir9 There you can set the filter you want. Please try it. In case there are still issues, please send us an email at contact@tagdiv.com and provide admin login for the website, we will check as well.
Thank you!
Hello
I am using Elementor to make Landing Page, I want to add widgets of the interface like Flex block and Big Grid Flex but I can’t add them.
The available options are Tagdiv Block which is very old and can’t customize anything?
Is there any way to connect Tagdiv Composer with Elementor?
Thanks
We ran into a reproducible issue with the Newsmag theme (tagDiv Composer) when importing a demo on PHP 8.2.
Symptoms:
tagDiv Importer stops with error:
Fatal error: Uncaught TypeError: Cannot access offset of type string on string in td_demo_util.php
Log also shows Undefined variable $sidebars_widgets and Automatic conversion of false to array is deprecated.
Root cause:
In td_demo_widgets::add_widget_to_sidebar(), the code uses $sidebars_widgets before it’s retrieved from get_option(‘sidebars_widgets’) and normalised.
PHP 8.x is stricter about this than PHP 7.x — in PHP 7 it silently converted null/false to array; in PHP 8 it throws a fatal error.
Workaround:
Patch the function to fetch and normalise $sidebars_widgets before using it. Here’s a minimal fix:
static function add_widget_to_sidebar($sidebar_id, $widget_name, $atts) {
$tmp_sidebars = td_options::get_array('sidebars');
if (empty($tmp_sidebars)) {
$tmp_sidebars = array();
}
if (!in_array('td-' . $sidebar_id, self::$hard_coded_sidebars) &&
!in_array($sidebar_id, $tmp_sidebars)
) {
self::kill(__CLASS__, __FUNCTION__,
'No sidebar with the name provided! - td-' . $sidebar_id,
array_merge(self::$hard_coded_sidebars, $tmp_sidebars)
);
}
// Normalise $atts
if (!is_array($atts)) {
if (is_string($atts)) {
$tmp = json_decode($atts, true);
$atts = is_array($tmp) ? $tmp : array();
} else {
$atts = array();
}
}
// FIX: Get and normalise $sidebars_widgets BEFORE using
$sidebars_widgets = get_option('sidebars_widgets');
if (!is_array($sidebars_widgets)) {
$sidebars_widgets = array();
}
$sb_key = 'td-' . td_util::sidebar_name_to_id($sidebar_id);
if (!isset($sidebars_widgets[$sb_key]) || !is_array($sidebars_widgets[$sb_key])) {
$sidebars_widgets[$sb_key] = array();
}
// Normalise widget instances
$opt_key = 'widget_' . $widget_name;
$widget_instances = get_option($opt_key);
if (!is_array($widget_instances)) {
$widget_instances = array();
}
// Add instance
$widget_instances[self::$last_widget_instance] = $atts;
update_option($opt_key, $widget_instances);
// Assign widget to sidebar
$sidebars_widgets[$sb_key][self::$last_sidebar_widget_position] =
$widget_name . '-' . self::$last_widget_instance;
update_option('sidebars_widgets', $sidebars_widgets);
self::$last_sidebar_widget_position++;
self::$last_widget_instance++;
}
Notes:
Tested on PHP 8.2.29 with Plesk Obsidian and Newsmag 5.4.3.3.
This patch allows the demo importer to complete successfully without downgrading PHP.
The EXIF warnings you may see in logs during import are unrelated and non-fatal.
If tagDiv devs see this — moving the $sidebars_widgets = get_option(‘sidebars_widgets’) block up in the function would resolve this for all PHP 8+ users.
Hi,
I’m running into a fatal error when trying to import a demo in Newsmag 5.4.3.3 (registered) with tagDiv Composer on a Plesk server.
The issue occurs on PHP 8.2 and PHP 8.4 during the demo import process.
Error Details
swift
Kopier
Rediger
PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string
in /wp-content/plugins/td-composer/legacy/common/wp_booster/wp-admin/panel/td_demo_util.php:2620
Stack trace:
#0 /…/td_import.php(159): td_demo_widgets::add_widget_to_sidebar()
#1 /…/td_demo_installer.php(319): require_once()
…
Additional warnings/notices during import:
Multiple exif_read_data(…): Incorrect APP1 Exif Identifier Code warnings
_load_textdomain_just_in_time called too early (WordPress 6.7.0 notice)
The fatal error prevents the demo from completing.
Environment
Theme: Newsmag 5.4.3.3 (registered)
tagDiv Composer: bundled version (legacy importer paths)
WordPress: 6.7.0
PHP Versions Tested: 8.2.x (FPM), 8.4.x (FPM) — both fail
Server: Plesk Obsidian, Apache2 (proxy_fcgi)
What We Found So Far
The error happens inside the legacy demo importer, specifically in td_demo_widgets::add_widget_to_sidebar() — looks like a PHP 8.1+ type handling change is breaking it.
The /legacy/… path suggests the importer code hasn’t been fully updated for PHP 8.2+.
No public changelog entries mention a fix for this specific fatal error.
There’s no pinned forum post or KB article covering it.
Rolling back to PHP 8.1 might work, but my current server doesn’t have it installed — planning to try that as a temporary workaround.
If the vendor has already patched this in a newer Composer or theme build, it’s not mentioned in docs.
Questions
Is this a known issue with the current demo importer on PHP 8.2+?
Has it been fixed in a newer release of Newsmag/tagDiv Composer (non-legacy importer)?
Is there an official workaround besides downgrading to PHP 8.1?
If I install PHP 8.1 just for the import, will that be supported, or do you recommend patching the importer code for PHP 8.2+?
Thanks in advance — happy to provide full error logs or run tests if it helps.
— Terje
Hi,
The latest sidebar can be edited from widgets section – https://i.imgur.com/XN3JABe.png – https://i.imgur.com/yYuaWXs.png
The best way will be to remove the Page Builder + Latest Articles + Pagination on Default Template and use tagDiv Composer to add the elements as you want.
Thank you!
Hi,
Please go to Newspaper > Plugins and install from there the tagDiv Standard Pack plugin, after that the old blocks should be back in Composer.
Thank you!
[STDERR] PHP Fatal error: Uncaught TypeError: Unsupported operand types: int – string in /home/livingin1/public_html/wp-content/plugins/td-cloud-library/state/single/tdb_state_single.php:1338\nStack trace:\n#0 /home/livingin1/public_html/wp-content/plugins/td-cloud-library/shortcodes/single/tdb_single_date.php(216): tdb_state_single->{closure}()\n#1 /home/livingin1/public_html/wp-content/plugins/td-cloud-library/shortcodes/single/tdb_single_date.php(216): Closure->__invoke()\n#2 /home/livingin1/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): tdb_single_date->render()\n#3 /home/livingin1/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function()\n#4 [internal function]: do_shortcode_tag()\n#5 /home/livingin1/public_html/wp-includes/shortcodes.php(273): preg_replace_callback()\n#6 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode()\n#7 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/shortcodes/vc_column.php(440): tdc_composer_block->do_shortcode()\n#8 /home/livingin1/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): vc_column->render()\n#9 /home/livingin1/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function()\n#10 [internal function]: do_shortcode_tag()\n#11 /home/livingin1/public_html/wp-includes/shortcodes.php(273): preg_replace_callback()\n#12 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode()\n#13 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/shortcodes/vc_row.php(1204): tdc_composer_block->do_shortcode()\n#14 /home/livingin1/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): vc_row->render()\n#15 /home/livingin1/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function()\n#16 [internal function]: do_shortcode_tag()\n#17 /home/livingin1/public_html/wp-includes/shortcodes.php(273): p
2025-08-12 06:39:54.154375 [NOTICE] [100585] [T0] [213.183.63.23:44728>87.97.241.170#APVH_livinginashoebox.com:443] [STDERR] reg_replace_callback()\n#18 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode()\n#19 /home/livingin1/public_html/wp-content/plugins/td-composer/includes/shortcodes/tdc_zone.php(771): tdc_composer_block->do_shortcode()\n#20 /home/livingin1/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): tdc_zone->render()\n#21 /home/livingin1/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function()\n#22 [internal function]: do_shortcode_tag()\n#23 /home/livingin1/public_html/wp-includes/shortcodes.php(273): preg_replace_callback()\n#24 /home/livingin1/public_html/wp-includes/class-wp-hook.php(324): do_shortcode()\n#25 /home/livingin1/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters()\n#26 /home/livingin1/public_html/wp-content/plugins/td-cloud-library/wp_templates/tdb_view_single.php(189): apply_filters()\n#27 /home/livingin1/public_html/wp-includes/template-loader.php(106): include(‘…’)\n#28 /home/livingin1/public_html/wp-blog-header.php(19): require_once(‘…’)\n#29 /home/livingin1/public_html/index.php(17): require(‘…’)\n#30 {main}\n thrown in /home/livingin1/public_html/wp-content/plugins/td-cloud-library/state/single/tdb_state_single.php on line 1338\n
Hi,
If you need to update the theme manually, once the theme update is complete, please go to Newspaper > Plugins and click “Update” for each theme plugin you’re using.
After all theme plugins have been updated, start re-enabling them beginning with tagDiv Composer.
Let us know if you need any help during the process!
Hi Fruiz, the js_composer.zip is now on Newspaper-tf > code > other_plugins >
js_composer.zip
Thank you!
Hi,
What you can do is use tagdiv Composer, edit the header and on the tablet, where you want the mobile menu to be displayed, not the desktop one, hide the current menu – https://i.imgur.com/JsdDBGu.png and add the mobile menu element https://i.imgur.com/PoNW2hd.png (this must be hidden on the viewports that you do not want to display, such as the desktop) https://i.imgur.com/wuLyNXM.png
Thank you!
Hi,
Newspaper theme has a responsive version, a mobile page (a separate page only for mobile) and a plugin tagDiv mobile theme (this will not display the sidebar and the content for pages should be set in the mobile editor).
However, because you are using widgets for the sidebar, the above solution will not work. If you want to have a different order of the elements in the sidebar widget, what you can do is:
– create a new widget that will be displayed only for mobile on hompages (hide it from the css tab so that it is not visible on other viewports)
– use the mobile page, here you can replace the current widget with the one you want, or you can remove the widget and add the elements with the composer tagdiv in the desired order
Thank you!
Hi,
The sidebar from your homepage is set using tagDiv Composer. If you check the provided images, you’ll see that the first should be the social counter, then ad block and editorial block, but in your homepage screenhost, you have an ad and popular video, which are different blocks.
Please go to Newsmag > theme panel > template settings > blog and post templates -> https://i.imgur.com/VLbGFey.png
If you want we can take a loo, for this please contact us via email at contact@tagdiv.com and provide temporary wp-admin access to the website.
Thank you!
Hello, according to your documentation it should be a Newspaper-tf/plugins/js_composer.zip file when downloading the last version of the theme files but the zip file doesn’t exist. I can update the plugin from the link you provided in this forum but I don’t want to risk my website using a non tested version of WpBakery Builder.
Hello Tagdiv,
I’m currently running PHP 7.4.33 because updating to a newer version results in a critical error. My web host identified the issue as being related to two Tagdiv plugins — I believe Tagdiv Cloud Library and Tagdiv Composer.
Could you advise on how I can resolve this so I can safely update PHP? I got an error log, if that helps
Url:https://www.livinginashoebox.com
Hi Calin, this is what I get in DivComposer
If I click “Create Mobile Page” it create me another Home Page. Is it correct? Is this when you talk about mobile?
If I click on the widget i have this menu on the left, but if click on the mobile icon and i made a change this change is for all the version of the homepage also desktop not only the mobile
Hi,
That space is coming from an ad , when you scroll down and up after a few seconds, the ad will be displayed. https://i.imgur.com/a5qIf6p.png
If you want to change the widget position, what you can do is to use tagDiv Composer and use the settings for row and column on the mobile version to reverse the columns inside the row. By doing this, you can make the sidebar display first https://tagdiv.com/flexibility-rows-columns-newspaper-theme/
Thank you!
Hello,
The zones refer to the header/content/footer zone.
Most of the time, the problem is from a shortcode that is not compatible with our theme; therefore, after you set it with tagDiv Composer and save the page, the next time you try to edit it, you’ll get that error. The simplest and fastest way to resolve it is to use a page/template revision – https://wordpress.com/support/page-post-revisions/
Also, please check our guide from here at point 5 -> https://forum.tagdiv.com/tagdiv-composer-not-working/ also after trying the steps from our guide you do not get any good results, you can send us an email at contact@tagdiv.com and provide wp-admin login, as well as cPanel and credentials. We will take a look. Include a link to this topic in the email.
Thank you!
