- ApiPractical example – How to add a new Block and Module
- Apitd_api_block::delete
- Apitd_api_block::update_key
- Apitd_api_block::update
- Apitd_api_block::add
- ApiAPI – Blocks – Introduction
- Apitd_api_thumb::update_key
- Apitd_api_thumb::update
- Apitd_api_thumb::add
- ApiAPI – Thumbnail – Introduction
- Apitd_api_category_top_posts_style::update_key
- Apitd_api_category_top_posts_style::update
- Apitd_api_category_top_posts_style::add
- ApiAPI – Category top section style – Introduction
- Apitd_api_module::update_key
- Apitd_api_module::update
- Apitd_api_module::add
- ApiAPI – Modules – Introduction
- ApiUsing the Theme API in plugins
- ApiThe Theme API
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
Hello,
I am writing to ask for help with configuring post timestamps on my website. Currently, when I create scheduled posts, the displayed time shows the date I created the draft rather than the actual publication date.
The Issue:
* I work with scheduled content that is created in advance
* Posts are set to publish at future dates via cron jobs
* However, the timestamp displays the draft creation date instead of the scheduled publication date
* This creates confusion for readers about when content was actually published
What I Need:
I would like example code to modify the tagdiv block so that it displays the publication date/time instead of the creation date for scheduled posts. While I can implement custom code on my website, I believe this should be a standard dropdown option in the theme settings or the block element itself.
Could someone please provide guidance or sample code for this modification?
Thank you for your assistance.
Best regards,
evropea
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,
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
After some investigation, it appears that certain elements available in the previous version I was using are no longer present in the latest release.
For example, in the earlier version, there was an element called “Big Grid 12”, which I can’t find in the new version. Instead, I see a similar element named “Big Grid Flex 4”.
As a result, when I open the webpage, instead of the element rendering correctly, I only see the shortcode because the template no longer recognizes the old element.
Example:
[td_block_big_grid_12 category_id=»55473″ sort=»»]
[td_block_2 category_id=»» limit=»6″ header_color=»#000000″ td_ajax_filter_ids=»» td_filter_default_txt=»All» ajax_pagination=»next_prev» td_ajax_filter_type=»» custom_title=»ÚLTIMAS NOTICIAS» custom_url=»últimas_noticias» post_ids=»-65255,-21788, -61097, -101029, -56563″][td_block_1 limit=»5″ custom_title=»RECUPERACIÓN» td_ajax_filter_type=»» td_ajax_filter_ids=»» td_filter_default_txt=»» ajax_pagination=»next_prev» sort=»modified_date» header_color=»#000000″ category_id=»1232″ custom_url=»recuperacion»]
Is there a way to continue using these previous elements, or is the only option to rebuild my website using the new ones?
Thank you.
Hi,
You can use the offset and filter settings from blocks – https://forum.tagdiv.com/flex-block-settings-guide/ or you can use the unique article option from the page https://forum.tagdiv.com/unique-articles/
Thank you!
Hi,
Please try accessing your website in incognito/private mode, as an ad blocker in your browser or even your antivirus software might be preventing the banners from showing.
Also, could you please share a link to your website so I can check on my end and see if the banners are displaying correctly?
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!
Yes, I did so but as you can see on my original post, It didn’t work. After upgrading both the theme and plugins, It changed the UI of my website and on top of that, plugins were disabled, blocking me to enable them.
Hi,
Please try this custom css:
.td-header-desktop-wrap {
display: block;
}
.td-header-desktop-wrap .tdc_zone .tdc-row {
display: none;
}
.td-header-desktop-wrap .tdc_zone #tdi_17.tdc-row {
display: block;
}
Can the CSS be set in the theme panel > custom code> advance css > phone – https://i.imgur.com/r2gFvDQ.png
Hi,
I have a suggestion for this: Assign the products to a specific category or tag, and then filter the block by that category or tag. This way, only the desired articles will be displayed. To mark an article as “on sale,” you need to reduce its original price. However, since there’s no built-in filter for sale items, using a category or tag is the best approach to identify and display them.
Thank you!
Hi,
If this situation is on the homepage, then use tagDiv Composer to edit the page, select the block and check the filter tab and there select the category for that block.
Thank you!
Hi,
I am not facing any theme-related problems as such, but I did encounter an issue (actually, I don’t even know if this is even an issue or not). I installed Termly a while back. But when I enable the autoblocker, featured images don’t display (woocommerce and posts).Is this normal? Is this how it is supposed to work? I browsed the web but found no answers. So am asking here.
I want to show products with sale only in woo products block.
(DISCOUNT PAGE)
Hi,
In case that you want to display some blocks inside the article you can try this guide:
How to insert a block inside the content of a post
Thank you!
Hi,
I just checked your website, and the banner is there – https://i.imgur.com/aCSIeyT.png. Just make sure that you do not have any ad blockers installed, because those will block the ads from being displayed for you.
Thank you!
Hi,
When a file is required from the child theme and is also related to ACF (Advanced Custom Fields), which is an external plugin, this indicates a custom implementation. In this case, it appears to be connected to a custom plugin or custom code specifically created for your website.
The file in question, acf-blocks-loader.php, is referenced using a path set within your child theme. However, this file does not exist in our theme, which confirms that it was custom developed likely by someone who previously worked on your site.
Thank you!
Hi,
I want to write articles using some of the theme blocks. Are these blocks available for use in posts?
From what I see, they can only be used in pages. How can I use them in posts?
please How to create a mega menu like Blockchain pro
Hi Calin,
Thank you for your response. The error did not resolve after following your suggestions. These are the steps I took.
– I verified I am using the latest Newspaper theme 12.7.1.
– I removed the child theme folder from wp-content/themes
– I refreshed the themes page in wp-admin to verify the theme was gone.
– I created Newspaper-child.zip from the theme package.
– I installed Newspaper-child.zip by uploading it into the WordPress admin panel. – WordPress said the installation was successful.
– I went back to the themes page and tried to preview the child theme.
– The same error showed.
2025/08/08 21:18:37 [error] 118#118: *1710 FastCGI sent in stderr: "PHP message: PHP Warning: require_once(/www/kinsta/public/mysite/wp-content/themes/Newspaper-child/blocks/acf-blocks-loader.php): Failed to open stream: No such file or directory in /www/kinsta/public/mysite/wp-content/themes/Newspaper/functions.php on line 644;
It is still looking for the /blocks/ folder in the child theme:
PHP message: PHP Fatal error: Uncaught Error: Failed opening required '/www/kinsta/public/mysite/wp-content/themes/Newspaper-child/blocks/acf-blocks-loader.php' (include_path='.:/usr/share/php') in /www/kinsta/public/mysite/wp-content/themes/Newspaper/functions.php:644
Thank you for any help you can provide.
Hi,
We received your email and it appears that this notice can be removed if the debug is set to false https://forum.tagdiv.com/requirements-for-newspaper/. It appears to be related to some settings from a block on the homepage, but for the moment, we haven’t identified it. We’ll reply via email when is done.
Thank yoU!
Hi,
How can I add a shortcode to a slider for the homepage? [soliloquy id=””]
Tried various things (text block, Raw HTML) but that didnt work.
Thanks
Hi,
The number of modules per row and the number of modules that should be displayed can be edited using tagDiv Composer, edit the homepage, select that section, and check in the general tab the post title length, the excerpt length, and the limit post number. https://i.imgur.com/XHxJUCg.png – https://forum.tagdiv.com/flex-block-settings-guide/
Thank you!
Hi,
The notification you are receiving means that the theme cannot reach our server and verify the key. The theme performs a check to verify the validity of the key and tries to connect to our database. If something interferes with this check, the theme will display that message. The check is made when accessing the demo install panel, the theme updates panel, or the license panel.
This kind of issue can be caused by plugin conflicts, or conflicts with various security/firewall settings from plugins or from the hosting, or from website restrictions set by the hosting. If something blocks the theme from verifying the key, the respective message is displayed and the theme will have limitations, unfortunately.
The first thing to do would be to check with the hosting if there are any restrictions in place, which would not allow the theme to reach our server and verify the key. I will take a look as well, for this please contact us via email at contact@tagdiv.com, I will need wp-admin login for the respective website and the license key, and also cPanel or a similar server manager. Let me know.
Thanks,
