- NewspaperHow to update a plugin
- NewspaperHow to update the WPBakery Page Builder plugin
- NewspaperHow to Update the Newspaper Theme
- NewspaperSingle Post Excerpt
- NewspaperWP Rocket and Newspaper Theme: Optimization Guide
- NewspaperCredit System
- NewspaperHow to use the Bing Maps API
- NewspaperModules Builder in Newspaper Theme
- NewspaperCreate a frontend submission form
- NewspaperCustom Fields Support
- NewspaperFlex Block Settings Guide
- NewspapertagDiv Opt-In Builder
- NewspaperHow to use the YouTube API
- NewspaperDefault Category Settings
- NewspapertagDiv Composer Tutorial
- NewspaperHow to Set the Image Avatar
- NewspaperUnique Articles
- NewspaperFacebook Share
- NewspaperCache plugin – install and configure
- NewspaperFeatured Image, Video or Audio
Hello,
It will be, but for the next one, not for today’s one, time was too short to fix it for today’s update.
Thanks!
Hi,
Quick update after upgrading Newspaper to v12.7.5.
The issue still reproduces with the Accessibility module enabled (Template Settings → Accessibility (Keyboard + Skip link + Search dialog)), but the behaviour has slightly changed due to the update.
Before 12.7.5, the focus/ARIA conflict typically involved #maincontent. After 12.7.5 (changelog mentions “Accessibility, improved main content wrapper selector”), the browser warning now consistently shows the ancestor being hidden/inert is #td-outer-wrap:
“Blocked aria-hidden on an element because its descendant retained focus…”
Focused element: #td-header-search-button / #td-header-search-button-mob
Ancestor with aria-hidden/inert: div#td-outer-wrap
So the underlying problem remains the same (ARIA hidden/inert applied to a container that still contains the focused search trigger/input), but the update appears to have changed which wrapper is targeted by the Accessibility logic.
We currently mitigate this with a temporary hotfix on our side that prevents aria-hidden/inert from being applied to the wrapper being targeted. After the update, that mitigation had to be adjusted from #maincontent to also cover #td-outer-wrap, which matches the new runtime behaviour.
In short: 12.7.5 changed the target wrapper, but the focus/aria-hidden timing conflict is still present.
Thank you.
Regards.
Hi,
This is not related to the theme updates, the file was made in 2021, and the last edit was in 2022 – https://prnt.sc/QCO_ijN0bNjc, so if the problem appeared only now, it was related to something else if the problem started just 19/02, maybe the amp was used without teh tagDiv Mobile theme plugin and only after your last update you also installed the tagDiv mobile theme to use it for amp?
Thank you!
Calin, good evening. This 404 error is only increasing in Google Search. One solution is to effectively edit wp-content/plugins/td-composer/mobile/header-amp.php to include nofollow parameters? A curious situation is that this error has never happened to us over several years – and with the increase reported by Google, we are concerned about our site’s ranking being lowered in the search engine. Is this a theme update issue?
I can edit the file directly from WordPress; could you guide me on how to do it?
Thank you.
I am currently running the Newspaper 12.7.4, TownTalk theme. Everything seems to be updated successfully, including the Newspaper plugins? I just discovered my WordPress error log is continuing to bloat with these errors. From my datacenter: https://levaire.com/td-cloud-library-database-error.png
Thoughts?
Hello,
After a recent update, I’ve noticed inconsistent behavior when loading my primary blog page at:
https://www.macworks.com/blog/
At times, the page loads as expected, showing the correct homepage layout and content. However, intermittently, the same URL displays a different or incorrect version of the page.
This is occurring using the same browser and URL, without any changes on my end between page loads.
I’ve included two examples below:
• Example 1: Expected homepage appearance
• Example 2: Alternate/incorrect page rendering that sometimes appears
Could you please review this behavior and advise what might be causing the inconsistency? I’m trying to determine whether this is related to caching, theme behavior, or a recent update.
Thank you in advance for your help.
Hello tagDiv Support Team,
I am using the Newspaper theme and have created a custom single post template. I want the “Display Featured Image (Show/Hide)” option to work correctly in this custom template.
Could you please clarify:
How this option is handled internally (post meta or theme setting)?
How can I conditionally show/hide the featured image in a custom single template based on this option?
Is there a recommended function, condition, or meta key to use so the behavior matches the default single post template?
I want to follow the theme’s best practice and avoid issues with future updates.
Thank you for your support.
Best regards,
Saroj Khanal
Please update me how to use the plugin and also is this plugin is free or proversion we have to use for extra features?? Did ACF plugin pro features are required??? Do let me know about the other plugins also Job Hunt PRO Plugin, Coaching PRO Plugin, Doctors PRO Plugin did i need to purchase to use any extra features is there any demo videos for these plugins.
Thanks
Hello tagDiv Team,
I hope you are doing well.
I am writing regarding a long-standing issue I have been experiencing with the Newspaper theme. This problem has been happening for approximately 7 years. I always hoped that future updates would eventually fix it, but unfortunately, it still persists.
The issue occurs when I use Cloudflare with the “Cache Everything” rule enabled (caching full HTML). This configuration has significantly improved my website performance and loading speed, which is extremely important for my project.
However, the problem is specifically with the mobile menu.
Randomly, when visiting the site on mobile and tapping the menu icon (hamburger icon) to open the side menu, the menu becomes completely unresponsive and does not open. The icon appears, but tapping it does nothing.
This issue:
Only happens on mobile devices.
Happens randomly — sometimes the menu works perfectly, other times it becomes blocked.
When it fails, it stays blocked until cache is cleared or refreshed.
Seems related to Cloudflare caching full HTML content.
Because it is random, you may sometimes see it working and sometimes not.
Please test this URL on a mobile device:
https://www.bibliatodo.com/TestimoniosCristianos/de-indigente-a-predicador-testimonio-impactante/
I have also recorded a video demonstrating the issue and will provide the video URL below.
After many years trying to investigate and solve this on my own without success, I was even considering changing the theme. However, I realized I never formally contacted you about this issue.
So I am reaching out with the hope that you can guide me toward a proper solution or best practice configuration when using Cloudflare Cache Everything together with Newspaper theme.
Could you please advise:
Is there any known compatibility issue between Newspaper and full HTML caching?
Is there a recommended Cloudflare configuration for this theme?
Are there specific scripts, cookies, or paths that should be excluded from caching?
Is there a known fix for the mobile menu becoming unresponsive under aggressive caching?
I truly appreciate your support and guidance.
Thank you very much in advance.
Best regards.
Yeah it’s so strange. The modal option is there, and seems to work everywhere apart from category cloud templates.
My updated work is still in dev but I’ll see if I can push it live sooner for you to take a look at. In the meantime, can you try importing the gallery template (https://cloud.tagdiv.com/photo-gallery-spa-heaven/) into a category cloud template, to see if it works for you?
Calin, I’d like to revisit this discussion. When I deactivate the mobile theme plugin, my entire site loses its configuration. Is there a solution so that I can access all my tagDiv Composer content on the mobile version? Previously, I could access our complete content, and I believe that with some update, our site became limited to news-only content on mobile – forgetting all the other content displayed on the main page. Could you help me? Thank you.
Hi,
after the last update all of the layouts I set were lost, pages loaded but none of the content appeared to click on, also I want to set white text on black background for my pages and posts, default text color #FFFFFF default background color #000000 but I can’t find where to do that without editing CSS files.
Thanks for any help.
Kevin
Hi @calin,
I’ll update you: I disabled Remove Unused CSS in Wp-Rocket and applied Loads CSS asynchronously (there are only these two options for CSS optimization). Leaving Loads CSS asynchronously enabled makes the menu work properly. My question is: is there a disadvantage to using it and avoiding Remove Used CSS? I mean, in my Google PageSpeed Insights score.
One last thing: I’m having some minor issues with my site and I don’t want to open up too many topics. Can I contact you via TagDiv’s email address so you can check a few things?
Thanks in advance for your reply.
Alex
Hi Calin,
I’ve tried importing the gallery on my local staging site using a blank category template, with all other plugins disabled, but frustratingly still can’t get the images to pop-up.
Update: if I create a new page, or a page cloud template, the gallery does work. However, if I import the gallery to a category cloud template, it doesn’t work.
Any idea why pop-up images wouldn’t work in category templates?
Hi,
Thank you for your suggestion. It has been added to our list, and we hope our developers will consider it for inclusion in one of the upcoming theme updates.
Hi,
The file is on the path wp-content/plugins/td-composer/legacy/Newspaper/includes/modules/td_module_single.php, but please notice that any changes made in the file will be lost when the plugin is updated.
What exactly do you want to edit in it? Maybe there is a different way.
It appears to be an update error, as we haven’t had any changes to our website – even when using AMP normally.
Hi!
I want to have the font color black, not grey, for the td-category-description on category pages like: https://www.rallyextra.se/kategori/reportage-2026/
I have updated the Custom CSS to:
.td-category-description {
width: 75%;
color: #000000;
font-weight: normal;
}
and width and font-weight is changed, but not the color of the text. What have I missed to fix?
Thanks for help.
Kind regards
Niclas
Hi!
I want to have the font color black, not grey, for the td-category-description on category pages like https://www.rallyextra.se/kategori/reportage-2026/
I have updated the Custom CSS to:
.td-category-description {
width: 75%;
color: #000000;
font-weight: normal;
}
width and font-weight is changed, but not the color of the text.
Thanks for help.
Kind regards
Niclas
Hi,
If you updated thetheme to version 12.7.4, did you set the theme panel update method?
Here is what you can try for the errors: go to plug-ins and disable and delete all td plugins you are using, go to Newspaper > plugins and reinstall and activate the plugins that were on the website before. In most situations, this resolves the problem.
Let me know the results.
Hello,
Unfortunately, there is no guide for how to move from Newsmag to Newspaper, but I will try my best to help you.
First, you need to make sure that you have a full backup for your website and database.
Now what you need to know is that during this process some elements, design from your website can be changed, so here are the steps that you need to do:
Right now you have the Newsmag theme activated, what you need to do is to install via WordPress the Newspaper theme, but do not activate it. After the theme is installed, go in plugins and disable all tagDiv plugins you have enabled and delete them, after that you need to activate the new theme (Newspaper theme) and make sure that you update and activate tagDiv Composer, tagDiv Standard pack (those plugins should bring back the website look and can be installed from Newspaper > plugins), also enable the rest of tagDiv plugins that you are using -> https://i.imgur.com/MvKx52B.png
I hope this will help you!
Hi,
WPBakery is a bundled plugin provided with the theme for older users who created pages using it. Some theme users have also created articles with this builder. However, it is not required, as the theme has its own builder, tagDiv Composer, which handles the theme layout.
If WPBakery is updated to the latest version, it should work with PHP 8+. We even recommend using PHP 8.3 for both the theme and WordPress.
Thank you!
Hi,
I believe that after the theme update, not all theme plugins that have been used before teh update have been installed/ updated. Please go to Newsapper > Plugins and see if you have the tagDiv Standard Pack plugin enabled, if not, install and activate it. I believe you had it before the theme update.
Hi,
Yes, the Facebook Like button has been deprecated. As a result, it is no longer being updated and will eventually stop working altogether.
A few weeks ago, the Like button was only displayed in the browser where you were logged into Facebook. (This should still work)
Hello TagDiv Support Team,
We are experiencing a critical performance issue on our website ifmnoticias.com, related to the Newspaper theme and TagDiv plugins.
We have detected excessive AJAX requests being generated from the following endpoint:
/wp-admin/admin-ajax.php?td_theme_name=Newspaper&v=12.7.4
In just 30 minutes, approximately 4,599 requests were sent to the site from this source. This spike is causing a significant increase in CPU usage on the server.
We suspect there may be a vulnerability or malfunction in the Newspaper theme (v12.7.4) and/or one of the TagDiv plugins triggering these repeated requests.
Actions already taken on our side:
Reduced the MySQL max connections from 5000 to 200 to improve stability.
Enabled Cloudflare Under Attack mode to mitigate potential abuse or malicious traffic.
However, the issue appears to originate from the theme/plugin itself rather than purely external traffic.
Could you please:
Confirm whether this is a known issue in version 12.7.4?
Advise if there is a patch, configuration adjustment, or update we should implement?
Recommend best practices to prevent admin-ajax overload caused by the theme?
This is a high-priority issue due to server performance impact.
We appreciate your prompt assistance.
Best regards,