No search results were found in Documentation!
Hi,
The tagDiv Composer is a builder, you can create with it pages and cloud template and those cloud template are for posts, authors, categories, cpts … but the tagDiv Composer can not be used to create articles, for this it should be use the WordPress editor.
Thank you!
Hi,
1. This iwll not be easy and I do not know for sure if is working, but I think it can be done like this:
– Listing Owners: Give them a new role like listing_owner.
– Commentators: Keep as subscriber.
Optional: Add a user meta (user_type) for extra filtering.
2. For this you need to edit the theme files and set to trigger your modal
– wp-content/plugins/td-cloud-library/parts/tdb-comments.php
– wp-content/plugins/td-cloud-library/parts/tdb-login-modal.php
Thank you!
Hi,
For that you need to use a single post template from cloud, edit it using tagDiv Composer and set the modified date – https://i.imgur.com/OhJIA4d.png – https://i.imgur.com/xhAASna.png – https://i.imgur.com/SRxWlvv.png
Thank you!
Hi,
First please make sure that you use the last theme version 12.7.1 and last WordPress version, after that please do a test using only tagDiv plugins to see if the problems with “When we try to upload a post we get the following error:” is still persisting, is possible to be a plugin conflict.
The “Notice: Function _load_textdomain_just_in_time was called incorrectly. Tra …” is just a notice, this will note affect the website for logged users or visitators.
When you see shortcodes like this [tdb_header_weather icon_color=”#ffffff” …] it is because one of the theme plugins taht provides that shortcode is disable and you need to install/enabled the tagdiv plugins (can be tagDiv Composer, tagDiv Cloud Library …)
Thank you!
Hi TagDiv Team,
We are experiencing a serious issue on our website (https://nowinsa.co.za).
When we try to upload a post we get the following error:
“The editor has encountered an unexpected error.”
TypeError: Cannot read properties of null (reading ‘toString’)
at pL (https://nowinsa.co.za/wp-includes/js/dist/components.min.js?ver=336a01176fa8097fbf37:33:143126)
at n (https://nowinsa.co.za/wp-includes/js/dist/components.min.js?ver=336a01176fa8097fbf37:33:146597)
at t.get (https://nowinsa.co.za/wp-includes/js/dist/components.min.js?ver=336a01176fa8097fbf37:33:146758)
at t.render (https://nowinsa.co.za/wp-includes/js/dist/components.min.js?ver=336a01176fa8097fbf37:33:155778)
at br (https://nowinsa.co.za/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1.1:10:59368)
at yr (https://nowinsa.co.za/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1.1:10:59167)
at Qs (https://nowinsa.co.za/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1.1:10:121084)
at wl (https://nowinsa.co.za/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1.1:10:88341)
at bl (https://nowinsa.co.za/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1.1:10:88269)
at yl (https://nowinsa.co.za/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1.1:10:88132)
Issue:
We’re getting the following error notice when debug mode is enabled:
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the td-cloud-library 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. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6121
This warning seems to break frontend shortcodes and prevent post uploads from working correctly. For example, instead of rendering, we see raw shortcodes like:
[tdb_header_weather icon_color=”#ffffff” …]
What we’ve tried:
-Enabled debug mode via wp-config.php to identify the issue
-Confirmed the warning disappears if we hide debug output (WP_DEBUG_DISPLAY set to false)
-Verified that the problem comes from td-cloud-library or the Composer plugin, as switching themes or disabling TagDiv plugins resolves it
-We treid to backdate both WordPress and theme Theme, and nothing seems to work.
Hello,
We are seeing this PHP warning at the rate of about 3/second:
PHP Warning: A non-numeric value encountered in /www/wp-content/plugins/td-cloud-library/shortcodes/single/tdb_single_author_box.php on line 395;
This is making our log files largely useless because we have to filter this out constantly. Not to mention putting unnecessary CPU work on our server to log all of these.
Any idea how we can make these stop?
Hi, I imported Gallery Images – Nature Love by tagDiv available in Cloud Library, I placed it in a new page, but the images that can be used or displayed are only 10 photos, I don’t know how to increase the number of photos more than 10, hoping for your help.
https://drive.google.com/file/d/1BgtFNAfDRT9gCBQM9pxAiWNAhqlMsK-u/view?usp=sharing
Regards.
Hi,
There is no newspaper-core.zip, I think there is a misunderstanding.
Did you manage to install the theme? – https://forum.tagdiv.com/install-via-wordpress/ (make sure you install only the theme zip inside the package you have downloaded from the themeforest account https://help.market.envato.com/hc/en-us/articles/202821510-Theme-is-missing-the-style-css-stylesheet-error)
After the theme is installed you need to go to Newspaper > Welcome section and you can install from there the tagDiv Composer and tagDiv Cloud Library plugins – https://i.imgur.com/LyI1bNb.png after that you need to activate the theme – https://forum.tagdiv.com/newspaper-6-how-to-activate-the-theme/ and only after that you can install the demo you mentioned – https://forum.tagdiv.com/installing-demos/
Also, all theme plugins are provided under Newspaper > Plugins tab – https://i.imgur.com/6NoXVCc.png
Thank you!
Hi,
Ok, it appears that the website is blocked for a part of countries, so I us a VPN to check it out.
Now, I see that on homepage you have a different header, so I believe that maybe one of the theme plugins is no longer installed? Please go to Newspaper plugins and make sure that you have installed and activate the tagDiv Composer, tagDiv Cloud Library and tagDiv Standard Pack (I believe that you do not have the standard pack that brings the old templates).
Thank you!
👋 Hello tagDiv team & community,
I’m currently building my personal digital magazine site using Newspaper Theme 12 and I’ve run into a strange layout issue that I can’t seem to resolve on my own. I’d really appreciate any help or insight you can offer!
🔍 The Issue:
The footer and content on post pages appears misaligned to the left side — but only on:
Category pages
Single post pages
It renders perfectly fine and centered on:
The homepage
Custom static pages (like “Privacy Policy” “Join Syaz+,” etc.)
🧪 What I’ve Tried:
Zeroed out margin/padding via tagDiv Composer
Checked all footer row/column settings (full width, centered content, etc.)
Applied custom CSS (example below), but this affects global layout and causes issues elsewhere
Inspected with dev tools — the td-container inside .td-footer-wrapper seems to shift left on posts/categories
You may view the issues when visiting my site on an actual mobile phone, weird thing is: the issues doesn’t show up on the tagDiv Composer’s mobile view.
🌐 My Website:
https://syaz.co
⚙️ Theme Version & Setup:
Theme: Newspaper 12
Composer: tagDiv Composer
Footer: Custom Footer Template from tagDiv Cloud Library
No caching/minification plugins running while debugging
💡 Desired Outcome:
I’d like the footer to remain centered consistently across all page types, including:
Category archives
Single blog posts
🛠️ Optional CSS I tried (not reliable):
body.category .td-footer-wrapper .td-container,
body.single-post .td-footer-wrapper .td-container {
margin-left: auto;
margin-right: auto;
text-align: center;
}
🙏 Any help is appreciated!
I’m hoping someone might’ve encountered this before — or if tagDiv devs could shed some light on what might be causing this layout behavior across different templates.
Thanks in advance,
Syazwan Razali
Hi Calin,
thanks for looking into this. A few additional details from our end:
1. We’ve used about ten different plugins that triggered the same “\_load\_textdomain\_just\_in\_time was called too early” notice, and they’ve all released fixes since WP 6.7 (November 12, 2024). The only one still spamming our logs is td-cloud-library.
2. To prove it’s definitely td-cloud-library, we spun up a fresh install with only the Newspaper theme plus tagDiv Composer and td-cloud-library active. With WP\_DEBUG (and/or WP\_DEBUG\_LOG) enabled, the notice appears—and disabling td-cloud-library alone removes it. Steps to reproduce:
* Install Newspaper theme + tagDiv Composer + tagDiv Cloud Library
* Add to wp-config.php:
`
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_DISPLAY’, true);
define(‘WP_DEBUG_LOG’, true);
`
* Visit any page and watch the notice flood the debug log.
3. We hunted down why that notice won’t go away under WP 6.7+. Here’s what we tried:
* Searched every PHP file in td-cloud-library for load\_plugin\_textdomain(…) calls—none exist.
* Made a small must-use plugin that removes WP’s JIT filters on “plugins\_loaded” and force-loads the text domain on init. But it still fails because WP 6.7+ attaches _load_textdomain_just_in_time so early that any __(…, 'td-cloud-library') call in the plugin’s global scope immediately triggers the notice—before our MU-plugin runs.
* In other words, as soon as the first translation function fires (e.g. __('…', 'td-cloud-library')), WP already tried and threw the warning.
What needs to happen: All translation function calls (__(), _e(), esc_html__(), etc.) in td-cloud-library must be moved out of the global scope so they don’t run before load_plugin_textdomain('td-cloud-library', …) fires on or after init. Until every translation call is wrapped in a callback (or otherwise deferred until after the domain is registered), that notice will keep spamming logs.
Hope this helps pinpoint the fix. Cheers!
Dear TagDiv Support Team,
I am writing to inquire about the high number of database queries, specifically duplicate queries, generated by your plugins tag div composer, cloud library (We have disable tag div standard pack for these problem).
Through recent performance debugging and analysis of our query logs, we have identified that a significant portion of our site’s database load originates from these plugins. This excessive query count is directly impacting our website’s overall performance and database responsiveness, leading to slowdowns and potential issues with critical background processes, including WordPress cron jobs (which sometimes fail to save their event lists due to database contention).
Could you please provide guidance or suggest methods for reducing the number of database queries generated by your plugins? We are looking for best practices or configurations that can help optimize query usage and improve performance without compromising essential theme functionalities.
Thank you for your time and assistance.
Antonio Ungaro
http://www.sport24h.it
It doesn’t seem to be a theme issue.
I recreated the Newspaper parent theme and child theme folders as ‘old’ themes.
And I still get the 502 error.
And the plugins I use are as follows:
classic-editor
td-cloud-library
td-composer
td-social-counter
wordpress-seo(yoast seo)
wp-super-cache
Hi Team,
I am facing this issue on my website maverickmefoundation.com. Please help. I have already updated the theme and the plugins, but the error message is not going away. I have also flushed the cache files…
Thank you.
Ritu
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the td-cloud-library 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 /var/www/wp-includes/functions.php on line 6121
Hi,
The tagDiv Composer is a builder and it can be used on pages and cloud templates only, not to create pots only templates for posts.
Thank you!
Hello,
To set a page to full width (or a cloud template), you’ll need to edit it with tagDiv Composer like this -> https://i.imgur.com/i5IUJ9E.jpg add or select a row and stretch it after your needs -> https://i.imgur.com/WKYebPX.jpg -> https://i.imgur.com/TO1BZ3M.png -> https://i.imgur.com/Yq8UCv3.jpg
If you want to make the layout full width, then to change the website width, you need to make sure that you don’t have set a background color/image in the Theme Panel because this makes your website boxed. Make sure this option is disabled => https://www.screencast.com/t/ejiNPCBF
Thank you!
Hi,
Based on the logs you’ve shared, it appears that the as_async_request_queue_runner action is being triggered frequently, leading to high CPU usage. This action is part of the Action Scheduler library, which is used by many plugins to manage asynchronous and scheduled tasks.
High CPU usage from this action is uncommon unless a large number of tasks are being generated. This could be caused by a plugin or theme creating excessive tasks, or by tasks not being properly cleared after execution.
To further investigate, consider using a plugin like WP Crontrol to inspect scheduled tasks (crons) for any unusual patterns. Additionally, you can check the Action Scheduler’s admin interface by going to Tools > Scheduled Actions to see if there are a large number of pending or failed actions.
There would be some ways to reduce the number of queries, if you will consider them.
For one of the queries (sql_calc_found_rows):
Reduce the number of ajax usage on the website, as those are the ones that will make requests to load more posts.
So ajax features like ajax pagination – https://i.imgur.com/EfKi0za.png – https://i.imgur.com/sMeot5s.png – https://i.imgur.com/vrJq3BC.png
The ajax menus – https://i.imgur.com/n0K9hCN.png
Also the header live search makes requests when it is used – https://i.imgur.com/1ZvDwZx.png This can be deactivated when using a cloud header template. We added an option specially for it, as it can cause increased load on large websites.
The mega-menu pagination – https://i.imgur.com/T8kYzu4.png This can be deactivated when using cloud header templates, an option for this was also added for the same reasons mostly.
You can disable the ajax view count from here -> https://i.imgur.com/BIwbscU.png
Me gustaría reportar un error relacionado con el funcionamiento del plugin td-cloud-library que afecta el rendimiento del sitio web. Al utilizar la consola de Query Monitor, me aparece el siguiente mensaje de advertencia:
Function _load_textdomain_just_in_time was called incorrectly. La carga de la traducción para el dominio td-cloud-library se activó demasiado pronto. Esto suele ser un indicador de que algún código del plugin o tema se ejecuta demasiado pronto. Las traducciones deberían cargarse en la acción init o más tarde. (This message was added in version 6.7.0.)
Detalles del error:
El error ocurre cuando el plugin intenta cargar las traducciones para el dominio td-cloud-library, pero las funciones de traducción (__() o translate()) se ejecutan antes del hook init, lo que causa que la carga de traducciones se realice demasiado pronto.
Esta carga prematura puede generar advertencias y afectar el rendimiento del sitio, ya que la traducción debería cargarse solo después de la acción init, que es el momento adecuado para ello en WordPress.
Registro del error:
El mensaje completo de la consola de Query Monitor proporciona el siguiente rastro:
_load_textdomain_just_in_time()
wp-includes/l10n.php:1379
get_translations_for_domain()
wp-includes/l10n.php:1409
translate()
wp-includes/l10n.php:195
__()
wp-includes/l10n.php:307
tdb_config::on_tdc_loaded()
wp-content/plugins/td-cloud-library/includes/tdb_config.php:15359
do_action(‘tdc_loaded’)
wp-includes/plugin.php:517
tdc_plugin_init()
wp-content/plugins/td-composer/td-composer.php:171
do_action(‘td_wp_booster_loaded’)
wp-includes/plugin.php:517
{closure}()
wp-content/plugins/td-composer/td-composer.php:191
do_action(‘td_wp_booster_legacy’)
wp-includes/plugin.php:517
Impacto del error:
El código del plugin está ejecutándose de forma incorrecta antes de que WordPress haya completado la inicialización de los recursos necesarios, como las traducciones. Esto puede generar problemas de rendimiento y posibles conflictos con otros plugins o funcionalidades del sitio.
Recomendación:
El problema parece estar en la carga prematura de las traducciones para el dominio td-cloud-library, lo cual depende de un código ejecutado demasiado pronto. De acuerdo con las mejores prácticas de desarrollo de plugins para WordPress, las funciones de traducción deben cargarse en el hook init o en un hook posterior.
Solicito su ayuda para corregir este comportamiento en el código del plugin, específicamente asegurándose de que las funciones de traducción se ejecuten correctamente solo después de que WordPress haya alcanzado el hook init.
Agradecería mucho si pudieran proporcionarme una solución para resolver este inconveniente, o bien, si existe alguna actualización del plugin que ya solucione este problema.
Hi people,
After installing my newsmag (latest).
I am not able to access admin.
I have verified that the files in question exist in the path they should. Not other changes are made since it a news site.
I have included pictures to show error, and the error message i get in admin.
td_api_base::mark_used_on_page : a component with the ID: tdc_check_domain is not set.
/home/seniorsprell.no/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php
Display backtrace
Array
(
[0] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php
[line] => 348
[function] => error
[class] => td_util
[type] => ::
[args] => Array
(
[0] => /home/seniorsprell.no/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php
[1] => td_api_base::mark_used_on_page : a component with the ID: tdc_check_domain is not set.
)
)
[1] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_api.php
[line] => 134
[function] => mark_used_on_page
[class] => td_api_base
[type] => ::
[args] => Array
(
[0] => tdc_check_domain
)
)
[2] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_autoload_classes.php
[line] => 23
[function] => get_by_id
[class] => td_api_base
[type] => ::
[args] => Array
(
[0] => tdc_check_domain
)
)
[3] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-content/plugins/td-cloud-library/includes/tdb_functions.php
[line] => 2136
[function] => loading_classes
[class] => td_autoload_classes
[object] => td_autoload_classes Object
(
)
[type] => ->
[args] => Array
(
[0] => tdc_check_domain
)
)
[4] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-includes/class-wp-hook.php
[line] => 324
[function] => tdb_on_before_admin_bar_render
[args] => Array
(
[0] =>
)
)
[5] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-includes/class-wp-hook.php
[line] => 348
[function] => apply_filters
[class] => WP_Hook
[object] => WP_Hook Object
(
[callbacks] => Array
(
[10] => Array
(
[wprss_modify_admin_bar] => Array
(
[function] => wprss_modify_admin_bar
[accepted_args] => 1
)
[tdb_on_before_admin_bar_render] => Array
(
[function] => tdb_on_before_admin_bar_render
[accepted_args] => 1
)
[tdc_on_admin_bar_menu] => Array
(
[function] => tdc_on_admin_bar_menu
[accepted_args] => 1
)
[00000000000032d90000000000000000backend_shortcut] => Array
(
[function] => Array
(
[0] => LiteSpeed\GUI Object
(
[_promo_true:LiteSpeed\GUI:private] =>
[_promo_list:LiteSpeed\GUI:private] => Array
(
[new_version] => Array
(
[0] => 7
[1] =>
)
[score] => Array
(
[0] => 14
[1] =>
)
)
[_summary:protected] => Array
(
[new_version] => 1748681771
[score] => 1749286571
)
)
[1] => backend_shortcut
)
[accepted_args] => 1
)
)
)
[priorities:protected] => Array
(
[0] => 10
)
[iterations:WP_Hook:private] => Array
(
[0] => Array
(
[0] => 10
)
)
[current_priority:WP_Hook:private] => Array
(
[0] => 10
)
[nesting_level:WP_Hook:private] => 1
[doing_action:WP_Hook:private] => 1
)
[type] => ->
[args] => Array
(
[0] =>
[1] => Array
(
[0] =>
)
)
)
[6] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-includes/plugin.php
[line] => 517
[function] => do_action
[class] => WP_Hook
[object] => WP_Hook Object
(
[callbacks] => Array
(
[10] => Array
(
[wprss_modify_admin_bar] => Array
(
[function] => wprss_modify_admin_bar
[accepted_args] => 1
)
[tdb_on_before_admin_bar_render] => Array
(
[function] => tdb_on_before_admin_bar_render
[accepted_args] => 1
)
[tdc_on_admin_bar_menu] => Array
(
[function] => tdc_on_admin_bar_menu
[accepted_args] => 1
)
[00000000000032d90000000000000000backend_shortcut] => Array
(
[function] => Array
(
[0] => LiteSpeed\GUI Object
(
[_promo_true:LiteSpeed\GUI:private] =>
[_promo_list:LiteSpeed\GUI:private] => Array
(
[new_version] => Array
(
[0] => 7
[1] =>
)
[score] => Array
(
[0] => 14
[1] =>
)
)
[_summary:protected] => Array
(
[new_version] => 1748681771
[score] => 1749286571
)
)
[1] => backend_shortcut
)
[accepted_args] => 1
)
)
)
[priorities:protected] => Array
(
[0] => 10
)
[iterations:WP_Hook:private] => Array
(
[0] => Array
(
[0] => 10
)
)
[current_priority:WP_Hook:private] => Array
(
[0] => 10
)
[nesting_level:WP_Hook:private] => 1
[doing_action:WP_Hook:private] => 1
)
[type] => ->
[args] => Array
(
[0] => Array
(
[0] =>
)
)
)
)
wp_booster error:
Missing parameter: ‘file’
/home/seniorsprell.no/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_autoload_classes.php
Display backtrace
Array
(
[0] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_autoload_classes.php
[line] => 45
[function] => error
[class] => td_util
[type] => ::
[args] => Array
(
[0] => /home/seniorsprell.no/public_html/wp-content/plugins/td-composer/legacy/common/wp_booster/td_autoload_classes.php
[1] => Missing parameter: ‘file’
)
)
[1] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-content/plugins/td-cloud-library/includes/tdb_functions.php
[line] => 2136
[function] => loading_classes
[class] => td_autoload_classes
[object] => td_autoload_classes Object
(
)
[type] => ->
[args] => Array
(
[0] => tdc_check_domain
)
)
[2] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-includes/class-wp-hook.php
[line] => 324
[function] => tdb_on_before_admin_bar_render
[args] => Array
(
[0] =>
)
)
[3] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-includes/class-wp-hook.php
[line] => 348
[function] => apply_filters
[class] => WP_Hook
[object] => WP_Hook Object
(
[callbacks] => Array
(
[10] => Array
(
[wprss_modify_admin_bar] => Array
(
[function] => wprss_modify_admin_bar
[accepted_args] => 1
)
[tdb_on_before_admin_bar_render] => Array
(
[function] => tdb_on_before_admin_bar_render
[accepted_args] => 1
)
[tdc_on_admin_bar_menu] => Array
(
[function] => tdc_on_admin_bar_menu
[accepted_args] => 1
)
[00000000000032d90000000000000000backend_shortcut] => Array
(
[function] => Array
(
[0] => LiteSpeed\GUI Object
(
[_promo_true:LiteSpeed\GUI:private] =>
[_promo_list:LiteSpeed\GUI:private] => Array
(
[new_version] => Array
(
[0] => 7
[1] =>
)
[score] => Array
(
[0] => 14
[1] =>
)
)
[_summary:protected] => Array
(
[new_version] => 1748681771
[score] => 1749286571
)
)
[1] => backend_shortcut
)
[accepted_args] => 1
)
)
)
[priorities:protected] => Array
(
[0] => 10
)
[iterations:WP_Hook:private] => Array
(
[0] => Array
(
[0] => 10
)
)
[current_priority:WP_Hook:private] => Array
(
[0] => 10
)
[nesting_level:WP_Hook:private] => 1
[doing_action:WP_Hook:private] => 1
)
[type] => ->
[args] => Array
(
[0] =>
[1] => Array
(
[0] =>
)
)
)
[4] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-includes/plugin.php
[line] => 517
[function] => do_action
[class] => WP_Hook
[object] => WP_Hook Object
(
[callbacks] => Array
(
[10] => Array
(
[wprss_modify_admin_bar] => Array
(
[function] => wprss_modify_admin_bar
[accepted_args] => 1
)
[tdb_on_before_admin_bar_render] => Array
(
[function] => tdb_on_before_admin_bar_render
[accepted_args] => 1
)
[tdc_on_admin_bar_menu] => Array
(
[function] => tdc_on_admin_bar_menu
[accepted_args] => 1
)
[00000000000032d90000000000000000backend_shortcut] => Array
(
[function] => Array
(
[0] => LiteSpeed\GUI Object
(
[_promo_true:LiteSpeed\GUI:private] =>
[_promo_list:LiteSpeed\GUI:private] => Array
(
[new_version] => Array
(
[0] => 7
[1] =>
)
[score] => Array
(
[0] => 14
[1] =>
)
)
[_summary:protected] => Array
(
[new_version] => 1748681771
[score] => 1749286571
)
)
[1] => backend_shortcut
)
[accepted_args] => 1
)
)
)
[priorities:protected] => Array
(
[0] => 10
)
[iterations:WP_Hook:private] => Array
(
[0] => Array
(
[0] => 10
)
)
[current_priority:WP_Hook:private] => Array
(
[0] => 10
)
[nesting_level:WP_Hook:private] => 1
[doing_action:WP_Hook:private] => 1
)
[type] => ->
[args] => Array
(
[0] => Array
(
[0] =>
)
)
)
[5] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-includes/admin-bar.php
[line] => 104
[function] => do_action
[args] => Array
(
[0] => wp_before_admin_bar_render
)
)
[6] => Array
(
[file] => /home/seniorsprell.no/public_html/wp-includes/class-wp-hook.php
[line] => 324
[function] => wp_admin_bar_render
[args] => Array
(
[0] =>
)
)
)
Uncaught Error: Class “tdc_check_domain” not found
in /home/seniorsprell.no/public_html/wp-content/plugins/td-cloud-library/includes/tdb_functions.php on line 2136
Call stack:
tdb_on_before_admin_bar_render()
wp-includes/class-wp-hook.php:324
WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:348
WP_Hook::do_action()
wp-includes/plugin.php:517
do_action()
wp-includes/admin-bar.php:104
wp_admin_bar_render()
wp-includes/class-wp-hook.php:324
WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:348
WP_Hook::do_action()
wp-includes/plugin.php:517
do_action()
wp-admin/admin-header.php:277
require_once(‘/home/seniorsprell.n…min/admin-header.php’)
wp-admin/index.php:137
Query Monitor
Hello team,
We’re currently encountering the following warning on our website running the Newspaper theme:
swift
Copy
Edit
Warning: Undefined array key “tdb_templates” in /srv/data/web/vhosts/www.spnl.org/htdocs/wp-content/plugins/td-cloud-library/includes/tdb_functions.php on line 661
This error started appearing after recent updates, and it’s now visible on our front end, impacting the user experience on https://www.spnl.org.
We would appreciate your support in resolving this issue. Could you please advise if there is:
A patch or plugin update available to fix this?
A recommended workaround to temporarily suppress the warning safely?
Any upcoming fixes in the next theme/plugin version?
Thanks in advance for your support. Please let us know how best to proceed.
Best regards,
Bassam
We have 2 problems on our website.
1:
We can’t update the theme. When we do, the websites design is crashed.
2:
Often when we want to upload media it takes ages to load and the website eventually crashes.
We tried everything, the debug file only shows 1 problem (german, but you’ll get it):
PHP Notice: Die Funktion _load_textdomain_just_in_time wurde fehlerhaft aufgerufen. Das Laden der Übersetzung für die Domain td-cloud-library wurde zu früh ausgelöst. Das ist normalerweise ein Hinweis auf Code im Plugin oder Theme, der zu früh läuft. Übersetzungen sollten mit der Aktion init oder später geladen werden. Weitere Informationen: Debugging in WordPress (engl.). (Diese Meldung wurde in Version 6.7.0 hinzugefügt.) in /html/wordpress/wp-includes/functions.php on line 6121
So the problem is the newspaper theme or the tagdiv plugins.
Website-URL: https://ludwigsburger-wochenblatt.de/
Could you help soon?
Thanks!
Valentin
Dear TagDiv Support,
My website is the problem: https://teknobilimadami.com/
I am experiencing a critical issue on my WordPress site that is directly related to the Newspaper Theme. When attempting to upload media files, the system either stalls significantly or fails with a 503 Service Unavailable error, specifically affecting the async-upload.php process.
Sometimes I add an image and when I open and close the page, I see that the image with the error has been loaded.
But these happen in the Newspaper theme. When I switch to the 2025 wordpress theme, images are uploaded instantly from the Media – Add Media – Media Library section without any problems.
After thorough debugging over the past 48 hours, I have tested and ruled out all other possible causes. Below is a complete breakdown of actions I took:
1. Hosting and Configuration
– PHP: 8.1
– Hosting: LiteSpeed / Shared Hosting (GuzelHosting)
– Limits Increased to:
– max_execution_time = 300
– upload_max_filesize = 128M
– post_max_size = 128M
– memory_limit = 512M
– Cloudflare set to “Development Mode”, and later fully paused
– WP Rocket and cache tools disabled during tests
2. Steps Taken & Results
– Switching to Twenty Twenty-Five theme resolves the issue instantly. Image uploads are fast and reliable.
– Activating Newspaper theme causes:
– Slow or failed uploads
– DevTools shows async-upload.php requests returning 503 errors
– Hosting panel shows CPU limit exceeded only when Newspaper is active
– Plugins tested individually (only Rank Math, SMTP, and Converter for Media were active; Converter later disabled)
3. Functions.php and Theme Code Review
– Output buffer using ob_start(“sanitize_output”) was temporarily removed.
– Theme update filters (pre_site_transient_update_themes) commented out.
– Admin-side JS injection via admin_head tested and removed.
These changes made little to no difference — the core issue seems to lie deeper in Newspaper’s admin/AJAX logic.
4. Attached Visual Evidence (8+ screenshots)
Please find attached:
1. DevTools console error (503 on async-upload.php) : https://prnt.sc/qHY-ahJWeCbr
2. CPanel CPU usage exceeded panel : https://prnt.sc/V4Wcb6RWVm8O
3. Functions.php sample (Attachments)
4. Theme switched: Twenty Twenty-Five (success) : https://prnt.sc/XsbBJDqxrBK_
5. Theme active: Newspaper (failure) : https://prnt.sc/3ORZ-qt9OwHj
6. WordPress debug.log output (Attachments)
7. Network panel XHR timing chart : https://prnt.sc/T1_rYdno5uaL
8. Cloudflare paused, issue persists : https://prnt.sc/CKQqSZ2OlLc-
I attach all other detailed screen photos to the e-mail. (20 attach picture screenshot)
Final Note & Request
I believe this issue can only be resolved from the theme side, not via hosting or plugin tweaks. I kindly request:
– Review of internal AJAX handling within the Newspaper theme
– Guidance on patching or disabling blocks that might interfere with admin upload requests
– Confirmation if this is a known issue, and whether an update will address it
I truly want this resolved. I have done my part as much as possible. Now I believe your team can take over and fix this properly.
I sent you contact@tagdiv.com e-mail in more detail. I would like to ask for your help in solving the problem.
Hi Patrik,
Using tagDiv Composer you’ll have access to use pre-made blocks, sections, pages, cloud templates. All those can be get from cloud and can be edited using tagDiv Composer.
Thank you!
Espero que se encuentren bien. Me gustaría exponer detalladamente las pruebas de rendimiento y la configuración de los plugins de optimización realizadas en el sitio http://www.itvpatagonia.com, con el fin de ofrecerles un contexto más claro sobre las conclusiones técnicas a las que hemos llegado respecto al rendimiento del theme Newspaper y el uso del plugin tagDiv Composer.
1. Plugins de Optimización Instalados
En el sitio web de http://www.itvpatagonia.com, hemos instalado y configurado los siguientes plugins de optimización para mejorar el rendimiento y la carga de las páginas:
WP Rocket: Configurado para la optimización de caché, precarga de caché, compresión de archivos estáticos, optimización de bases de datos, y optimización de scripts JavaScript y CSS.
Cloudflare: Usado como CDN y servicio de mitigación de ataques DDoS, con reglas específicas para excluir el backend de la caché y optimizar la entrega de contenido estático.
Redis: Configurado para optimizar la caché de objetos en el servidor, lo que ha ayudado a reducir los tiempos de respuesta de las consultas a la base de datos.
tagDiv Cloud Library: Plugin proporcionado por Newspaper para acceder a plantillas prediseñadas y optimizar el uso de recursos de la web.
Smush Pro: Usado para la optimización de imágenes, comprimiendo y redimensionando las imágenes para mejorar la velocidad de carga.
EWWW Image Optimizer: Complemento para optimizar aún más las imágenes y garantizar que estén en los formatos más ligeros posibles (incluyendo WebP).
2. Pruebas de Rendimiento y Revisión
A lo largo de este tiempo, hemos realizado diversas pruebas de rendimiento con herramientas como GTmetrix y Google PageSpeed Insights, así como evaluaciones internas utilizando New Relic y Query Monitor, para examinar el impacto de los plugins y la estructura del sitio.
Pruebas clave realizadas:
Rendimiento de carga: Con un volumen de alrededor de 10,000 publicaciones, observamos que la carga del sitio se ve afectada negativamente, especialmente al trabajar con tagDiv Composer y Newspaper.
Uso de CPU y memoria: Durante la carga masiva de contenido y la generación de nuevas páginas, experimentamos picos de uso de CPU, que no se lograron reducir completamente incluso después de optimizar todos los plugins de rendimiento mencionados.
Tiempo de respuesta del servidor: El tiempo de respuesta del servidor también se incrementa significativamente cuando el número de publicaciones excede las 10,000, independientemente de la optimización de caché y otros ajustes.
Problemas con tagDiv Composer: El plugin tagDiv Composer muestra un rendimiento inconsistente y no se comporta de manera óptima cuando se trabaja con grandes volúmenes de contenido. Esto afecta directamente la experiencia del usuario y la administración del sitio.
3. Conclusión Técnica
A pesar de la implementación y configuración de los mejores plugins de optimización disponibles, hemos llegado a la conclusión de que el tema Newspaper y su plugin tagDiv Composer no son capaces de funcionar de manera óptima con un volumen de contenido superior a 10,000 publicaciones. Este comportamiento se mantiene consistente a pesar de las múltiples configuraciones y ajustes en los plugins de rendimiento y cache.
Por tanto, la consulta técnica original no estaba relacionada con recomendaciones generales sobre qué plugins de optimización utilizar o qué tipo de hosting es el mejor. Ya hemos realizado todas las pruebas posibles en este sentido, y estamos en busca de una solución más profunda y técnica que considere los problemas de rendimiento inherentes al uso de Newspaper en sitios con grandes volúmenes de contenido.
Agradecería que, en lugar de proporcionar recomendaciones genéricas, pudiéramos recibir una revisión técnica detallada o incluso una actualización o mejora en los plugins/funcionalidades de Newspaper y tagDiv Composer que puedan garantizar el rendimiento adecuado en este tipo de sitios.
Quedo atento a su pronta respuesta.
Hi,
1. Yes, you can combine more pre-built website. All pre-build webiste have been made using tagDiv Composer and tagDiv Cloud Library. The most used option is to install a demo, in this case will be better to install the Job Hunt Pro and after that from Cloud templates to import the template you want for your website blog – https://i.imgur.com/cNEz2i5.png
2. The theme panel language will apply only on those texts that are not dynamic and can not be edited using tagDiv Composer. Use the theme builder, select the element and change the text – https://i.imgur.com/jiwnXRG.png – https://i.imgur.com/6EWvPqA.png
3. Settings the fonts in the theme panel it’s ok, but you’ll also need to set it on pages and cloud templates, it is possible that those to use different fonts – https://forum.tagdiv.com/font-customization/ open the page/template with tagDiv Composer and select the website manager, then select the global fonts and add your fonts there and replace those that are currently set – https://i.imgur.com/3t3A03G.png
4. You can import the homepage of Week Pro – https://i.imgur.com/1K8KAyR.png – https://i.imgur.com/muVc00t.png then set it as homepage, open the page with tagDiv Composer and add the elements you want on it, if you want you can use the cloud to add the Job Hunt sections you want in the week page – https://i.imgur.com/gqd7Upn.png – https://i.imgur.com/6XUhMrE.png
5. The sidebar can be set in 2 ways, using tagDiv Composer, set the row in columns and add in the right column the elements you want, then you can save the elements and drag theme from composer in the other pages and cloud templates.
Solution 2 is using widgets – https://forum.tagdiv.com/sidebars-tutorial/you can use default Newspaper sidebar widget, add the elements you want it it (dashboard > appearance > widgets), the just use tagDiv Composer on pages and cloud templates were you want the sidebar, ad the the sidebar widget and select the widget you want to display.
6. Unfortunately I can not see the article – https://i.imgur.com/D8JkMP1.png , but if you imported a single post template (week pro one) and is assigned, then the elements set in the theme should look the same, only the content added with the wordpress editor can look different, but not in matter of fonts, should be the same fonts.
7. This can be a problem related to more factors, for example something is interfering with the theme or theme plugin, or something is not installed enabled (required theme plugins), make sure that tagDiv Composer, tagDiv Cloud Library, tagDiv opt-in builder are installed and activated and also the Job Hunt PRO Plugin – https://i.imgur.com/2LGJPkD.png
8. Just make sure that you have install the pre-build website Job hunt pro and this will bring the form for submitting jobs – https://i.imgur.com/MlJLhOj.png – https://i.imgur.com/Y2K9PHD.png also you can check our documentation for how to create one – https://forum.tagdiv.com/create-frontend-submission-form/
9. To add an extra filter you’ll need to add a new taxonomy, this can be done using a plugin as ACF plugin, this allow you to create PCTs and taxonomies. Create the taxonomy you need and use the guide form point 8 to add the taxonomy on form.
Thank you!
