- NewspaperSocial Sharing
- NewspaperSharing
- NewspaperDesign your post pages using the Default Templates
- NewspaperFacebook Share
Claude for the win! – Found it — confirmed directly in the page’s DOM. The cause is a menu link URL collision, not a bug in the “active state” logic itself:
The root issue: Under each of the SPORTS, NEWS, MUSIC, and BUSINESS dropdowns, the “Writers” submenu header is set to link to https://barrettmedia.com/ — the homepage — instead of a real anchor page (probably because there’s no dedicated “Writers” landing page, so whoever built the menu left the URL pointing at home as a placeholder).
WordPress’s nav walker assigns the current-menu-item / current_page_item classes (which drive the “active” styling) by comparing each menu item’s URL to the current page’s URL. Since four separate “Writers” items all share the exact same href as HOME, all of them get flagged current/active whenever you’re on the homepage — alongside HOME itself, which is correctly active.
That’s 5 “active” items per menu instance (HOME + 4x Writers). And because the theme renders the same nav markup three times in the DOM (desktop menu, mobile menu, and what looks like a sticky/duplicate header version — all sharing the menu-fall-2025-main-menu-2 menu), it shows up 15 times total in the page.
The fix: give each “Writers” submenu parent a real destination (an actual writers/authors archive page, or at minimum a distinct # / non-matching anchor) instead of the bare homepage URL. Once those links stop matching https://barrettmedia.com/, WordPress will stop marking them current, and only HOME will show active on the homepage.
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
I got this info from BlogVault on vulnerabilities of Tagdiv Composer and Tagdiv Opt-in Builder:
Hubert Séguin
Hi Simion,
Thank you for your help, but still don’t work. I record a video, look if I did something wrong. https://drive.google.com/file/d/1ECKDCkBuaBzArHQ6fI7dBEt9kmqG6nKX/view?usp=sharing
Hi,
When I add this code, the text appears too small, both when used in a normal block and in a classic paragraph:
The font size is set to 12, but it doesn’t render as an actual 12pt — it displays much smaller than that. Even if I increase the font size value, the text still stays just as small and doesn’t change.
Could you please check why the size isn’t being applied correctly?
https://drive.google.com/file/d/1mNdMANvtH9s3fCRpURR26iO-JL4EtadY/view?usp=sharing
Thank you,
Antonella
Hi Newspaper support,
I’d like to set Georgia 12px as the default font for post content. I went to Theme Panel > Theme Fonts > Post Content and set it there, but the change doesn’t seem to take effect.
When I use Gutenberg blocks, the text still appears smaller than expected — Georgia 12 only displays correctly if I use the Classic Editor instead.
I also noticed that if I go into the block options and manually set the Typography size to “M”, the text does display correctly in Georgia 12. However, I don’t want to have to set this manually every time — I need it applied by default, automatically, without editing each block individually.
Theme: Newspaper, version 12.7.6
WordPress version: 7.0
Could you help me understand why the Theme Fonts setting isn’t being applied automatically to Gutenberg content, and how I can fix this so the font applies consistently by default, regardless of which editor I use?
Thank you very much for your help.
Kind Regards
Antonella
Hi,
Please make sure that the OG meta tags required for sharing on socials are available on your website -> https://ahrefs.com/blog/open-graph-meta-tags/ Or else the sharing may not work correctly or at all.
The theme does not load the OG meta tags, each website owner can use their preferred method for loading them. Since most website owners use a SEO plugin, the usual method is to load the OG meta tags with the SEO plugin, like Yoast -> https://ahrefs.com/blog/open-graph-meta-tags/#setting-open-graph-tags-in-wordpress Or please check the settings of your preferred SEO plugin.
If you are already loading the OG meta tags and it’s not working, I suggest using the Facebook debugger -> https://developers.facebook.com/tools/debug Test the post there to see if there are any issues.
Thank you!
When sharing news posts on platforms like Facebook or WhatsApp, the featured images are not being pulled or displayed in the link preview. This issue is affecting the appearance and engagement of shared posts. Please investigate and resolve the problem as soon as possible.
Meragujarat.in
Hello everyone,
I’m having a license activation issue with the Newspaper WordPress Theme by tagDiv and I would like to know if anyone has experienced something similar.
I have an official Envato/ThemeForest Regular License for Newspaper Theme. The purchase is valid and the item still appears in my Envato downloads area. The license certificate confirms the purchase for:
Tema: Newspaper – News & WooCommerce WordPress Theme
Autor: tagDiv
Tipo de licença: Regular License
The theme had been working on this website for years.
The problem started after I reset the license key/domain association inside the Newspaper/tagDiv panel. After the reset, the license seems to have lost its association with the domain, and now I cannot activate it again.
Current behavior:
1. With no HTTP-blocking snippet active, WordPress Site Health does not show any warning about external HTTP requests being blocked.
2. When I try to activate the theme with the official Envato purchase code, the Newspaper activation page shows:
“Your purchase key is not valid.”
3. Earlier, when a performance snippet was active, the activation screen showed:
“Envato API is down, please try again later.”
4. That snippet was related to WP_HTTP_BLOCK_EXTERNAL, but it has already been disabled for testing.
5. With the snippet disabled and server cache cleared, the error is no longer the API error — it is now:
“Your purchase key is not valid.”
6. The key is the official purchase code from Envato, and the product is still listed in my Envato account.
It looks like the reset removed the domain association, and now the tagDiv validation system is rejecting the same official purchase code instead of allowing me to reassign it to the website.
I have already contacted tagDiv support, but I’m posting here in case someone has gone through the same situation and found a faster technical workaround.
Has anyone experienced this after resetting a Newspaper Theme license/domain association?
Is there any safe way to force the theme to re-sync the license with tagDiv/Envato, or does this require tagDiv to manually reassign the domain on their side?
Important: I am not sharing the full purchase code publicly for security reasons, but I have the official Envato license certificate and proof of purchase.
Thank you.
I’d like to know how to make these settings visible only to administrators, so authors can’t change them. I’ll post a screenshot to show exactly which options I’m referring to.
https://drive.google.com/file/d/1afHqyPhRqdCiW-Qvhn7pKWz3X3-1mJ0R/view?usp=sharing
Thank you
Hi,
Unfortunately there isn’t much we can do about that. Maybe its’ something temporary on their side. Did you test with the Facebook debugger?
As long as the required OG meta tags are loaded on the website, and I see you are loading them with Yoast -> https://prnt.sc/Wl-VvjlYnklE the sharing should work.
And normally if it works in the Facebook debugger -> https://developers.facebook.com/tools/debug it works with most other socials. I tested a few posts and it seems to work -> https://prnt.sc/u9l4JNqqPQQt
Besides the OG meta tags there are some recommendations for the featured image size, but these aren’t exactly requirements -> https://developers.facebook.com/docs/sharing/webmasters/images/ It does say something important here -> https://prnt.sc/aFNQHT-1psvp
I suggest testing the post with the debugger, and then sharing it.
Thank you!
Hi,
I’m attaching some screenshots to show the issue I’m still experiencing:
Desktop version shows this : https://drive.google.com/file/d/1yvIdZ7OQoG1CVzYcbSVwprbJPobEu7rP/view?usp=sharing
Mobile version not shows banners:
https://drive.google.com/file/d/1aIlYlGByVFndlmmE6e07WPBYztzGm1MO/view?usp=sharing
I’m currently resolving the server‑side issues with my hosting provider, so that part is already being handled.
Thank you!
Hi,
If the image appears in the debugger, then the image should appear when sharing. That warning is not important.
The problem is that you don’t seem to be loading the required OG meta tags for sharing. Without those the sharing may not work or it can use the wrong information or image. It can be very random.
Please check this guide https://ahrefs.com/blog/open-graph-meta-tags/
Are you planning on using a SEO plugin on the website? That’s normally a required plugin for any website, and also a good way to load the OG meta tags for sharing. In the guide I provided please check this section specifically https://ahrefs.com/blog/open-graph-meta-tags/#setting-open-graph-tags-in-wordpress
Then the sharing should work fine. Please check it out.
Thank you!
Hi, We have problem when try to share article https://aafpress.ge/?p=3658 on facebook, the photo does not appears.
on facebook tool https://developers.facebook.com/tools/debug we got message: Warnings That Should Be Fixed – Inferred Property – The ‘og:image’ property should be explicitly provided, even if a value can be inferred from other tags.
https://prnt.sc/E1lOMG5FQNO1
https://prnt.sc/Uq9xdFvgXQtW
Could you please help us to fix this issue
Can you fix the errors? We need answers!
Hi,
I understand your point, and I also understand that Facebook currently has crawler inconsistencies affecting many websites.
However, from a technical and operational perspective, the conclusion in my specific case remains very simple:
- At 3:00 PM the website was using Newspaper and Facebook sharing returned 403/incomplete OG scraping.
- At 3:30 PM, on the exact same server, same IP, same Apache stack, same PHP version, same firewall, same permissions and same Facebook crawler, the issue disappeared immediately after switching to a competing theme.
No other infrastructure variable changed.
This does not necessarily mean the theme is “globally broken,” but it clearly demonstrates that the theme stack is not compatible with every environment or every Facebook crawler scenario.
And honestly, identifying why a specific theme behaves unpredictably in some environments is not the responsibility of the webmaster or the client. That responsibility belongs to the software vendor and its technical architecture.
From the user perspective, the reality is straightforward:
with Theme A the feature failed, with Theme B it worked instantly in the same environment.
At that point, continuing to blame Facebook, the provider, Apache or the firewall becomes difficult to justify from an evidence-based perspective.
Thank you anyway for the discussion and for taking the time to reply.
Bye.
Hi,
I still suggest considering that it is not a theme related issue. Please also consider the level of support requests we would receive, if it would not work for anyone. I’m sure that other theme users are using the Facebook share as well.
Besides this topic, there is only one other topic this entire year, with the same issue. Please check this other topic https://forum.tagdiv.com/topic/response-code-403/ The user did not change the theme, yet the sharing is working now. If it was something from the theme, then why is it working.
And please also consider the hundreds and thousands of similar online complaints describing the same issue, on Facebook’s forums. I’m sure that not all those websites use Newspaper.
The theme cannot block Facebook from accessing the website or resources from the website, it can’t return a 403 response by it’s own. There must be something specific that causes it, or simply a specific issue with Facebook itself.
I’ll check more topics about it and if I find something I will post it in this topic.
Thank you!
Normally the theme doesn’t interfere with the sharing part in any way. It’s all handled by the SEO plugin used to load the required meta tags https://prnt.sc/C5m0QQLzuiVV If those meta tags are loaded the sharing across all socials usually works fine.
I tested a post from your website with the Facebook debugger, it looks fine https://prnt.sc/M_eXLdN7NArv
I tested sharing directly from the website, it looks fine https://prnt.sc/T7RtR0AlnbFB
I tested sharing on WhatsApp, looks fine https://prnt.sc/f-8Sk4fPSUkZ
From what I see it appears to be working correctly.
Thank you!
I solved it by switching to a different theme.
That solved the sharing issue, so I had clear forensic proof that it was not a server problem, Apache, permissions, the firewall, or any other excuse. It simply did not work. And if the people who built it cannot make it work, then the sensible choice is to change it.
Hello,
I have noticed that the 403 error problem when sharing on Facebook has become more and more frequent lately and does not seem to be related to a specific theme, it appears similarly on most themes.
Most likely, it is a recent change in Facebook crawlers or the way they access and validate shared content.
https://developers.facebook.com/community/threads/2400191473830317/
https://developers.facebook.com/community/threads/825654679324994/
https://developers.facebook.com/community/threads/1053535300291870/
https://www.youtube.com/watch?v=m1k2yl9rEwQ
https://sitesos.ro/eroare-403-facebookexternalhit-waf-rezolvare/
I am experiencing a persistent Facebook Sharing Debugger / Open Graph issue on a website using the Newspaper theme by TagDiv:
The Facebook Debugger consistently returns HTTP 403 and fails to properly retrieve Open Graph metadata from article pages.
Before suggesting generic hosting/firewall checks, please note the following:
Technical context:
What has already been verified:
Important observation:
Another WordPress site (mine, personal) hosted on the exact same server successfully returns proper Open Graph data and is scraped correctly by Facebook.
This strongly suggests the issue is related either to:
The Facebook Debugger currently retrieves incomplete OG data and sometimes only partial metadata such as:
Could you please provide technical insight specifically related to Newspaper/TagDiv behavior with Facebook crawlers, rather than generic hosting or firewall suggestions?
Thank you.I am experiencing a persistent issue with Facebook sharing/scraping on my website serenissima.news, which uses the Newspaper theme by TagDiv.
I have already performed a deep cleanup of the database and verified the server configuration. Before suggesting the usual “contact your hosting provider to whitelist Facebook in the firewall,” please consider the following:
I am the hosting provider. I own and manage the server (DirectAdmin based).
The firewall is NOT the issue. There are dozens of other websites on the same server (same IP) that share perfectly on Facebook without any blocks.
The issue is site-specific. Only the installation using the Newspaper theme is failing to provide the correct metadata or is being blocked/rejected during the scrape.
What I have checked so far:
Metadata: Standard OG tags are present, but the Facebook Debugger is not pulling them correctly.
Plugins: Performed a cleanup of caching plugins (WP Super Cache removed) and optimized the wp_options table.
Isolation: As mentioned, other sites on the same server work flawlessly, ruling out any server-side IP blacklisting or Firewall (CSF/LFD) interference.
I suspect there is a specific conflict within the theme’s header output or a built-in SEO/Open Graph setting in TagDiv that is clashing with Facebook’s crawler.
Please provide technical insights that don’t involve “whitelisting” as that has already been ruled out.
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.
in Newspaper tagdiv template the share button to facebook is not working well in mobile It opens the facebook app but not sharing the post.
When using the desktop version it works well.
Please check this post in mobile – IOS:
https://haipo.co.il/item/623610
Hi,
Thank you for sharing this with us. I have forwarded the information to our development team, and they will take a closer look.
We appreciate your time and for bringing this to our attention.
Thanks again!
