- NewsmagUsing other ads
- NewspaperUsing Other Ads
- NewsmagSidebar ads
- NewspaperSidebar ads
- NewspaperIntroduction to CPT and ACF with Newspaper Theme
- NewspaperHow to edit modules for Flex Block X
- NewspaperHow to use the Posts List shortcode
- NewspaperCreate a frontend submission form
- NewspaperHow to Use the Tabbed Content shortcode
- NewspaperWooCommerce: Happy “Add to Favorites!”
- NewspaperHow to generate Facebook App ID
- NewspaperLink Tracker
- NewspaperFlex Block Settings Guide
- NewspaperGeneral Options that May Interfere with the Newspaper Theme
- NewspaperSocial Icons
- NewspaperPosts Loop Element
- NewspaperSet a Background for Category Page
- NewspaperThe Newspaper Mobile Theme: Introduction
- NewspaperHow to Add a Logo in Newspaper
- NewspapertagDiv Shop
Hello,
Since August 1, I have noticed that the WordPress administration panel has been responding more slowly than usual.
I have reviewed several possible causes and found that WordPress is currently reporting a critical Site Health issue related to autoloaded options.
Current data reported by WordPress:
– 1,326 autoloaded options.
– Approximate size shown by Site Health: 2 MB.
– WordPress indicates that this volume could affect performance.
I also checked the options table directly in the database. The current autoloaded volume is approximately:
– autoload = yes: 1.54 MB
– autoload = auto: 0.12 MB
– autoload = on: 0.11 MB
Approximate total loaded automatically: 1.77 MB.
The total number also matches the 1,326 options reported by Site Health:
– yes: 1,131 options
– auto: 164 options
– on: 31 options
– total: 1,326 options
The largest individual options related to Newspaper/TagDiv are:
– td_011_settings: 820.24 KB — autoload yes
– td_011: 164.02 KB — autoload yes
– td_011_remote_cache: 35.64 KB — autoload yes
– td_011_log: 8.18 KB — autoload yes
The td_011_settings and td_011 options alone total approximately 984 KB. Therefore, these two options currently represent more than half of all the data WordPress loads automatically.
As an additional check, I also found a residual option from an old plugin:
– wpts_compat: 287.02 KB — autoload yes
Using WP-CLI, I confirmed that it belonged to a previous WPtouch installation:
– Original serialized class: WPtouchDefaultSettingsCompat
– WPtouch is no longer installed.
– There is no active or inactive WPtouch plugin or WPtouch folder on the server.
I did not delete the option. I only changed its autoload value from yes to off in a fully reversible way.
After making this change:
– The total autoloaded size decreased from approximately 2.05 MB to 1.77 MB.
– The autoload = yes group decreased from 1.82 MB to 1.54 MB.
– The administration panel appears to respond slightly faster, although I cannot confirm with complete certainty that the improvement is exclusively related to this change.
– Site Health still reports a critical issue related to autoloaded options.
I have also reviewed other possible causes of the slow administration panel.
1. Action Scheduler
The active Action Scheduler table appears to be working normally:
– No actions are currently in progress.
– Only three actions are pending, and all of them are scheduled for future dates.
– There have been no new failed actions since August 1.
– There is no active backlog of blocked or repeatedly failing jobs.
2. WP-Cron
The WordPress cron option is approximately 12.28 KB, so it does not appear unusually large.
3. WP Rocket RUCSS and background processes
There are periodic checks related to WP Rocket SaaS jobs, but the actions are completed successfully and do not accumulate. There does not appear to be a blocked queue that would independently explain the continued wp-admin slowdown.
Therefore, I cannot confirm that Newspaper options are the only cause of the problem, but they currently represent the main remaining portion of the autoloaded data.
I would like you to review the following questions specifically:
1. Is it normal for td_011_settings to exceed 820 KB?
2. Do td_011_settings and td_011 need to remain autoloaded on every WordPress request, including wp-admin requests?
3. Is it safe to change the autoload value of either of these options to off, or does Newspaper require them during almost every request?
4. Does Newspaper provide an official process for cleaning, rebuilding, or reducing td_011_settings and removing old configuration data that is no longer used?
5. Could td_011_settings contain accumulated data from Cloud Templates, the Theme Panel, blocks, advertisements, headers, footers, or old configurations that are no longer active?
6. Is there a diagnostic tool or recommended method to identify which internal settings are responsible for the 820 KB stored in td_011_settings?
7. Would it be possible to split this option into several smaller options and avoid autoloading data that is only required on specific screens?
8. Has there been any recent change in Newspaper or TagDiv Composer that could have increased the size of these options or the amount of processing performed inside wp-admin?
I have not modified or deleted any Newspaper-related option. Before changing their autoload values or altering their contents, I need confirmation from your team regarding which options must remain autoloaded and what official procedure you recommend to reduce their size without affecting the theme or the Cloud Templates.
Thank you.
Hi TagDiv team. I just discovered a HUGE issue that is going to impact all of my media clients. We have been using infinite load for single posts to great success … so we thought.
However, I just discovered that when infinite scroll triggers, it loads three (or more?) additional articles … each of which trigger a GA4 pageview event. That’s a big problem because it is drastically over-inflating my clients’ GA4 pageview data and loading ad impressions that no one ever sees, lowering my clients’ ad click through rate (CTR).
Here is a Claude-assisted analysis I did looking at network-level events on one of my client sites. It might help you.
The solution would be to only load ONE new post at the bottom of a post, then load another new post at the bottom of the second post, and so one. The problem is when we preload MULTIPLE posts at the end of the first post.
Please let me know if I can be of any assistance. Most of my client site are geo-blocked to just the US and Canada, so we can open one up to you if you’d like.
Hi, I’m using tagDiv Composer on a page-type entry. When I add a “Column text” module inside a column and click the “Edit Content” button to open the text editor (WP Editor), the popup opens but stays stuck loading indefinitely with a spinning icon, never actually showing the WordPress editor.
Steps to reproduce:
Open the tagDiv Composer editor on an entry/page.
Add a Row with columns.
Drag the “Column text” module into an empty column.
Click “Edit Content” in the module’s settings panel.
The “WP Editor” popup opens but the content never finishes loading (infinite spinner).
Expected behavior: the WordPress text editor (WP Editor) should open so I can write/paste content, including shortcodes.
Actual behavior: the popup stays loading forever and doesn’t let me edit the module’s content.
Additional context: I specifically need this module because the “Raw HTML” module doesn’t execute WordPress shortcodes (it displays them as plain text on the frontend), and “Column text” should process them correctly.
Environment: WordPress with Newspaper theme / tagDiv Composer. Relevant active plugins: Advanced Ads, WP Fastest Cache, WPCode, Popup Maker, SEO plugin (Yoast or similar), among others.
Could you let me know if this is a known bug, or if there might be a plugin/cache conflict causing the editor not to load?
Hello tagDiv Team,
I noticed that the Social Counter element includes support for platforms like Facebook, Instagram, YouTube, TikTok, Pinterest, X (Twitter), and others, but there is no option to add Threads.
Since Threads by Meta has become a major social media platform and many publishers and news organizations actively use it, I believe it should be included as a supported social network in the Social Counter element.
Could you please let me know if there are any plans to add Threads support in a future update? It would be a valuable addition for publishers like us.
Thank you!
Is it possible to make the entire <row> highlighted in the photo visible only on the desktop version? And conversely, is it possible to set an entire <row> containing ads to be visible only on the mobile version?

Hi,
Maybe you’ve set that post back to draft because it leads to a 404 page for me. I checked other posts and the content seems to be displayed, for example this one https://www.stefanegirard.fr/barbe-incomplete-zones-clairsemees-faut-il-insister-corriger-ou-styliser-autrement/ displays the content -> https://prnt.sc/xUdisDTCDu_l
Is it happening just for some posts perhaps? If all the posts use the same post template as the post I checked, they should all display the post content.
Let me know.
Thank you!
Hi,
While ads can’t be inserted inside blocks, they can be inserted in post loops. There is an option which I think was added after this post was created -> https://prnt.sc/R9PVUePWS02G An ad can be set there and can be repeated after a set number of posts.
Besides that, ads can be displayed in ad boxes everywhere in the page, just not inside other blocks, only around them.
Thank you!
Let’s see.
1. That is possible.
The emails will be collected in the Emails section of our subscription plugin, please check the guide I provided above -> https://forum.tagdiv.com/leads/ You can create different lists if you want, and email addresses will be added in the lists. The list can be set on each of the leads element -> https://prnt.sc/aUbTvjHTDCHf
If you want to send an email on subscription, and also to try adn avoid spam, you can use this option -> https://prnt.sc/xegnD4O_3LFc This will send a thank you email and a confirmation link. The email can be customized in the subscription plugin email settings -> https://prnt.sc/N-9sQTmz6MTK -> https://prnt.sc/ipv5bEt3jML7 There are more emails that you can customize there as needed.
The emails can be exported -> https://prnt.sc/A5zlnQhjGAy0 No other management is available, exporting is usually the most important thing to have, so you can then import them in mailing/newsletter service. For example importing into Mailchimp from a file -> https://mailchimp.com/help/import-contacts-mailchimp/
2. I can’t say what your recommend setup is unfortunately, it depends on what type of content you want the subscribers to submit. As I mentioned, please start with a content submission page. A minimal submission page should contain the post title, the featured image, the post content, and of course the submit button -> https://prnt.sc/IZkaOWxFAlGw But you can collect more information relevant to the content type you are using. Custom fields can be used as well, through the ACF plugin.
3. I’m not sure what you mean exactly. The login/register page is for logging in or creating an account. That’s the only purpose of the page.
4. That is a button. It can be configured to open the mailing service of the visitor when pressed, so they can send you an email. Please configure the button like this -> https://prnt.sc/EoTLXYXzZZMD Use your email address.
These features that we are discussing are all theme features. Of course, for example for sending emails it depends on the capabilities of the website and may require a SMTP plugin. I suggest checking with your hosting about it.
Also, if there are things that aren’t working properly, please mention what is not working properly exactly, or provide some examples of the issue. I will check as well and try to help.
I hope that the information I provided is helpful. If you have any other questions let me know.
Thank you!
“Hello, I am here to report the same issue. Since updating to WordPress 7.0, the Gutenberg editor is severely bugged, very slow, and the layout/styles are completely broken.
I have done some troubleshooting on my end:
I tested other WP 7.0 sites without the Newspaper theme, and the editor works perfectly.
I disabled all third-party plugins, and the issue persists. It is definitively tied to the theme and the tagDiv Composer.
Checking the browser console, there are conflicts with the new WP 7.0 iframe structure. The console throws errors such as: td-guten-blocks-editor-css-css was added to the iframe incorrectly and fails to load load-scripts.php.
Is there an ETA for a full compatibility patch for WordPress 7.0?”
“Chrome Console”
load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-dom-ready,wp-hooks&ver=7.0:5 JQMIGRATE: Migrate is installed, version 3.4.1
v833ccba57c9e4d2798f2e76cebdd09a11778172276447:1 Failed to load resource: net::ERR_ADDRESS_INVALID
deprecated.min.js?ver=990e85f234fee8f7d446:1 Block with API version 2 or lower is deprecated since version 6.9. See: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/block-migration-for-iframe-editor-compatibility/ Note: The block “mpp/user-profile” is registered with API version 1. This means that the post editor may work as a non-iframe editor. Since all editors are planned to work as iframes in the future, set the apiVersion field to 3 and test the block inside the iframe editor.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 Block with API version 2 or lower is deprecated since version 6.9. See: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/block-migration-for-iframe-editor-compatibility/ Note: The block “mpp/user-profile-enhanced” is registered with API version 1. This means that the post editor may work as a non-iframe editor. Since all editors are planned to work as iframes in the future, set the apiVersion field to 3 and test the block inside the iframe editor.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 wp.compose.withState is deprecated since version 5.8. Please use wp.element.useState instead.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 Block with API version 2 or lower is deprecated since version 6.9. See: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/block-migration-for-iframe-editor-compatibility/ Note: The block “advads/gblock” is registered with API version 2. This means that the post editor may work as a non-iframe editor. Since all editors are planned to work as iframes in the future, set the apiVersion field to 3 and test the block inside the iframe editor.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 36px default size for wp.components.SelectControl is deprecated since version 6.8 and will be removed in version 7.1. Note: Set the __next40pxDefaultSize prop to true to start opting into the new default size, which will become the default in a future version.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 36px default size for wp.components.RangeControl is deprecated since version 6.8 and will be removed in version 7.1. Note: Set the __next40pxDefaultSize prop to true to start opting into the new default size, which will become the default in a future version.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
deprecated.min.js?ver=990e85f234fee8f7d446:1 wp.editor.RichTextToolbarButton is deprecated since version 5.3 and will be removed in version 6.2. Please use wp.blockEditor.RichTextToolbarButton instead.
S @ deprecated.min.js?ver=990e85f234fee8f7d446:1
load-scripts.php:1 Failed to load resource: the server responded with a status of 404 ()
Hi,
The theme ad spots are usually for ads, they can be any type of ads. But they could be used to display other things if needed.
For example in pages you can place ad boxes -> https://prnt.sc/AeKBgu11QDHF and select a spot -> https://prnt.sc/VM1dxB54O39L which displays content from the theme panel -> https://prnt.sc/_kAwiKZ_je0W
It depends on what you want to do exactly. If you want to display something related to businesses, and the information is added by the business owner when they submit their information on their website, then it depends on how you are collecting that information. If you end up using the frontend submission plugin that I mentioned, it should have options to create the submission form as needed, with custom fields as well. So you collect the information, and then you display it.
Our other theme, Newspaper, has frontend submission of it’s own, for example you can check the directory demos https://demo.tagdiv.com/select_demo/newspaper-prebuilt-websites/?demo-type=directory These all have one or more custom post types and content submission bases on subscription.
In case I misduerstood your question please correct me.
Thank you!
Hello tagDiv Team and Community,
I wanted to report a severe, obfuscated malware infection targeting the Newspaper theme ecosystem that I recently diagnosed and cleaned. The malware specifically targets mobile users while executing stealth tactics to hide from logged-in administrators.
Here are the technical details of the exploit to help the security team and other users:
1. The Behavior:
Mobile visitors loading the site are immediately hit with a 302 Redirect chain. The network analysis showed the site calling a rogue script masquerading as an ad network: [https://async.gsyndication.com/](https://async.gsyndication.com/). This script then loads a Yandex tracking tag ([https://mc.yandex.ru/metrika/tag.js](https://mc.yandex.ru/metrika/tag.js)), which triggers the final destination spam redirect (e.g., varors.com).
2. The Entry Point / Core Infection:
The script dynamically prepends an obfuscated PHP code block to the very top of wp-config.php using an eval(base64_decode(…)) string. When decoded, the script explicitly avoids injecting the malicious payload if the request URI contains paths like /wp-admin/, /wp-json, or wp-login.php, effectively hiding the redirect from site admins.
3. The Active Backdoor Location:
After cleaning wp-config.php, the file was repeatedly re-infected. Running a server-side file modification search (find . -mtime -2 -type f) isolated the live backdoor execution directly inside the td-mobile-plugin directory.
Files inside wp-content/plugins/td-mobile-plugin/ (specifically Mobile_Detect.php and custom code panel handlers) had been compromised and modified by the attacker to act as a persistent script injector. Every time a mobile user-agent touched the site, the plugin dynamically rewrote wp-config.php to maintain persistence.
How it was resolved:
Completely deleted the compromised td-mobile-plugin directory from the server.
Cleaned the wp-config.php file and stripped the eval block.
Implemented define( ‘DISALLOW_FILE_MODS’, true ); and hardened server file permissions (chmod 440 on config).
Please look into how the automated bots are injecting code into the td-mobile-plugin directories, and let this serve as a warning to other webmasters to check their mobile plugin files if they experience ghost redirects!
Hi,
after updating WordPress to the latest version and updating PHP on my server, the System Status page in the Newspaper theme stopped working.
Instead of showing the theme version and server information, I get this message:
“There has been a critical error on this website.”
Everything else works correctly:
the frontend works without issues
the Theme Panel loads
the website is fully functional
Only System Status is broken.
My environment:
Newspaper: 12.7.6 (the latest version available on ThemeForest)
WordPress: latest version
PHP: recently updated (likely 8.2 or 8.3)
No other changes were made
The issue appeared immediately after the WP + PHP update
Disabling cache/security plugins does not fix the issue
It seems that the System Status module in Newspaper 12.7.6 is not fully compatible with the newest WordPress/PHP versions.
Questions:
Is Newspaper 12.7.6 fully compatible with the latest WordPress and PHP 8.2/8.3?
Is this a known issue affecting the System Status module?
Is there a recommended PHP version (e.g., 8.1) for Newspaper 12.7.6?
Will there be an update to restore compatibility?
Hello,
We are experiencing an issue on our WordPress website using the Newspaper theme together with Cloudflare.
Every time we publish a news article, Cloudflare shows a CAPTCHA challenge before the publishing process can be completed. If we do not complete the CAPTCHA, the article is not published. The same thing also happens quite often when saving a draft.
The main problem is that we are currently unable to upload images properly. It looks like Cloudflare is blocking the upload process, but in this case no CAPTCHA is shown, so we have no way to complete the challenge. The only workaround we have found is to save a draft of any article, wait for the Cloudflare CAPTCHA to appear, complete it, and then our computer seems to be temporarily “authorized”. After that, we can publish articles, upload images and make other important changes for a while.
This issue also affects some Newspaper theme features. For example, the infinite scroll option, which loads more articles when scrolling, does not work unless the Cloudflare CAPTCHA has already been completed. The same happens with some news modules that load more posts or paginate results using AJAX.
This is especially important because the infinite scroll and AJAX loading issue affects 100% of our users. Visitors never see the Cloudflare CAPTCHA challenge, so they cannot complete it. As a result, they are unable to load more articles in any of the Newspaper theme “flex” modules that rely on AJAX loading or pagination. The module simply keeps loading forever, showing the spinning icon, but no additional content is loaded.
So the issue seems to be that Cloudflare is challenging or blocking some WordPress/Newspaper AJAX requests or admin actions, but in some cases the CAPTCHA is not displayed to the user, which makes the action impossible to complete.
Could you please help us identify which Newspaper theme AJAX requests, endpoints, scripts or WordPress actions should be excluded or whitelisted in Cloudflare so that features such as infinite scroll, AJAX pagination, image uploads, post publishing and the “flex” modules work correctly?
We would also appreciate any recommended Cloudflare configuration for the Newspaper theme, especially regarding:
* WordPress admin actions
* Media uploads
* admin-ajax.php requests
* Newspaper infinite scroll
* Newspaper AJAX pagination and post loading modules
* Newspaper “flex” modules that load more posts through AJAX
* Any theme-specific AJAX endpoints that should not be challenged by Cloudflare
Thank you.
please and please mr simion i beging you make the style of comments like this image and answer me quicly on support contact without other quations
I turned off tagDiv Mobile Theme, since I couldn’t controll the styles of homepage index – is it possible.
Without the plugin I cannot control the mobile logo. It either takes the Retina logo (I have conflict, because I need black for desktop and white for Mobile). Still cant find the place where i can edit this file https://iberix.pl/wp-content/uploads/2026/04/np10blue-white.png, which is preloaded for mobile version.
Another question: how could I edit the intex of articles on mobile version using tagDiv Mobile Theme. When I turn on the plugin the grid changes and the images of the articles are distorted.
my site’s iberix.pl
Hi,
Those thumbnails are indeed blurry. It’s the same on my test install. The thing is that they are also blurry if I test with a default theme, I think they look even worse https://prnt.sc/4SaSaFy2OAiT
There is a very small thumb there, 100×100 https://leather-templates.com/wp-content/uploads/2025/03/901-Leather-Belt-Pattern-v01-fixed-belt-free-02-100×100.jpeg If it was bigger it would look better, but I see no way to set a bigger thumb for the gallery in Woocommerce.
I found a lot of topics online about blurry woocommerce images, especially in galleries. It looks like there was an issue but I’m not sure if it was fixed https://wordpress.org/support/topic/weird-image-behaviour-in-product-gallery-after-last-update/
Some say to use this option in the wordpress customizer to make the thumbs bigger https://prnt.sc/6L8fZs_QQ3HE and then regenerate the thumbs, but I tried it and it doesn’t seem to have changed anything. I tried other code solutions but no luck so far. I’ll keep looking, maybe there is a way to increase the size of the thumbs or a way to make them look better.
Thank you!
Hello tagDiv team,
We would like to report a recurring fatal error affecting a WordPress.com-hosted site using Newspaper and tagDiv Composer.
This issue seems to occur only when the site visibility is set to private on WordPress.com. We use the same Newspaper/tagDiv stack on other sites, but this is the only one where the WordPress.com private-site access flow is involved.
The fatal error is:
PHP Fatal error: Uncaught Error: Class “td_res_context” not found
The error is triggered from:
wp-content/plugins/td-composer/legacy/common/wp_booster/td_js_generator.php
From the stack trace, the issue happens during the wp_footer hook. In this specific WordPress.com private-site flow, WordPress.com serves an access-denied/private-site template and calls wp_footer(). At that point, tagDiv Composer runs its footer callback and tries to use the td_res_context class, but that class has not been loaded yet.
The class appears to be defined in:
wp-content/plugins/td-composer/legacy/common/wp_booster/td_css_res_compiler.php
So it looks like the Composer callback in td_js_generator.php assumes that td_res_context is already available when wp_footer runs. That assumption seems to fail in this WordPress.com private-site access-denied context.
Environment:
– Hosting: WordPress.com
– Site visibility: Private
– WordPress: 6.9.4
– PHP: 8.4.21
– Theme: Newspaper 12.7.6
– tagDiv Composer: 5.4.5
– tagDiv Cloud Library: 3.9.5
– tagDiv Standard Pack: 2.8, built on 05.05.2026 9:08
We kept this issue as a low-priority investigation for some time because, although the fatal error was recurring in the PHP logs, the site appeared to work correctly in normal usage. Both the front end and the back office were functioning as expected, and we did not observe any visible impact for regular users or administrators.
However, the error became very frequent in the PHP logs, so we investigated further.
As a temporary workaround, we added a defensive snippet that runs before the tagDiv Composer footer callback and loads the file containing td_res_context only if the class is not already available. After applying this workaround, the recurring fatal errors stopped.
This suggests that the issue could be fixed in the plugin by either:
1. Ensuring the required dependency is loaded before td_res_context is used; or
2. Adding a guard clause before calling td_res_context inside the wp_footer callback.
Could you please review this scenario and consider adding a compatibility fix for WordPress.com private sites or for cases where wp_footer is called outside the normal theme-rendering flow?
Thank you.
Best regards.
Hello, Calin. Thank you for replying. I’m not using image ads, I’m using non-Google banner ads that are not images. I pasted the ad code into Custom ad 2 in the Theme panel. Then I dragged the box ad to the mobile header. Then I chose Custom ad 2 in TagDiv composer. However, when I click the other viewports, the Custom ad 2 code shows in all 4 viewports. I only want the mobile ad to show on mobile.
Hello, I have a non-Adsense 728×90 ad that shows in the mobile viewport and stretches off the page. I have followed every advice in other posts on this forum. I even created Custom ad 1 and Custom ad 2 in the Theme panel and configured them in the ad box. But the same ad code shows in all 4 viewports. So I was able to show a mobile ad for Custom 1, but the same ad also shows for desktop and tablet.
Why not make the 4 viewports separate instead of all 4 the same?
My question: Is there a way to hardcode the mobile ad so it doesn’t show on desktop?
Hi,
First thing is to make sure that you have all the OG data for this you can use our guide https://forum.tagdiv.com/facebook-share/
If everything is correct, then the problem is most likely related to the recent changes made by Facebook. There are also similar discussions reported by other users:
https://developers.facebook.com/community/threads/1253430129378332/
https://developers.facebook.com/community/threads/954245347126924/
Facebook goes crazy – not scrapping images, giving 403 response code suddenly on 10 of my blogs
byu/movies2019 infacebook
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.
Hello,
We are currently working with your Newspaper theme and have encountered an SEO issue when defining headings.
We have a global header with a mega menu, in which we have explicitly specified that the titles should be of the type <p>
If you check the following URL:
– https://living.spotahome.com/
You can see that there are two H1 tags (another error) and quite a few H3 tags coming from the menu; these H3 tags, when checking the page’s source code, start at line 2276.
All the source code for the menu appears as <p>, but it seems to be duplicated in this area, and we can’t figure out why.
We also have an issue with the two H1 tags—we don’t know where they’re coming from, but there should only be one.
Here is the SEO heading structure, where there should only be one H1 heading, and the rest should be H2 headings. The H3 headings are an error in the structure, and we couldn’t find them.
<H1> Spotahome LivingBest info for expats in european cities
<H1> Spotahome LivingBest info for expats in european cities
<H3> Digital Nomad Starter Kit for Spain: Essentials to Set Up Fast
<H3> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H3> Internet & Mobile Providers in Spain
<H3> Making Friends in Madrid: How to Build a Social Life Fast
<H3> Where to Live in Madrid in 2026: Best Neighborhoods
<H3> Barceloneta Beach Life: What Living by the Sea in Barcelona Is Really Like
<H3> Digital Nomad Starter Kit for Spain: Essentials to Set Up Fast
<H3> Barcelona Metro Guide: Everything You Need to Know Before You Ride
<H3> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H3> L’Eixample: Barcelona’s Modernist Architecture District
<H3> Your First Week in Valencia: What to Do and What to Set Up
<H3> Common Mistakes New Tenants Make (and How to Avoid Them)
<H3> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H3> The ultimate rental guide to Living in Valencia in 2026
<H3> Universities in Valencia: Complete Guide for International Students
<H3> Common Mistakes New Tenants Make (and How to Avoid Them)
<H3> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H3> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H3> Your First Week in Milan: What to Do and What to Set Up
<H3> Milan Design Week Guide, what to see, events, and tips for visitors
<H3> Living in Milan in 2026: The Complete Guide to Relocating
<H3> Your First Week in Berlin: What to Do and What to Set Up
<H3> Berlin Nightlife and Culture Guide: Clubs, Bars, and Creative Life
<H3> Berlin for Digital Nomads: Complete Guide to Living and Working Remotely
<H3> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H3> The ultimate rental guide to choosing where to live in Berlin in 2026
<H3> Common Mistakes New Tenants Make (and How to Avoid Them)
<H3> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H3> First Week in Paris: Checklist for Expats
<H3> Areas to Avoid in Paris: Safe Neighborhood Guide 2026
<H3> Living in Paris 2026: Complete Move and Life Guide
<H3> London first week checklist: essential guide for new residents
<H3> Where to live in London: 3 best neighborhoods to move to
<H3> Common Mistakes New Tenants Make (and How to Avoid Them)
<H3> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H3> London for Digital Nomads: Where to Live, Work and Connect
<H3> Common Mistakes New Tenants Make (and How to Avoid Them)
<H3> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H3> First Week in Brussels Checklist: What to Do First
<H3> Your First Week in Lisbon: What to Do and What to Set Up
<H3> Common Mistakes New Tenants Make (and How to Avoid Them)
<H3> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H3> Lisbon Neighborhoods Guide: Where to Live in 2026
<H3> Living in Lisbon: The Complete Guide for Expats and Newcomers in 2026
<H2> Your First Week in Berlin: What to Do and What to Set Up
<H2> Lisbon Neighborhoods Guide: Where to Live in 2026
<H2> Making Friends in Madrid: How to Build a Social Life Fast
<H2> London first week checklist: essential guide for new residents
<H2> Where to live in London: 3 best neighborhoods to move to
<H2> Barcelona Metro Guide: Everything You Need to Know Before You Ride
<H2> Eating in Barcelona Like a Local: Food Costs, Markets and Daily Habits for Expats
<H2> Valencia Neighbourhood Guide 2026: Find your perfect Barrio for your Lifestyle
<H2> Your First Week in Berlin: What to Do and What to Set Up
<H3> Join or social media
<H2> London first week checklist: essential guide for new residents
<H2> Where to live in London: 3 best neighborhoods to move to
<H2> Your First Week in Lisbon: What to Do and What to Set Up
<H2> Barceloneta Beach Life: What Living by the Sea in Barcelona Is Really Like
<H2> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H2> Barcelona Metro Guide: Everything You Need to Know Before You Ride
<H2> Common Mistakes New Tenants Make (and How to Avoid Them)
<H2> How to Open a Bank Account in Spain (2026) and Avoid Common Mistakes
<H2> First Week in Paris: Checklist for Expats
<H2> Valencia Neighbourhood Guide 2026: Find your perfect Barrio for your Lifestyle
<H2> Where to live in London: 3 best neighborhoods to move to
<H2> Universities in Valencia: Complete Guide for International Students
<H2> London first week checklist: essential guide for new residents
<H2> Where to live in London: 3 best neighborhoods to move to
<H2> Your First Week in Lisbon: What to Do and What to Set Up
<H2> Barceloneta Beach Life: What Living by the Sea in Barcelona Is Really Like
<H2> Digital Nomad Starter Kit for Spain: Essentials to Set Up Fast
<H2> Your First Week in Valencia: What to Do and What to Set Up
<H2> Your First Week in Berlin: What to Do and What to Set Up
<H2> Berlin Nightlife and Culture Guide: Clubs, Bars, and Creative Life
<H2> Common Mistakes New Tenants Make (and How to Avoid Them)
<H2> Berlin for Digital Nomads: Complete Guide to Living and Working Remotely
<H2> Barcelona Metro Guide: Everything You Need to Know Before You Ride
<H2> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H4> Enjoying the cityLifestyle
<H2> London first week checklist: essential guide for new residents
<H2> Where to live in London: 3 best neighborhoods to move to
<H2> London first week checklist: essential guide for new residents
<H2> Where to live in London: 3 best neighborhoods to move to
<H2> Your First Week in Lisbon: What to Do and What to Set Up
<H2> Barceloneta Beach Life: What Living by the Sea in Barcelona Is Really Like
<H2> Digital Nomad Starter Kit for Spain: Essentials to Set Up Fast
<H2> Your First Week in Valencia: What to Do and What to Set Up
<H2> Your First Week in Berlin: What to Do and What to Set Up
<H2> Berlin Nightlife and Culture Guide: Clubs, Bars, and Creative Life
<H2> Common Mistakes New Tenants Make (and How to Avoid Them)
<H2> Berlin for Digital Nomads: Complete Guide to Living and Working Remotely
<H2> Barcelona Metro Guide: Everything You Need to Know Before You Ride
<H2> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H2> London first week checklist: essential guide for new residents
<H2> Where to live in London: 3 best neighborhoods to move to
<H2> Your First Week in Lisbon: What to Do and What to Set Up
<H2> Barceloneta Beach Life: What Living by the Sea in Barcelona Is Really Like
<H2> Digital Nomad Starter Kit for Spain: Essentials to Set Up Fast
<H2> Your First Week in Valencia: What to Do and What to Set Up
<H2> Your First Week in Berlin: What to Do and What to Set Up
<H2> Berlin Nightlife and Culture Guide: Clubs, Bars, and Creative Life
<H2> Common Mistakes New Tenants Make (and How to Avoid Them)
<H2> Berlin for Digital Nomads: Complete Guide to Living and Working Remotely
<H2> Barcelona Metro Guide: Everything You Need to Know Before You Ride
<H2> Erasmus+ in 2026: The Complete Guide for International Students Coming to Europe
<H2> London first week checklist: essential guide for new residents
<H3> Where to live in London: 3 best neighborhoods to move to
<H3> Your First Week in Lisbon: What to Do and What to Set Up
<H3> Barceloneta Beach Life: What Living by the Sea in Barcelona Is Really Like
<H3> Digital Nomad Starter Kit for Spain: Essentials to Set Up Fast
Thank you in advance for your support.
Hi,
Yes, this is normal, the theme has 2 heads, one used only on mobile that starts from 737px (https://prnt.sc/VMduZHsWM4r3) width and the other one used for desktop. So if you have a cloud header, you can also edit the mobile header and add the elements you want to have when a mobile device is in use https://prnt.sc/Vd_GP6lzXlJV
Also, there is no real device that will have 767px width, so that case should ot happen on a real device.
Thank you so much, I’ve finally received the code in the ads tab after my persistence, but now I have another problem. After approval and adding the ads.txt code, the ads aren’t showing. Do I need to activate something in Newspaper for them to appear? I’ve enabled all the options in that tab, and I’ve configured automatic ads in ads.
Thanks
Please check on your mobile device and you can see that mobile menu is not working for pages.
Check for example:
https://ruralnet.mk/stratesko-i-proektno-planiranje/
or another page
Mobile menu is properly selected, look on attached photos and please help how to fix moblie menu on pages.


Thanks,
Vladimir