- 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
- Apitd_api_module::update_key
- Apitd_api_module::update
- Apitd_api_block::update_key
- Apitd_api_block::update
- Apitd_api_header_style::update_key
- Apitd_api_header_style::update
I see that there has been no progress on this front. I still have to use the CLEAR button under Theme Status to clean the transient entries in the database.
Since my website has significant traffic, the entries bloat the database and increase its size to hundreds of MBs.
Please can you tell me if you plan to fix it in the next update?
Thanks.
Hi tagDiv Team,
Thank you for the update.
I wanted to share that this forum was much more than just a community support platform. For many users, from beginners to experts, it acted as immediate first aid for almost every issue or feature understanding related to the Newspaper theme. It truly served as a comprehensive encyclopedia over the years.
I am incredibly grateful for the platform you built and the constant support you provided here. Thank you for all the effort put into maintaining it, and I look forward to continuing to work with your team via email.
Will miss you @ncalex & @bogdan-b 🙁
Regards,
Amit
Hi,
As far as I know all known vulnerabilities have been fixed for the composer -> https://patchstack.com/database/wordpress/plugin/td-composer/vulnerabilities
In the last update there were fixes for the composer, cloud library, opt-in builder -> https://tagdiv.com/newspaper-changelog/ I don’t think there are more at this time. Please update the theme.
Thank you!
Hi everyone,
We want to share an important update about how we provide support here at tagDiv.
After careful consideration, we’ve decided to close our community support forum. This wasn’t an easy decision, and we’re incredibly grateful for the years of questions, answers, tips, and troubleshooting shared here by all of you. This forum has been a valuable part of our journey, and your contributions have helped countless fellow users along the way.
What’s changing:
The forum will be closing, but rest assured – our commitment to supporting you hasn’t changed one bit.
What stays the same:
If you have an active support period, you’ll continue to receive the same dedicated support you’re used to – just through email instead. Our team will keep helping you with questions, issues, and guidance whenever you need it.
Why we’re making this change:
This move allows us to focus our resources on providing faster, more direct, and more personalized support to each of you – without the overhead of maintaining a separate forum platform.
What you need to know:
For support, simply email us at contact@tagdiv.com
Please make sure to provide a license key in the email, with a valid support period.
The forum website will be shut down in approximately one week.
We know change can bring questions, and we’re here for you every step of the way. Thank you for being part of this community – it’s been a pleasure supporting you, and we look forward to continuing that relationship via email.
Warmly,
The tagDiv Team
How are you updating the theme exactly?
Please use the automatic update from the theme -> https://prnt.sc/2tXnqfm9lhwA That option will update the theme and the theme plugins.
Or it could be updated manually. The steps are presented here -> https://tagdiv.com/update-newspaper-theme/
I wouldn’t advise using third party tools to update the theme. Please try the methods described in the guide.
Thank you!
…and coincidentally July 23rd is when I updated to the latest version of the Newspaper theme.
Hi, I tried to update the theme but I ran into this problem:
https://drive.google.com/file/d/1zj91LeocpH2lw-igN-O94w9a_SIUNZTW/view?usp=sharing
Hi Simion,
The website URL is https://mraclin.hr/
I have already completed all of those steps:
Scanned the entire database for cpajoliette (0 results).
Replaced WordPress core folders (wp-includes, wp-admin).
Updated the theme and tagDiv Composer to the latest clean versions.
Checked all theme options, headers, and custom code sections.
Ran a full Wordfence scan and verified that the files and database are clean.
Despite all files and database records being clean, external live scanners (like Sucuri) still report the injected script on the front end. Could this be caused by how tagDiv Composer caches shortcodes/elements, or is there a specific theme setting/table where this script could still be cached?
Best regards,
Mladen
Hi,
The latest theme update contains the fix for both the vulnerabilities you mentioned -> https://tagdiv.com/newspaper-changelog/ Please update the theme.
Thank you!
Not everyone. That issue happens only when using infinite load for posts. But we’ll see what we can do about in the next theme update, it’s a priority issue. We are very sorry for the situation.
Hi Simion,
Thank you for the update. I have updated the theme and tagDiv Composer to version 5.4.3.7, cleared all site cache, and re-scanned the site. However, ESET antivirus is still blocking the website.
Could you please advise if there are any specific database tables or remaining cached elements I should check, or if this might be a false positive on ESET’s end that needs to be reported?
Thanks!
Hi,
Sure you can, you can easily revert to the previous theme version right from the theme updates panel. The chances of having issues after updating are very low however. There’s isn’t much that could go wrong. I suggest trying it. In case there are any problems let know.
Thank you!
I’m going to perform the final update – New Version: 5.4.3.7 – I noticed it’s a robust update.
Whenever I perform an update, I’m apprehensive about potential problems on the site. If this happens, can I quickly revert to the previous version through the control panel? Thank you.
Hi,
Looks fine to me -> https://prnt.sc/77f2AXXQuCtW If there were design issues and there was code displayed, then most likely the required theme plugins weren’t updated or active.
Updating the theme using the automatic update method -> https://prnt.sc/6kml6pM1v_Lc should have updated the plugins as well. But if you updated manually perhaps, then the theme plugins must be updated/activated manually as well.
Thank you!
Hi,
Infinite loads for posts loads one post at a time once the previous post ends. The new posts are loaded with ajax in an iframe. And they are loaded entirely, the head content is loaded as well, meaning that this could indeed happen since the analytics code is loaded in the head.
However, I have so solution for this issue unfortunately. The infinite load feature was built a long time ago, and for now there aren’t any plans to rework it. I’ll mark it for further testing, maybe something could be done about it in a future update. Hopefully a solution can be found.
Thank you!
yess thnx just updated 🙂
Wordfence should mark it as fixed soon. The issue affected the composer from the Newspaper theme, which was fixed -> https://patchstack.com/database/wordpress/plugin/td-composer/vulnerability/wordpress-tagdiv-composer-plugin-5-4-3-reflected-cross-site-scripting-xss-vulnerability
Today a new update was released for Newsmag -> https://tagdiv.com/newsmag/ The composer is now version 5.4.6. Please update the theme and it will be fine.
The new update should be available now in the theme updates panel-> https://prnt.sc/1Ht5uOVL4ISe and also on the themeforest website. More about it here -> https://tagdiv.com/newsmag/
Go to Newspaper -> Plugins
Both ‘tagDiv Composer’ / ‘tagDiv Cloud library’ plugins are required and may need to be updated and activated (it is a 2 step process; click to update, then click again to activate; perform this on both plugins)
I just updated my site and noticed that I had to perform this after 12.7.7 update
Hope this is your answer.
(random user)
-
This reply was modified 2 weeks by
marcusdoc. Reason: clarity
In fact, the whole website looks different now! The update of the theme has changed my entire website! Please help.
Hi,
I did the latest theme update for the website http://www.travelmonitor.com.au and now the menu is broken and shows code instead of the menu. How do I fix this?
Hi,
We just released an update for Newspaper today, and very soon there will be one for Newsmag. It contains the fix for the issue. It doesn’t affect the Newsmag theme, but since the plugin is called the same and version is the same for both themes, it will get flagged regardless of using the Newsmag composer. We just need to change the version of the plugin basically. Hopefully we can do this today and release this minor update.
We are very sorry for this situation.
Thank you!
The tagDiv Header Search element generates invalid ARIA markup in both desktop and mobile header instances.
The generated HTML is:
<div class=”tdb-drop-down-search”
aria-labelledby=”td-header-search-button”>
The W3C validator reports:
The aria-labelledby attribute must not be specified on any div element unless the element has an appropriate role.
The search itself works correctly. The issue is specifically the generated markup.
I confirmed the source in:
wp-content/plugins/td-cloud-library/shortcodes/header/tdb_header_search.php
The original PHP output was:
$buffy .= ‘<div class=”tdb-drop-down-search” aria-labelledby=”td-header-search-button”>’;
I changed it to:
$buffy .= ‘<div class=”tdb-drop-down-search” role=”search” aria-labelledby=”td-header-search-button”>’;
After clearing caches and revalidating, both validator errors disappeared. Desktop and mobile search continued to function normally.
This confirms that the issue is not caused by search placement, template layout, or custom CSS. It is caused by the Header Search element omitting an appropriate role from the .tdb-drop-down-search container.
Please update the plugin output to include:
role=”search”
on that container, or otherwise revise the ARIA structure so aria-labelledby is used on an element with a valid role.
The error appeared twice because the page contains separate desktop and mobile Header Search elements.
The update will be available tomorrow, first thing. The package is almost ready.
@ferhatakbas
Is the website infected with malware? What files are being modified/infected because of the XSS issue exactly? Please install wordfence and scan the website if there are such issues.
This vulnerability from the composer is related specifically to the simplified button element -> https://prnt.sc/gvSvPHoOk3iV While this is a medium level vulnerability, even if the button is used in a page, there is very little risk of a website getting infected with malware because of it. I won’t get into more details about how it can be exploited, but again, the chances are very low. If your website is actually infected with malware, restoring backups won’t fix it, neither will updating the theme. Please use a security plugin like wordfence and scan the website’s files in and outside of the wordpress installation.
Thank you!
From what version did you update? Is this the main website? -> https://tbrnewsmedia.com/ That’s Newspaper 4, from 2014. This changes things. Those aren’t old shortcodes, they are very old shortcodes, they don’t exist in the theme anymore unfortunately.
My suggestion is to consider using a new homepage. If you want to keep it simple, I suggest the default demo -> https://demo.tagdiv.com/newspaper/ This is the non-PRO version. These non-PRO demos rely on the theme panel settings and templates.
You can also import just a homepage, they are available separately -> https://cloud.tagdiv.com/#/load/All It can be done from the cloud library dashboard -> https://prnt.sc/gmxEkzRSHmY1
Or you can choose any of the theme demos, if you maybe want to update the design -> https://demo.tagdiv.com/select_demo/newspaper-prebuilt-websites/?demo-type=all
The PRO demos are fully built with our composer, meaning you can edit and customize the homepage and also the post template, category template, etc. with the composer -> https://tagdiv.com/live-visual-builder/
We can discuss more, let me know if you have any questions.
Thank you!