- TutorialstagDiv Social Counter Tutorial
Hi,
It seems there may be a misunderstanding here. Perhaps you’ve previously used a different theme that handled things a certain way, and now you’re expecting all themes to behave similarly. If that’s the case, I’m sorry to disappoint you.
As I mentioned before, when you install a demo, only the content and layout specific to that demo are included. For example, if you want to set up a shop, you’ll need to configure it manually using tagDiv Composer and tagDiv Shop (please make sure the plugin is installed, as I mentioned earlier).
Once the necessary plugin is active, you can use tagDiv Composer to build your shop pages. There are also pre-designed templates available, which you can easily import from the Cloud Library:
https://demo.tagdiv.com/select_demo/newspaper-prebuilt-websites/?demo-type=shop
To clarify again: when you add new functionality like a shop that wasn’t part of the originally installed demo, the layout for those new features won’t exist by default. You’ll need to create or import the layout manually.
Thank you!
Hi,
You can contact us privately via email at contact@tagdiv.com if you’d like to share your credentials. Please do not post them on the forum.
Regarding your issue:
The problem is that you’ve edited the single post template each time when you think you add the article content, as shown here: https://i.imgur.com/LeuIZit.jpeg also, the dynamic post content element was replace with a Text with Title element. This element displays static content and does not automatically show each article’s content.
To display content dynamically for each post, you need to use the Post Content element instead: https://i.imgur.com/hldTlpY.png (I set it back)
If I understand correctly, you created the articles, then opened each article individually, edited the cloud template using tagDiv Composer, and manually changed the text inside the fixed text block. That’s the root of the issue.
There are currently 24 edits on your template, and 22 of them are changes to the text inside the static Text with Title element.
This means you’ve essentially created articles with only a title, but added the content directly in the template, not in the article itself https://i.imgur.com/U6qR7mt.png
Articles should be created properly in the post editor, like this example:
https://www.pomeranian.dk/wp-admin/post.php?post=64&action=edit
frontend view: https://www.pomeranian.dk/index.php/2025/06/26/mobile-marketing-is-said-to-be-the-future-of-e-commerce/
Also, please make sure you’re using the global template from the panel: https://i.imgur.com/vHbkSTS.png use an individual template only if you want a custom layout for a specific article.
Thank you!
Hello,
When you install a demo, only the pages, the templates and elements included in that specific demo will use its layout and design. If you create new pages or add additional features, such as a shop (using WooCommerce), forum pages, or other content, these will not automatically have a template applied, as they are considered custom additions.
However, there’s no need to worry! The theme allows you to fully customize templates to achieve the layout you want. You can do this using tagDiv Composer along with Cloud Templates.
For creating and customizing shop pages specifically, you’ll need to install the tagDiv Shop plugin. You can do this by going to Newspaper > Plugins in your WordPress dashboard. Once installed, you’ll be able to create and edit shop templates using the theme builder.
Thank you for your understanding!
Hi,
I believe there’s a misunderstanding. tagDiv Composer is a page builder—you can use it to create pages and cloud templates. In your case, you can create templates for articles, but not the articles themselves. What it allows is customizing the layout and elements that your articles will use.
Once the template is ready, you’ll use the WordPress editor to actually create and write the articles. https://i.imgur.com/WA5GrgO.png https://forum.tagdiv.com/design-post-pages-using-cloud-library-templates/
Hi,
In tdc_history, all actions performed using tagDiv Composer are stored for every page and cloud template where you’ve used the Composer (https://i.imgur.com/0NbEObD.png). This allows you to use the Undo and Redo options → https://i.imgur.com/p9074lE.jpg, and also restore backups directly from the panel → https://i.imgur.com/QqX33GE.png. What you can do is to disable the Undo and Redo option – https://i.imgur.com/DPwPQHe.png and delete and reduce the number of backups in the theme panel https://i.imgur.com/JZnZpiN.png (the theme panel backups when it is disabled offers the option to delete all backups, after that can be enabled back to have a theme panel backup).
I hope this will help you!
Hi,
You can edit a page using tagDiv Composer and import that section from cloud – https://i.imgur.com/i0u6vYv.png. That effect is made using CSS on elements with CSS td-kattmar-module-bg https://i.imgur.com/ZiHvVxf.png – https://i.imgur.com/iddJuZ8.png
Thank you!
The attachment cloud template shows the ‘description’ field, inexplicably.
How can this be fixed or modified to show the ‘caption’ field (which is what everyone uses!). It seems that Tagdiv is incredibly slow on fixing this as the OP asked for this almost a year ago.
Hi,
Is that plugin providing a shortcode? If so, then use that shortcode and set it using tagDiv Composer on pages and cloud template in column text, in text zone, here – https://imgur.com/DSSni9j
Thank you!
If I update the theme through the WordPress dashboard, will settings such as the cloud templates, menu, etc, remain unchanged?
Hi,
You can use the Flex Block and customize it to fit your layout. Alternatively, you can use the Module Builder to create your own module, or simply import a block you like from the Cloud Library and add it to your sidebar.
Regarding filters:
If the block is placed on a category page and you want to display posts from that category, use the special filters (https://i.imgur.com/YsQSGx4.png).
If it’s on a single post template, make sure to use the single post special filter.
If you’d like to show posts from a specific category across all templates, just select that category from the dropdown menu.
Thank you!
Buna,
Am inteles ce doriti sa obtineti, insa este posibil sa nu ma fi exprimat suficient de clar.
In prezent, atunci cand folositi tema Newspaper si deschideti un articol, prima imagine apare de doua ori (https://i.imgur.com/A8ub9nk.png). Acest lucru se intampla deoarece template-ul folosit afiseaza automat imaginea setata ca featured image, iar aceeasi imagine este inclusa si ca prim element in continutul articolului.
O solutie permanenta, care se aplica tuturor articolelor, este folosirea unui single post template din tagDiv Cloud Library, din care sa eliminati elementul de featured image. In acest fel, articolul va ramane neschimbat ca structura si continut, doar ca nu se va mai incarca si afisa acea imagine duplicata. https://i.imgur.com/UHQiuld.png https://i.imgur.com/212sYqY.png
O alta varianta este ascunderea imaginii din continut folosind un cod CSS. Totusi, aceasta optiune o ascunde doar vizual imaginea va continua sa fie incarcata in pagina, ceea ce poate afecta performanta.
Sper ca am reusit sa explic cat mai clar situatia.
Multumesc!
Hi,
What you can do is to try to exclude the js code for pagination on CloudFlare. Try to exclude those files: tdLoopAjax.js and tagdiv_theme.min.js
I hope this will help you!
All of my posts now have a “blog” look to them with a white background and no widgets, when they used to have widgets and a black background. I have not edited anything in days and now all of sudden while going through my site, the posts look very different. I’m thinking this is just a template change, but I’m not sure why it happened in the first place or exactly what to change to go back.
When I used to change the content in a widget on a post, I would go to “Cloud templates>Single templates> Revenant Single Template> Edit with TD Composer”. When I go there now, it still shows the proper widgets with the black background.
Can you help with:
– I’m not sure what to do next as I’m now nervous about messing the whole thing up.
– Is there any way to find out how this happened and maybe just go back to an old setting? Kind of like restoring a backup.
Thanks,
Don
My site is served through CloudFlare. For several months, the “Load More” (or, alternatively, infinite load–any function that is designed to load additional posts) on the main page has been broken. You get a spinning wheel. However, if you turn off CloudFlare (or put it into Developer Mode), the problem immediately goes away. Is there a way to avoid this problem? Thanks.
Hi,
Please replace the current tagdiv composer plugin and tagdiv option plugin with those from below:
– https://cdn.tagdiv.com/wp-content/uploads/2025/05/td-composer.zip
– https://cdn.tagdiv.com/wp-content/uploads/2025/07/td-cloud-library.zip
I hope this will resolve the problem.
Thank you!
Hi ahmedkhaled912,
For the situation with 404, please make sure that all settings are set as in our guide firm here – https://forum.tagdiv.com/requirements-for-newspaper/. In case the error persists, please contact us via email at contact@tagdiv.com and provide a temporary wp-admin and cPanel access to investigate and resolve the problem.
This Notice: Function _load_textdomain_just_in_time was called incorrectly…. Please get the plugin from here – https://cdn.tagdiv.com/wp-content/uploads/2025/07/td-cloud-library.zip. This should be used only with Newspaper v12.7.1 and will resolve that notice.
Let me know the results!
Hi Qplus Account,
This Notice: Function _load_textdomain_just_in_time was called incorrectly…. Please get the plugin from here – https://cdn.tagdiv.com/wp-content/uploads/2025/07/td-cloud-library.zip. This should be used only with Newspaper v12.7.1 and will resolve that notice.
Let me know the results!
Hi,
Usually, when this happens, it is used a cache that does not have the option to deliver a separate mobile cache version. Also, sometimes it can be Cloudflare cache, if this is used (the free version does not have a separate cache per viewport).
The simplest way to resolve the problem is to disable the tagDiv Mobile theme plugin, or in case the amp plugin is used to be set to be used only on amp version https://i.imgur.com/mn3AIzp.png also, make sure that the amp redirect is disabled https://i.imgur.com/P5XcUxA.png
Thank you!
Hi TagDiv Support,
I’m using the latest version of the Newspaper theme (v12) along with the TagDiv Composer plugin. I’m currently encountering a critical issue: whenever I try to edit any page using TagDiv Composer, I get a 404 error.
Here’s what I’ve done so far to troubleshoot:
Updated WordPress, the Newspaper theme, and all plugins to the latest versions
Resaved permalink settings
Cleared all cache (browser, site, CDN)
Deactivated all other plugins to check for conflicts
Verified that the pages exist and are using the correct templates
I also enabled debugging and noticed this warning in the logs:
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the “td-cloud-library” domain was triggered too early.
(From: /wp-includes/functions.php on line 6121)
This may point to an issue with how the theme or plugin handles translation loading, possibly affecting the TagDiv Composer’s ability to load edit URLs correctly.
Can you please advise:
Is this a known issue in the current version?
Is there a patch or update available to resolve this?
Are there any specific server settings or requirements (e.g., rewrite rules, PHP version) that I should verify?
Looking forward to your help as this is preventing us from editing content on the site.
Hi,
That is an extra class and you can set the CSS for that class in theme panel > custom code> custom CSS, or in live CSS or directly in page or cloud template in a raw CSS element.
Thank you!
Hi,
Is there a way to increase a number of ad slots in Single Post Content for Cloud Library Post Templates?
My articles are pretty long so there is a lot of unused space between content that could be converted into profit.
Currently I am using Adsense in-content auto ads to fill up the articles but I’s preffer more control over it.
All plugins are deactivated (except tagDiv plugins) and after replacing td composer and td cloud library I am getting this:
Logo
VESTI
BTS PODCAST
KONCERTI I DOGAĐAJI
RECENZIJE
RAZBIJANJE TIŠINE
O NAMA
More
Fatal error: Uncaught ValueError: Unknown format specifier ” ” in /home/milosbts/public_html/wp-content/plugins/td-cloud-library/parts/tdb-comments.php:177 Stack trace: #0 /home/milosbts/public_html/wp-content/plugins/td-cloud-library/parts/tdb-comments.php(177): sprintf() #1 /home/milosbts/public_html/wp-includes/comment-template.php(1629): require(‘/home/milosbts/…’) #2 /home/milosbts/public_html/wp-content/plugins/td-cloud-library/state/single/tdb_state_single.php(2110): comments_template() #3 /home/milosbts/public_html/wp-content/plugins/td-cloud-library/shortcodes/single/tdb_single_comments.php(470): tdb_state_single->{closure}() #4 /home/milosbts/public_html/wp-content/plugins/td-cloud-library/shortcodes/single/tdb_single_comments.php(470): Closure->__invoke() #5 /home/milosbts/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): tdb_single_comments->render() #6 /home/milosbts/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function() #7 [internal function]: do_shortcode_tag() #8 /home/milosbts/public_html/wp-includes/shortcodes.php(273): preg_replace_callback() #9 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode() #10 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/shortcodes/vc_column.php(440): tdc_composer_block->do_shortcode() #11 /home/milosbts/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): vc_column->render() #12 /home/milosbts/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function() #13 [internal function]: do_shortcode_tag() #14 /home/milosbts/public_html/wp-includes/shortcodes.php(273): preg_replace_callback() #15 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode() #16 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/shortcodes/vc_row.php(1204): tdc_composer_block->do_shortcode() #17 /home/milosbts/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): vc_row->render() #18 /home/milosbts/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function() #19 [internal function]: do_shortcode_tag() #20 /home/milosbts/public_html/wp-includes/shortcodes.php(273): preg_replace_callback() #21 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode() #22 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/shortcodes/tdc_zone.php(771): tdc_composer_block->do_shortcode() #23 /home/milosbts/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): tdc_zone->render() #24 /home/milosbts/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function() #25 [internal function]: do_shortcode_tag() #26 /home/milosbts/public_html/wp-includes/shortcodes.php(273): preg_replace_callback() #27 /home/milosbts/public_html/wp-includes/class-wp-hook.php(324): do_shortcode() #28 /home/milosbts/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters() #29 /home/milosbts/public_html/wp-content/plugins/td-cloud-library/wp_templates/tdb_view_single.php(189): apply_filters() #30 /home/milosbts/public_html/wp-includes/template-loader.php(106): include(‘/home/milosbts/…’) #31 /home/milosbts/public_html/wp-blog-header.php(19): require_once(‘/home/milosbts/…’) #32 /home/milosbts/public_html/index.php(17): require(‘/home/milosbts/…’) #33 {main} thrown in /home/milosbts/public_html/wp-content/plugins/td-cloud-library/parts/tdb-comments.php on line 177
There has been a critical error on this website.
As soon as I move back from any php 8.x version to php 7.4 the error message is gone.
Hi,
Normally, with the provided version of tagDiv Cloud Library, the notice _load_textdomain_just_in_time should no longer be displayed.
Also, the fatal error “Fatal error: Uncaught ValueErro” is coming from the comment element, do you use any extra plugins for comments?
Can you please replace the tagDiv Composer too with the one from here – https://cdn.tagdiv.com/wp-content/uploads/2025/05/td-composer.zip
And please make a test using only tagDiv plugins to see if the problems persist.
Thank you!
Okay Calin. Thanks for your insights. I will try your recommendations. It will take a while I think, but I am curious if things will improve.
Now I only need to figure out how to make a staging site. Never done that before, but I will work it out.
I also learned there are double query’s made (sometimes 1200) so that can not be good. The main plugins (beside your theme) contributing to this are WPMF (+cloud addon+gallery addon), Rank Math and FS-Poster. I will get back to you if I have some results Calain. Thanks for pointing me in a direction to investigate further.
I have copied files from zip and this is the new error message:
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the media-library-organizer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/milosbts/public_html/wp-includes/functions.php on line 6121
Logo
VESTI
BTS PODCAST
KONCERTI I DOGAĐAJI
RECENZIJE
RAZBIJANJE TIŠINE
O NAMA
More
Fatal error: Uncaught ValueError: Unknown format specifier ” ” in /home/milosbts/public_html/wp-content/plugins/td-cloud-library/parts/tdb-comments.php:177 Stack trace: #0 /home/milosbts/public_html/wp-content/plugins/td-cloud-library/parts/tdb-comments.php(177): sprintf() #1 /home/milosbts/public_html/wp-includes/comment-template.php(1629): require(‘/home/milosbts/…’) #2 /home/milosbts/public_html/wp-content/plugins/td-cloud-library/state/single/tdb_state_single.php(2110): comments_template() #3 /home/milosbts/public_html/wp-content/plugins/td-cloud-library/shortcodes/single/tdb_single_comments.php(470): tdb_state_single->{closure}() #4 /home/milosbts/public_html/wp-content/plugins/td-cloud-library/shortcodes/single/tdb_single_comments.php(470): Closure->__invoke() #5 /home/milosbts/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): tdb_single_comments->render() #6 /home/milosbts/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function() #7 [internal function]: do_shortcode_tag() #8 /home/milosbts/public_html/wp-includes/shortcodes.php(273): preg_replace_callback() #9 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode() #10 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/shortcodes/vc_column.php(440): tdc_composer_block->do_shortcode() #11 /home/milosbts/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): vc_column->render() #12 /home/milosbts/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function() #13 [internal function]: do_shortcode_tag() #14 /home/milosbts/public_html/wp-includes/shortcodes.php(273): preg_replace_callback() #15 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode() #16 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/shortcodes/vc_row.php(1204): tdc_composer_block->do_shortcode() #17 /home/milosbts/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): vc_row->render() #18 /home/milosbts/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function() #19 [internal function]: do_shortcode_tag() #20 /home/milosbts/public_html/wp-includes/shortcodes.php(273): preg_replace_callback() #21 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/tdc_composer_block.php(222): do_shortcode() #22 /home/milosbts/public_html/wp-content/plugins/td-composer/includes/shortcodes/tdc_zone.php(771): tdc_composer_block->do_shortcode() #23 /home/milosbts/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_global_blocks.php(27): tdc_zone->render() #24 /home/milosbts/public_html/wp-includes/shortcodes.php(434): td_global_blocks::proxy_function() #25 [internal function]: do_shortcode_tag() #26 /home/milosbts/public_html/wp-includes/shortcodes.php(273): preg_replace_callback() #27 /home/milosbts/public_html/wp-includes/class-wp-hook.php(324): do_shortcode() #28 /home/milosbts/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters() #29 /home/milosbts/public_html/wp-content/plugins/td-cloud-library/wp_templates/tdb_view_single.php(189): apply_filters() #30 /home/milosbts/public_html/wp-includes/template-loader.php(106): include(‘/home/milosbts/…’) #31 /home/milosbts/public_html/wp-blog-header.php(19): require_once(‘/home/milosbts/…’) #32 /home/milosbts/public_html/index.php(17): require(‘/home/milosbts/…’) #33 {main} thrown in /home/milosbts/public_html/wp-content/plugins/td-cloud-library/parts/tdb-comments.php on line 177
There has been a critical error on this website.
Line 177 looks the same as the previous error:
esc_attr( sprintf( __td( 'Logged in as %s. Edit your profile.' , TD_THEME_NAME), $user_identity ) ),
