Search Results for 'cdn'

Results from the Forum
Calin
tagDiv Staff

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!

Calin
tagDiv Staff

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!

Calin
tagDiv Staff

Hi,
If the situation appears only when you are not logged in, then indeed is a cache problem. It will be need to be sure that your cache and object cache is cleared also if you are using CDN this must be purge.
Thank you!

Calin
tagDiv Staff

Hi,

If you have the last Newspaper version, 12.7.1 then please replace the td cloud library with this one https://cdn.tagdiv.com/wp-content/uploads/2025/07/td-cloud-library.zip

Thank you!

Calin
tagDiv Staff

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!

Calin
tagDiv Staff

Hi Aldis,
I see that now on desktop the results are better – https://i.imgur.com/d8ONEjN.png but on mobile are like you mentioned – https://i.imgur.com/FjqIfoQ.png

Her are some settings that can help.
– set the menu links using the custom link instead using page and category (those will do more request to the database the custom link).
– use plugins to clean transient and database ( WP-Sweep and Advanced Database Cleaner)
– make sure you have set the WP rocket settings similar with those from our guide – https://forum.tagdiv.com/wp-rocket-and-newspaper-theme-optimization-guide/ (settings can be changed if you find for your situation some configurations with better results)
– use a CDN https://forum.tagdiv.com/cloudflare-cdn/
– make sure you are using an image optimize
– use only cloud template and remove tagDiv Standard Pack plugin
– make sure all images have set width and height
I hope those will help you!
Thank you!

Calin
tagDiv Staff

Hello,
Before the update make sure you have a full backup, after the theme is updated please make sure that also the theme plugins are all updated. Make sure that the tagDiv Standard pack plugin will also be installed (this can be installed from Newspaper > plugins), when everything is updated, make sure that you clean all cache, object cache and purge CDN.
Thank you!

joseboto
Participant
#0

Dear TagDiv Support Team,

I’m currently using the latest version of the Newspaper theme for my editorial website project, and I’ve encountered an issue regarding the Social Share functionality.

Under Theme Panel > Social Networks, only a limited selection of platforms is available — such as Koo, Naver, Kakao, Flipboard, Gettr, and Copy URL. However, major platforms like Facebook, X (Twitter), WhatsApp, LinkedIn, and Email are completely missing from the list, and I’m unable to activate or reorder them.

This issue appeared recently. These platforms were previously visible and functional. So far, I have tried the following steps:

Cleared all cache (browser, WordPress cache plugins, and CDN)

Deactivated all third-party plugins

Reinstalled the theme from the official ThemeForest package

Tested on different browsers and devices

Despite these actions, the issue persists. Could you please assist in restoring the full set of social networks in the Theme Panel or advise on how to resolve this limitation?

Best regards,
José Boto

Calin
tagDiv Staff

Hi,

If I’m not mistaken, you’re currently using the latest theme version, 12.7.1 — is that correct? If so, please download the updated tagDiv Composer plugin from the following link: – https://cdn.tagdiv.com/wp-content/uploads/2025/05/td-composer.zip
After downloading, replace the existing plugin on your website with this one. It includes a fix implemented by our developers.

Thank you!

Calin
tagDiv Staff

Hi YamhillAdvocate,
Please try like this: check when you are logged in on the website if is displaying the right version or not, if is displaying the right version then you have a cache from a plugin, or maybe from server or CDN that is applying on your website.
Also, if the problem was resolve for a few minutes after the cache was cleared then this is a cache problem, but latter you disabled the mobile plugin … but there was still cache version delivered, not without cache.
When you are using the mobile theme plugin the cache plugin should support mobile cache (to have a separate cache version that will be delivered only on mobile devices, for example – https://i.imgur.com/4MtTg1K.pnghttps://forum.tagdiv.com/cache-plugin-install-and-configure/
Thank you!

Calin
tagDiv Staff

Hi,
This situation is related to the cache plugin you are using, this can not or do not have the option to cache the mobile version separate and deliver the mobile cache when a mobile is used and the cache of desktop version and a desktop is used. IN this situation if you want to keep the current cache plugin (or server/CDN cache, you need to disable the tagDiv mobile theme plugin and make sure that all cache and object cache is cleared).
Thank you!

Calin
tagDiv Staff

Hi Nikki,

This is what you can do:
– Clear all caches – Browser, WordPress cache plugin, and CDN (e.g. Cloudflare).
– Use normal URLs – Make sure you’re not visiting /amp/ or ?amp=1 versions.
– Resave permalinks – Go to Settings > Permalinks and click “Save Changes.”
– Check theme settings – Some themes have built-in AMP/mobile modes. Disable any AMP options.
– Remove AMP redirects – Check .htaccess for AMP rules and remove them if present.
– Redirect old AMP URLs – Redirect /amp/ or ?amp=1 to the regular post using a plugin or .htaccess

Thank you!

Calin
tagDiv Staff

Hi,

If I’m right you have the last theme version, 12.7.1, right? if is so, then please download the tagDiv Composer using this link – https://cdn.tagdiv.com/wp-content/uploads/2025/05/td-composer.zip and replace the one from your website. This plugin contains a fix made by our developers.

Thank you!

Calin
tagDiv Staff

Hi,

We are sorry for this inconvenience. This can be resolved by replacing the current tagDiv plugin with the one from here – https://cdn.tagdiv.com/wp-content/uploads/2025/05/td-composer.zip
I hope this will help you!

Thank you!

jasm90
tagDiv Member

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.

Calin
tagDiv Staff

Hi,

If I’m right you have the last theme version, 12.7.1, right? if is so, then please download the tagDiv Composer using this link – https://cdn.tagdiv.com/wp-content/uploads/2025/05/td-composer.zip and replace the one from your website. This plugin contains a fix made by our developers.

Thank you!

dragbikecom
tagDiv Member

I have the AMP Plugin activated because when I disabled it, I got this message:

‘The tagDiv Mobile Theme now works best with the AMP plugin to provide a complete solution for your content on mobiles.’

I thought I needed to run this as well. But I have disabled it and cleared my caches at our CDN, purged cache on the server, and on my browsers. But that did not fix the issue. The password protection works on POSTS but not on PAGES (on mobile). Would the AMP differ between the two types of content to allow it to work on POSTS and not PAGES?

Simion C.
tagDiv Staff

Hi,

This situation is a bit unusual. If anything, the website should be much faster if the images are delivered from a fast external source. I’ve seen for example cases with the ewww image optimization plugin, which can deliver images from their CDN, and the performance was improved drastically. And I’ve seen other cases with other image CDNs being used, with great results. I’m referring to websites that were also using our theme.

Testing with the composer inactive isn’t that relevant, as the pages will just be a bunch of code with no or less images. The composer is the theme.

Using lazyload should help, there’s a difference from loading all the images at once, and just the ones that are actually in view. Right now I see no lazyload active on the website. And I see that at this time the images are not served externally anymore on the website.

The problem could be with the source of the images, or something related to the offload plugin. What if its something similar to this topic https://wordpress.org/support/topic/wp-offload-media-lite-causing-huge-number-of-db-queries/ Are all the images offloaded? Or if you check with the query monitor plugin, is there also a high number of queries from the plugin?

Thank you!

andresugai
tagDiv Member

Update

After noticing a very high page load time on several pages on the site, I used the Code Profiler diagnostic tool to identify the plugins and themes that were contributing the most to the load time.

Initially, the profiler showed that the WP Offload Media plugin was consuming an excessive amount of time (approximately 4 seconds), which was the main factor in the slowness of the pages.

To diagnose the specific cause of this high consumption by WP Offload Media, I performed isolation tests of plugins and settings. I temporarily disabled other plugins and adjusted the WP Offload Media settings, running Code Profiler after each change.

The results of the isolation tests were very revealing:

Test 1 (Original Condition): With TagDiv Composer enabled and WP Offload Media enabled and configured to rewrite URLs to S3/CDN, WP Offload Media had an execution time of approximately 4 seconds. (See Screenshot 1: Original Condition)
Test 2: By disabling the TagDiv Composer plugin, the execution time of WP Offload Media dropped dramatically to around 0.06-0.15 seconds, a normal and acceptable time. (See Screenshot 2: TagDiv Composer Disabled)
Test 3 (Crucial Result): I kept TagDiv Composer enabled, but adjusted the WP Offload Media settings to disable URL rewriting (“Copy files also to Amazon S3” and “Rewrite Media URLs” options disabled). In this condition, with WP Offload Media still ON but not interacting with S3/CDN for rewriting, the execution time of WP Offload Media was approximately 0.22 seconds. (See Screenshot 3: WP Offload Media Active, S3/CDN Disabled, TagDiv Composer Active)
Based on these results, the conclusion is that the high CPU consumption and execution time by WP Offload Media (the 4 seconds) occurs specifically when the TagDiv Composer plugin is active AND WP Offload Media is configured to intercept and rewrite media URLs to Amazon S3/CDN. When S3 URL rewriting is disabled in WP Offload Media, even with the plugin active and TagDiv Composer active, the execution time of WP Offload Media returns to normal.
This strongly suggests that there is a conflict or inefficient interaction between WP Offload Media’s URL rewriting logic (when pointing to S3/CDN) and TagDiv Composer’s page processing. Unfortunately, disabling TagDiv Composer is not a viable solution, as it is critical to the structure and layout of my site built with your theme.

I was wondering if you have any knowledge of this specific compatibility issue or performance conflict when using TagDiv Composer/Newspaper Theme in conjunction with S3 media offload plugins that rewrite URLs (such as WP Offload Media). Is there a recommended setting within the theme or Composer, a specific plugin/theme version, or a workaround that can be applied to resolve this conflict and allow both plugins to work optimally together?

I greatly appreciate your attention, support, and any guidance you can provide in resolving this critical performance issue for my site.

Thanks for your help!

View post on imgur.com

Bettina
tagDiv Staff

Hello!


@simchris
Unfortunately, no.


@nitrofox
Make sure you’ve tried all the optimization suggestions from here:
https://forum.tagdiv.com/wp-rocket-and-newspaper-theme-optimization-guide/
https://forum.tagdiv.com/autoptimize-install-configuration/
https://forum.tagdiv.com/how-to-make-the-site-faster/
https://forum.tagdiv.com/cloudflare-cdn/
Limit the number of backups: https://app.screencast.com/M5Wco6Td6nymr
Google AdSense and CMP scripts (especially Google’s own CMP) are notorious for slowing down mobile performance on tools like PageSpeed Insights. You mentioned trying a timeout or “run on scroll” for JavaScript. While that helps ads, it’s problematic for CMP. As advice: Let the CMP load first, but delay ad-related JavaScript. Delay ad scripts, improve First Contentful Paint (FCP), and still show ads. Another workaround here could be to use data-block-on-consent for Ads. Please eliminate Unused CSS with PurgeCSS or WP Rocket Add-ons. Enable “Remove Unused CSS” if not already on.
In the WP Rocket -> Delay Javascript execution, you can add:
adsbygoogle.js
gpt.js
googletagmanager.com
googlesyndication.com
Any js code can be added here: https://app.screencast.com/uDYjK7nL0vKG8
I hope that helps you!

Thank you!

jusantoinette@gmail.com
tagDiv Member

Look I fully understand how to optimize wordpress for speed, but I don’t even have enough data on there for this to be occuring at a 12 post website. Thats should be concerning to you guys – on it’s own. What’s more is that CDN is also activated by default. In the last 20 years – I don’t think I’ve ever seen a template effect such a bad speed report, right out of the box with 12 live posts. I thought you guys would be concerned to get that feedback.

Bettina
tagDiv Staff

Hello!

Thank you for your feedback — we completely understand the importance of a high PageSpeed Insights score. Our theme is built following WordPress best practices and is optimized to perform well out of the box.

To achieve the best performance, we recommend:

– optimizing images (e.g. using WebP and compression),

– enabling lazy loading,

– using a caching plugin (like WP Rocket or LiteSpeed Cache),

and implementing a CDN for faster delivery of static assets.
Useful guides for optimization are here:
https://forum.tagdiv.com/wp-rocket-and-newspaper-theme-optimization-guide/
https://forum.tagdiv.com/autoptimize-install-configuration/
https://forum.tagdiv.com/how-to-make-the-site-faster/
https://forum.tagdiv.com/cloudflare-cdn/
Check all these requirements for the theme: https://forum.tagdiv.com/requirements-for-newspaper/
Limit the number of backups: https://app.screencast.com/M5Wco6Td6nymr

If you are still disappointed about our theme, you can request a refund here: https://themeforest.net/refund_requests/new

Thank you for your feedback!

Anamaria
tagDiv Staff

Hello,

What can I say, your experience was quite an adventure! I’m glad that in the end, you managed to solve it. Also, if you haven’t already done so, I recommend using Wordfence to scan your website. You can also use a CDN for added security. Also, the topic will remain open in case another user has experienced the same issue and can offer you some advice.

Have a great day!

Bettina
tagDiv Staff

Hello!

1. Free are the WP Super Cache and Cloudflare (CDN).
2. Try the Fluent Forms plugin or Contact Form 7 + Flamingo.
3. Try the OMGF plugin.
4. Yes, you can use only the theme features for ads. It’s pretty simple to use.

Thank you!

Viewing 25 results - 101 through 125 (of 6,440 total)