- NewsmagHow to update a plugin
- NewspaperHow to update a plugin
- NewsmagHow to update the theme
- NewsmagHow to update the WPBakery plugin
- NewspaperHow to update the WPBakery Page Builder plugin
- NewspaperHow to Update the Newspaper Theme
- Apitd_api_top_bar_template::update_key
- Apitd_api_top_bar_template::update
- Apitd_api_single_template::update_key
- Apitd_api_single_template::update
- Apitd_api_footer_template::update_key
- Apitd_api_footer_template::update
- Apitd_api_smart_list::update_key
- Apitd_api_smart_list::update
- Apitd_api_thumb::update_key
- Apitd_api_thumb::update
- Apitd_api_category_top_posts_style::update_key
- Apitd_api_category_top_posts_style::update
- Apitd_api_category_template::update_key
- Apitd_api_category_template::update
Hi Chris, yes, all blocks, elements, and anything else that uses a global color or font will automatically update everywhere that global color or font is being used whenever it is changed.
So the cloud templates – do all modules use the global colors and fonts – so all modules can be updated fast via the global colors?
Hello,
after the last update of Newspaper theme, my social counter don’t works: it’s impossible to display the social icons and the counter (my business pages are connected).
Please let me know, thank you so much!
Carlo
The Social Counter does not scrape the Pinterest count. I have followers, but the count is zero.
I made sure all the keys were updated for the social sites.
I asked Cursor AI, with the (Auto) model selected, to review the code. It stated that there were issues with the Social Counter code.
Good morning,
I’m writing because, when accessing the WordPress dashboard and trying to open the Newspaper > System status section, a critical error appears and the page does not load.
The message displayed is the following:
“There has been a critical error on this website. Please check your site admin email inbox for instructions.”
The WordPress version currently installed is 6.9.4, while the Newspaper theme is updated to version 12.7.5.
I am also attaching a screenshot of the page. Could you please let me know what I can do to solve this issue?
Thank you very much
Hi,
I’ve just checked the site and can see that you’ve updated the block, and it is now displaying correctly. It looks like the issue was related to cached content that was still being applied.
Thank you!
Hi gmodonesi,
If you are using Cloud Templates, please make sure the required plugins are installed: tagDiv Composer and tagDiv Cloud Library. In some cases, tagDiv Opt-In Builder may also be needed.
If you are still using older templates, you will also need the tagDiv Standard Pack.
All these plugins can be installed from Newspaper > Plugins.
As a best practice, please always check which theme plugins are currently in use before updating the theme, and ensure they are properly installed and updated afterwards.
Thank you!
This also happened to me after update, I had to update and activate the mandatory plugins and it was able to fix it.
Hi,
I just checked teh website and now it appears to be ok.
Maybe the tagDiv Composer (theme plugin) was not installed/updated.
Thank you!
please, check http://www.jazzitalia.net
The website is competely broken after having updated to version 5.4.3.6.
Hi gmodonesi,
Did you make sure that all the theme plugins you used before the theme update are still in use? Could you provide a link to the website?
Hi,
I understand the situation.
What I recommend is to use a staging version of the website when performing the theme update. This allows you to safely test the update and check whether there are any impacts on the website layout or functionality before applying it to the live site.
Hi Paniki2300,
The Revolution Slider is currently showing the immediately next available plugin version rather than the latest one. This is expected behavior, which is why the version displayed may not match the most recent release.
To properly update the plugin, please follow these steps:
1. Connect to the theme account and download the full package
2. Unzip the downloaded package
3. Inside the extracted files, locate the plugins folder
4. Find the revolution_slider folder, which contains the plugin files
5. Use the zip inside this folder to install or update the plugin manually following the standard update procedure: https://forum.tagdiv.com/how-to-install-revolution-slider-v5/
Thank you!
oké, read it en will not do the update. I changed to much on the layout en will not start over again.
Hello guys,
I just updated to the latest version, and I can see in the changelogs that the latest version of Revolution Slider is included. (Ref: https://tagdiv.com/newspaper-changelog/ – misc: Updated Revolution slider to the latest version (7.0.11);)
But when I check my plugins page, it says I am running the version of 6.7.41, and there is a new update for Revolution Slider (6.7.54) which is another version of the mentioned 7.0.11?
So how do I update to latest version of this? When I download from Themeforest, I dont have the “Newspaper-tf\plugins\revolution_slider_5” folder, in the downloaded folder, even though I download the complete install package.
Can you please help me from here? 🙂
Hi,
Could you please provide a bit more detail?
Are you referring to changes made in the Theme Panel settings or modifications made directly within the theme files? If changes were made directly to the theme files, please note that these will be overwritten during a theme update. In such cases, it’s recommended to use a child theme for customizations.
If you are referring to Theme Panel settings, these should not be affected by a theme update.
A few recommendations:
– always perform a full backup before running any updates
– before updating the theme, take note of the active theme plugins, and after the update, ensure all required plugins are installed and up to date. If any required plugin is missing, you can reinstall it from Newspaper > Plugins
How to Update the Newspaper Theme – https://forum.tagdiv.com/how-to-update-the-theme-2/
Thank you!
Does it change setting on the old theme? I changed a lot…
Hello,
I made an update for the Newspaper and now is showing lik that when i am logged in on WP and when i try the page in incognito is showing the normal page.
What is the problem ?
Hi,
Those days will be a theme update, and it will also include an improvement to the weather widget.
Thank you!
Hello,
Our developers have already prepared a package for Newsmag; however, in the meantime, a vulnerability was identified in Newspaper, which has been prioritized.
An update for Newspaper will be released in the coming days, after which we will verify whether this vulnerability also affects Newsmag. If not, we will proceed with releasing the existing package.
Thank you for your understanding.
We’re now in May and still no update. When to expect?
I appreciate your suggestions and I will follow them. Thank you for reporting this issue to the theme developers. I hope they can fix it permanently in the next update, because mobile traffic is the most important. If it’s already like this on a VPS, I can only imagine how it must be for users on shared hosting.
I also forgot to mention that Google Fonts are significantly affecting performance. The theme depends on them, and they are adding about 37.8 KiB of render‑blocking resources in PageSpeed, as you can see in this screenshot: https://ibb.co/4H1PDGc
You suggested the OMGF plugin (https://wordpress.org/plugins/host-webfonts-local/). I installed it, but unfortunately it’s very limited and constantly shows messages encouraging you to upgrade to the Pro version to improve performance. The Pro version requires an annual payment.
I looked for alternative plugins, but most of them are also paid. My suggestion is something much simpler: please ask the theme developer to include an option to download and host the fonts locally directly within the theme, instead of depending on paid third‑party plugins. This would improve site speed and overall performance.
If you could also pass this suggestion on to the theme developer, it would help a lot.
Hi,
Yes, that’s very likely Facebook often caches old data. It can take some time for the updated image to appear.
You can speed it up by using Facebook’s Sharing Debugger to force a refresh.
Hello @Calin
I am writing to you after a deep technical audit that lasted two days, conducted by a Senior Infrastructure Engineer and Web Performance Specialist. We had to take this measure because our PageSpeed scores are stuck between 31% and 41% on mobile, despite running on a high-end VPS with persistent cache (Redis/Object Cache) and every possible server-side optimization.
Google has officially notified us regarding this poor performance, stating that our site is no longer a priority in search rankings due to failing Core Web Vitals. After a thorough investigation of the source code and database, we have pinpointed the root cause: The Newspaper theme is loading both Desktop and Mobile assets simultaneously on mobile devices.
Even with dedicated mobile pages (separate IDs), the theme “stacks” the entire desktop framework on top of the mobile one. This redundancy is killing our performance.
I need you to take this diagnostic to the tagDiv development team immediately. We need to know if and when a fix will be released. If this architectural flaw is not resolved, I will be forced to migrate to another theme or develop a custom one, as I cannot afford to lose my SEO ranking due to theme bloat.
Technical Diagnostic:
Problem: Mobile pages heavier than desktop pages
Date: 03/05/2026
Theme: Newspaper 12.7.5
Plugin: td-composer
Server: VPS Ubuntu — CyberPanel — LiteSpeed
CONTEXT
The site glostv.com uses the Newspaper 12.7.5 theme with the td-composer plugin and has a system of separate pages for mobile and desktop, where each version was built individually in the Newspaper visual editor (tagDiv Composer). The site owner reported that pages on mobile are significantly heavier than on desktop, even though there are separate and optimized mobile pages already built.
MOBILE SYSTEM ARCHITECTURE
The following pages were created as mobile templates inside the tagDiv Composer itself and are marked in the database with the flag tdc_is_mobile_template = 1:
ID 7584 — tv ao vivo Brasil (mobile version)
ID 7617 — POPULARES TOP (mobile version)
ID 8700 — Estados (mobile version)
ID 8872 — Homepage (mobile version)
ID 9944 — Política de Privacidade (mobile version)
ID 9948 — Termos de Uso (mobile version)
ID 10581 — Sobre Nós (mobile version)
ID 10597 — Política de Cookies (mobile version)
TECHNICAL PROBLEM IDENTIFIED
Problem 1 — td-composer loads assets WITHOUT any device distinction
Confirmed directly in the file:
wp-content/plugins/td-composer/legacy/common/wp_booster/td_wp_booster_functions.php
Line 362 — Composer JS loads for ALL devices:
add_action(‘wp_enqueue_scripts’, ‘load_js_composer_front’, 1000);
Line 430 — Full Newspaper CSS loads for ALL devices:
add_action(‘wp_enqueue_scripts’, ‘load_front_css’, 1001);
Line 744 — Full theme JS loads for ALL devices:
add_action(‘wp_enqueue_scripts’, ‘load_front_js’);
None of these functions have any device check. They load for both desktop and mobile equally, without any condition whatsoever.
Problem 2 — The mobile engine loads ON TOP of the desktop engine
Confirmed in the file:
wp-content/plugins/td-composer/mobile/functions.php
Line 149 — Mobile CSS loads ON TOP of the desktop CSS already loaded:
add_action(‘wp_enqueue_scripts’, ‘tdm_load_front_css’);
Line 173 — Mobile JS loads ON TOP of the desktop JS already loaded:
add_action(‘wp_enqueue_scripts’, ‘load_front_js’);
Line 184 — Mobile specific script loads ON TOP of all previous ones:
wp_enqueue_script(‘td-site’, TDC_URL.’/mobile/js/tagdiv_theme.min.js’);
Problem 3 — The flag tdc_is_mobile_template does NOT remove desktop assets
Confirmed in the file:
wp-content/plugins/td-composer/includes/tdc_state.php
Line 42:
private static $is_mobile_template = false;
Line 202:
public static function set_is_mobile_template($is_mobile_template) {
self::$is_mobile_template = $is_mobile_template;
}
This flag only serves to let the visual editor know it is on a mobile page. It does not execute any removal of desktop CSS or JS. It is purely an internal state variable with no effect on asset loading.
Problem 4 — Proof: Zero wp_dequeue for mobile anywhere in td-composer
I ran the following command directly on the server via terminal:
grep -r “wp_dequeue|deregister” wp-content/plugins/td-composer/ -n | grep -i “mobile|desktop|css|js”
The only result found was the removal of Visual Composer scripts in the backend administrative editor, not in the frontend. Throughout the entire td-composer codebase, there is not a single wp_dequeue_style() or wp_dequeue_script() instruction conditioned on mobile device detection in the frontend.
WHAT THE MOBILE BROWSER IS ACTUALLY DOWNLOADING
When a user accesses the site from a mobile device, the browser downloads all of this before rendering the mobile page:
From the desktop engine (which should NOT load on mobile):
Full legacy CSS of Newspaper
td-composer frontend JS (desktop visual engine)
tagdiv_theme.min.js desktop version
td-cloud-library CSS
td-standard-pack CSS
td-multi-purpose/style.css
Desktop version fonts
From the mobile engine (which loads ON TOP of the desktop):
Newspaper mobile CSS
tagdiv_theme.min.js mobile version
Mobile specific scripts
Fonts loaded again
The mobile browser is downloading the complete Newspaper framework twice. Once for the desktop layout that is discarded and once for the mobile layout that is actually used. This directly explains why mobile pages feel heavier and slower than desktop pages. DIRECT QUESTION TO SUPPORT
Does td-composer 12.7.5 have any native mechanism to remove desktop engine assets—specifically the functions load_front_css, load_js_composer_front, and load_front_js located in td_wp_booster_functions.php—when the page being served is already marked with tdc_is_mobile_template = 1 in the database?
If yes, in which file and on which line does this asset cleanup occur?
If no, when is the development team going to release an update to fix this? It is unacceptable that a high-end theme like Newspaper forces a mobile device to download the entire desktop framework AND the mobile framework simultaneously. My server-side analysis confirms that even when using dedicated mobile pages, the theme simply “stacks” assets instead of “swapping” them.
This redundancy is causing a massive performance overhead and killing our Core Web Vitals. We have separate pages for a reason, and the theme should NOT be loading desktop junk on a mobile-dedicated template. We need a clear position on when this will be resolved so that tdc_is_mobile_template = 1 actually triggers a wp_dequeue of unnecessary desktop resources.
