- NewsmagRequirements for Newsmag
- NewsmagtagDiv Social Counter tutorial
Hi,
Most of the time the problem is from a shortcode that is not compatible with our theme or a plugin conflict, therefore after you set it with tagDiv Composer and save the page/cloud template, the next time when you try to edit it, you’ll get that error.
If is only for one page or a cloud template (it can be on the header or footer, you can change them for tests and see if the problem persists), this is from some settings/shortcodes set on it and it can be fixed using the page revision -https://wordpress.com/support/page-post-revisions/
I hope this will help you!
Hi,
A 403 status means “Forbidden”, meaning something is blocking the request. Here are the most likely causes and fixes:
– Security Plugins or WAF (e.g. Wordfence, Sucuri, Cloudflare)
– ModSecurity (Server Firewall)
– Incorrect File Permissions, file should be 644.
– Theme or Plugin Conflict, do a test using only the main theme and tagdiv plugins.
Thank you!
Hi,
I think that here is a misunderstanding.
What I want to say is that if you use the free version of Elementor with the theme, there should be no problems, but this doesn’t mean that our theme contains elements from Elementor or elementor contains elements from our theme, each builder has it’s own elements, elementor has the elements coming with elementor and you can use it to create a page without problem and Newspaper theme has the tagDiv Composer that can create pages and cloud templates. Just do not use both builders on the same page.
Thank you!
Hi,
In td_011 are store all the data from the theme, there all set the settings, cloud templates, backup for theme panel, pages and so on. -> https://imgur.com/k7nkIRg
If you have more settings and a big website then is possible that the database to grow, there are set data for posts and pages, categories, author.
If you want you can check this article: 7 Tips To Reduce WordPress Database Size -> https://www.webhostingsecretrevealed.net/blog/wordpress-blog/7-tips-to-reduce-wordpress-database-size/ but before to make any actions, please make a full backup to your website and database and only after that make changes in database.
Thank you!
Hello,
We are sorry for this inconvenience.
Unfortunately, if you have the pro version of Elementor, this does not work with cloud templates; it works only for standard templates and only the free version work with cloud.
Thank you!
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,
What can be done is to replace all standard template and standard blocks with cloud template and flex blocks and after that to disable the tagDiv Standard Pack plugin, after that a good part of css will be removed.
Also, check if you are using css in live css – https://i.imgur.com/RyLF3vQ.png
Also, please check if the plugin has any option to remove unused css
Thank you!
Hi Rajender Singh,
I see that you are using standard templates and not cloud templates, but the mode that the block works is the same, the Related Articles will display only article s on the same level, so if you are in a subcategory, then will display only articles from that subcategory. If you want to change it you’ll need a developer that know how to change the code in wp-content/plugins/td-standard-pack/Newspaper/includes/shortcodes/td_block_related_posts.php file so it will work as you need.
Thank you for your understanding!
Hi percezioni.
You need to make sure that the social network are set with the full link (https://www….), please check in the theme panel > social > social networks – https://i.imgur.com/YnsOKLz.png make sure that if you have a social there is the complete link to that social. Next step will be to check on pages and cloud templates, the social networks, those are set using tagDiv Composer and not the theme panel settings, but the link should also be the full – https://i.imgur.com/aajksb1.png (set the full link)
Thank you!
Hi,
From the theme panel > social networks you need to remove the social networks and this will remove theme from standard headers and mobile menu. But in case that you are using a standard header template and not a cloud then this method will remove the socials from both (desktop and mobile) versions. So, if you are using a standard header and footer then you’ll need to use the above css.
The expanded subcategories on mobile menu can be achieve on cloud header were you can use a popup element as mobile menu and you can create the mobile menu in a page using tagDiv Composer and you can use the element list menu, that one can be configurate to display by default the menu expanded. This can be done only if you are using a cloud header.
If you are using the standard header then you can try this custom css:
.td-mobile-main-menu .sub-menu {
max-height: max-content;
opacity: 1;
}
.td-mobile-content .td_mobile_submenu > a .td-icon-menu-right {
display: none;
}
Thank you!
Hi,
If is a single post template from cloud, then it can be edited using tagDiv Composer, select the elements and changed the title – https://i.imgur.com/JAUfuHO.png – https://i.imgur.com/SXiycu0.png
Thank you!
Hi,
For Rank Math pleas ego to sitemap settings > cloud template and make sure all options are disabled – https://i.imgur.com/WFyEf6W.png also, go to instant indexing and make sure that cloud templates are unchecked – https://i.imgur.com/MprNNxq.png
Thank you!
Hi,
This can be done if you are using a cloud header, edit it with tagDiv Composer and use the mobile horizontal menu element – https://i.imgur.com/oOdrVwU.png
Thank you!
Hi,
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 when you try to edit it, you’ll get that error. The most simple and fast way to resolve it is to use a page revision – https://wordpress.com/support/page-post-revisions/ now if the problem is on all pages most of the time this problem is related to the cloud header and cloud footer (set a default one in the theme panel – https://i.imgur.com/VKTq62w.png and check if the problem persist, if not, then the problem is related after the last changes to the header or footer)
For this error, you can 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!
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
Hi,
I think that right no on mobile you do not have the responsive version of your website and I think that you are using the tagDiv Mobile theme plugin, this will change the layout and make it more simple.
It appears that your cloud header is empty, and the 2 top elements from the page (my account and subscribe).
My recommendation is to import the cloud header again from cloud templates – https://i.imgur.com/6LEylkO.png import the cloud header from the demo you have installed then just adjust it using the tagDiv Composer – https://forum.tagdiv.com/tagdiv-composer-tutorial/
Thank you!
Hi,
If you’re using Yoast SEO, you can easily prevent the tdb_templates pages from being indexed by Google. Here’s how:
Go to Yoast SEO > Settings in your WordPress dashboard.
Under Content Types, look for Cloud Templates.
Toggle “Show Cloud templates in search results” to Off.
This will add a noindex directive to those pages and keep them out of Google’s index.
If you’re using a different SEO plugin, look for similar settings to disable indexing of custom post types. If you’re not using any SEO plugin, you can manually disallow them in your robots.txt or add a noindex meta tag via a custom function.
Hope this helps!
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’re having an issue with our site where we have Cloud Templates for the header assigned to specific pages.
At seemingly random intervals, they are switching back to the global header for a time, then seemingly randomly going back to the correct Cloud Template – has anyone seen this or does anyone have any recommendations?
Thanks.
Asunto: Problemas persistentes con carga AJAX – Caché en bloques no fue efectivo
Estimado equipo de soporte de tagDiv,
Gracias por su respuesta anterior. Después de probar la solución recomendada de activar el caché para los bloques Flex, lamento informar que no produjo mejoras significativas en el rendimiento del servidor.
Actualmente operamos un sitio de noticias de alto tráfico con más de 10.000 publicaciones, y nuestra infraestructura incluye:
VPS optimo
Nginx, PHP 8.1 (FPM), Redis como caché de objetos
WP Rocket (totalmente optimizado), Cloudflare activo, y la última versión del theme Newspaper
No usamos WooCommerce ni funciones de suscripción – es un sitio exclusivamente de publicaciones
A pesar de tener todas las capas de caché activas y optimizadas, seguimos observando un alto consumo de CPU incluso en momentos sin visitas. Tras una revisión más profunda, la causa principal parece ser el uso de AJAX, especialmente:
admin-ajax.php?action=as_async_request_queue_runner
tareas en segundo plano generadas por el theme/plugins (probablemente vía Action Scheduler)
llamadas generales a admin-ajax generadas por el theme y el constructor
En este contexto, no es viable desactivar funcionalidades críticas o plugins simplemente para reducir la carga del servidor, especialmente considerando que muchas llamadas AJAX provienen de la estructura misma del theme (incluyendo tagDiv Composer y bloques dinámicos).
Necesitamos una solución técnica concreta y viable para reducir la sobrecarga de AJAX sin sacrificar funciones esenciales.
Agradeceríamos su orientación sobre lo siguiente:
¿Existe algún mecanismo interno o actualización en desarrollo para minimizar las consultas AJAX en segundo plano?
¿Es posible configurar tagDiv Composer o componentes del theme para reducir su dependencia de admin-ajax en entornos productivos?
¿Tienen prácticas recomendadas o configuraciones avanzadas específicamente para sitios con gran volumen de contenido que utilicen Newspaper?
Esperamos su orientación experta, ya que esta situación está afectando el rendimiento y la escalabilidad de nuestro sitio en producción.
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
Hello,
In addition to using caching, Cloudflare, and Redis, I’d also recommend enabling caching for the Flex Block. This feature can make a noticeable difference by significantly reducing the number of server requests, especially on content-heavy pages.
It’s also good to keep in mind that, like any visual page builder, tagDiv Composer requires more resources while editing. This is perfectly normal. Real-time builders perform many background processes—adding, removing, and modifying elements, all of which generate multiple live requests. On websites with large databases (for example, those with a high volume of articles), using filters on blocks can slow things down a bit, as each block applies its own query to retrieve specific content.
This behavior is common across most live builders, not just tagDiv Composer. The system is working hard to provide instant feedback, which naturally increases resource usage.
What you can do:
A good next step would be to monitor resource usage and identify which pages or specific elements are using the most server resources. Often, features like AJAX filters or “most popular articles” widgets can be more demanding, since they constantly query the database for up-to-date information.
Identifying and optimizing these high-impact areas can help keep your site fast and responsive both for your visitors and during editing sessions.
Thanks again
