- NewspapertagDiv Cloud Library Plugin
- NewspapertagDiv Shop
- NewspaperHow to Use tagDiv Cloud Library
- NewspaperCloud Library Templates
- NewspaperDesign your Post Pages using the Cloud Library Templates
- NewspapertagDiv Composer Tutorial
- NewspaperIntroduction to CPT and ACF with Newspaper Theme
- NewspaperSocial Sharing
- NewspaperInfinite Loading for Single Posts
- NewspaperCustom Post Type Support
- NewspaperHeader Builder
- NewspaperUsing the Theme Translations with WPML
- NewspaperInstagram in Newspaper WordPress Theme
- NewsmagRequirements for Newsmag
- NewspaperSmart Lists
- NewspaperAuthor Card
- NewspaperFeatured Images
- NewspaperSmart Sidebar
- NewspaperPost template ads
- NewspaperFooter Builder
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!
Hi,
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!
Hello, I just installed Yoast SEO Premium, and I see that no schema is passing through nor breadcrumbs list.
In the Theme Panel the “enable article schema” is disabled, and in Yoast SEO I use the default article for all posts.
The URL of my post is https://horrormovies.gr/movies/final-destination-bloodlines-2025-review/.
I disabled all plugins also except the tagDiv Composer, tagDiv Cloud Library, and Yoast SEO. Nothing changed.
Hi,
The demo you have was builder using tagDiv Composer and cloud templates, therefore everything can be edited using the theme builder on frontend. The theme panel settings are normally added by tagDiv standard pack, please check if this plugin is installed if you have it, please disable, this brings old templates that are not editable on frontend with the builder.
– https://www.youtube.com/watch?v=SoGQ0d5kIBg
Thank you!
Hi again,
Thank you for your previous response. I understand that there is currently no native support for a global Page template similar to how Single Post templates work via Cloud Library.
However, duplicating a designed page manually for each of our pages is unfortunately not a scalable or maintainable solution for our workflow.
Here’s why:
We have over 80 static Pages (not Posts) — such as “Rankings”, “Terms of Use”, “Privacy Policy”, etc.
We need all these pages to have a consistent layout, identical to our Single Post template (header, featured image, date, sidebars, etc.).
Editing and managing 80 separate copies of the same layout breaks maintainability — any design update means repeating changes manually 80 times.
The current Cloud Library approach works great for posts, but we’re specifically trying to apply it to WordPress Pages.
We’ve tried using custom page.php templates in the theme or plugin folders, but TagDiv Cloud Library always overrides the page output.
What we’re asking:
Is there any method — through PHP, a filter, or even a workaround — to assign a single Cloud Template (or custom template) globally to all WordPress Pages and have it pull each page’s content automatically?
We believe this would be extremely useful for many use cases, and perhaps there’s an internal way or workaround that we’re missing.
Thank you again for your support and time — we really hope there’s a way to make this work.
Best regards,
Hi,
This notice will be resolved in the coming theme update, but until then if you want you can get the plugin td cloud library with the fix 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
Thank you!
Hi,
Our theme offers the possibility to display any ads and banners using the ad box element, this element can be set using tagDiv Composer on pages and cloud templates.
To create slider ads or other type or ads it will be need to use a dedicate plugin for ads or to have the code that can rotate the banners. All those can be displayed using the ad box element, the shortcode/ code can be set in the theme panel ads section and from the ad box element can be choose that source from the ad should be read or it can be set directly on ad box element in custom ad tab.
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.
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
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.
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!
I don’t use cache at all i deactivate…
List Module:
AMP
MailPoet
MC4WP: Mailchimp for WordPress
tagDiv Cloud Library
tagDiv Composer
tagDiv Mobile Theme
tagDiv Newsletter
tagDiv Opt-In Builder
tagDiv Social Counter
tagDiv Standard Pack
Selectează WPS Hide Login
WPS Hide Login
Yoast SEO
This is a list of my plugin.
i use Cpanel Litespeed Webserver
Hi,
1. When you see shortcodes on your website it is because some theme plugins are not installed and activated, please go to Newspaper > plugins and make sure that tagDiv Composer, tagDiv Cloud library are installed and activated, if there are still shortcodes on your website, this means that there are other team plugin that needs to be installed (it can be tgDiv opt-in builder, or maybe the tagdiv social counter or newsletter)
2. If I understand correctly you are referring to the post template used for your articles, if you have cache and object cache, make sure that you clear it select the template you want to use for your articles, try to set it in the theme panel – https://i.imgur.com/FcBQ13r.png
3. The media images that you are referring are coming from tagdiv Newsletter plugin, if you do not use it then you can disable the plugin and delete the images, but if you use the plugin and delete the image, then those will bring back when the newsletter shortcode is used and when the plugin is installed.
Thank you!
Dear Support Team,
we are currently experiencing an issue with the Newspaper 12 theme (latest version) in a WordPress Multisite environment. On any post or page where the paywall is active, the burger menu also displays the paywall overlay. This is incorrect behavior — the navigation menu should remain accessible and unaffected by the paywall restriction, allowing users to browse the site structure even if the article content is restricted.
This issue is particularly noticeable on mobile devices and occurs consistently on all pages with active paywall protection. It seems that the paywall overlay wraps the entire page content, including the mobile navigation menu.
We are using the following setup:
• WordPress Multisite with separate instances per blog
• Theme: Newspaper 12
• Page Builder: tagDiv Composer (for all pages)
• Post Editor: Gutenberg (for all articles)
Relevant Plugins in use:
• tagDiv Cloud Library
• tagDiv Composer
• WooCommerce
• WooCommerce Memberships
• WooCommerce Subscriptions
• and others
Hi,
Based on your screenshot, some of the theme plugins appear to be disabled. Please go to Newspaper > Plugins and make sure that tagDiv Composer, tagDiv Cloud Library, and any other theme plugins you were using are installed and activated. This should resolve the issue.
Thank you!
Hi,
In those case the first recommendation will be to make sure you are using the last theme version and WordPress version. If you already have the last version of the theme, please disable and delete tagDiv Composer and tagDiv Cloud Library, after that please go to Newspaper > plugins and reinstall those 2 plugins from there.
I hope this will help you!
Thank you
Contextual Menus Not Working in TagDiv Composer – Persistent React Error #200
Issue Description
The contextual menus (e.g., row settings, column settings) in the TagDiv Composer builder are not opening or responding on all browsers (Chrome, Brave, Firefox). The browser console shows the following React error:
text
Uncaught Error: Minified React error #200; visit https://reactjs.org/docs/error-decoder.html?invariant=200 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at react-dom.min.js?ver=18.3.1.1:10:128046
at classic-editor.js?ver=d439270160c30dd62b3a:525:5674
at window.yoast.initEditorIntegration (classic-editor.js?ver=d439270160c30dd62b3a:525:6011)
Steps Already Taken
Disabled all plugins except TagDiv Composer, Cloud Library, and essential TagDiv plugins – issue persists.
Increased PHP memory limit to 256M in wp-config.php.
Added the recommended .htaccess directives for TagDiv builder functionality at the end of the .htaccess file (including SubstituteMaxLineLength 10M and Header always append X-Frame-Options SAMEORIGIN).
Reset theme options via Theme Panel > Support > Reset Theme.
Tested with default WordPress theme (Twenty Twenty-Three) – TagDiv builder not available for testing there.
Verified no 403/404 errors on admin-ajax.php requests in the network console.
Noted Google Maps warnings related to deprecated markers but confirmed API key is valid.
Tested the issue on multiple browsers (Chrome, Brave, Firefox) with the same result.
Technical Environment
Theme: Newspaper 12
Active TagDiv Plugins: Composer, Cloud Library, etc.
Hosting: Infomaniak
PHP Version: 8.1+
Apache modules confirmed active: mod_headers, mod_rewrite
mod_substitute is enabled (confirmed with hosting support)
No server-side errors related to permissions or timeouts found.
Request for Support
Please help identify the root cause of the React error in classic-editor.js, which seems related to Yoast SEO integration.
Confirm compatibility of TagDiv Composer with React 18+ and the latest WordPress versions.
Advise on any necessary server configurations or known conflicts that could cause this issue.
Provide guidance on ensuring proper DOM targeting and iframe handling within the builder to restore contextual menu functionality.
Attachments
PHP and server error logs (available via Infomaniak Manager).
Full browser console logs including Console and Network tabs.
Exported theme settings from Theme Panel.
Additional Note:
The .htaccess directives recommended by TagDiv for the builder’s proper operation have been added at the end of the .htaccess file and are present on the server.
Thank you very much for your assistance. Looking forward to your guidance to resolve this issue.
Best regards
