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!
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,
The issue is not with WordPress or the theme.
The Facebook Debugger shows a 403 error, which means your server is blocking Facebook’s crawler (facebookexternalhit / Facebot).
Because Facebook can’t access the page, it cannot read the title or image, so previews don’t show.
Fix: ask your hosting provider or check your site’s firewall/CDN (e.g. Cloudflare, Wordfence) and whitelist Facebook’s crawler or disable rules blocking bots.
After that, use Facebook Debugger → “Scrape Again.”
My posts on Facebook are not showing image or posts title in recent days. Domain name is http://www.topic.ie and I am running the latest version of WordPress and Newspaper theme. I’ve checked Facebook Debugger and I get the message: Response Code 403. What is wrong?
Hi,
I just checked, and it appears that there is a 403 https://prnt.sc/putozxRijzqD – https://prnt.sc/eil-LOVtn3Ew (seems to be from Cloudflare https://prnt.sc/qtJsei3ubT23 – https://prnt.sc/Ro5cfud4H3V6 ). Could you exclude the admin-ajax request from being blocked?
Hi Calin, thanks
unfortunately i can’t see your links at all, i get this message “{“data”:{“error”:”Imgur is temporarily over capacity. Please try again later.”},”success”:false,”status”:403})
any solution ?
Hi Calin,
thanks.
Besides i can’t see the png you provide (it opens me a page with the following text “{“data”:{“error”:”Imgur is temporarily over capacity. Please try again later.”},”success”:false,”status”:403}”), i succeeded deleting the code through incognito tab.
thanks
Hi, firstly. cant see your imgur`s >{“data”:{“error”:”Imgur is temporarily over capacity. Please try again later.”},”success”:false,”status”:403}
Second, yes. We have upgraded to php 8.3 and it went away.
Thanks
Hi,
That’s a bit unusual, because we use cloudflare for almost all our websites and demos, and there are a lot of theme users that use it as well.
Are you using any custom rules in cloudflare perhaps? Or you could try to create a rule to not block the theme ajax requests used for pagination.
Something like this:
https://community.cloudflare.com/t/admin-ajax-error-403/609324
https://community.cloudflare.com/t/wp-admin-admin-ajax-php-returning-a-403-error/424352
I suggest checking the rules first, you can pause them and check again. By default cloudflare should not cause such problems.
Thanks.
Hi,
Usually, this situation appears when something is interfering with the theme, please open the console and look if there are any 403 errors.
Sometimes it can be a plugin conflict, so if you want, you can make a test using only tagDiv plugins.
Thank you!
Hi,
Yes, it was fixed after installing the plugin.
https://s34.picofile.com/file/8486557126/Screenshot_2025_08_21_140342.png
Now I have a few questions:
How can I move the search button to the right? (shown with the blue arrow)
Why is the spacing between the menu items shorter at the end of the menu? (shown with the red arrow)
How can I move the “Login to account” text to the right? (shown with the green arrow)
How can I fix the spacing between the login icon and the shopping cart? (shown with the yellow arrow)
Thank you for your guidance.
Hi,
Please check the console when you hit the save button and see if there is an error. With right-click -> inspect -> console -> select the error in the tab network -> preview, you can see the cause and check the suggestion from here https://forum.tagdiv.com/topic/newspaper-theme-panel-settings-are-not-being-saved/ -> https://community.godaddy.com/s/question/0D58W00007ggvUDSAY/403-forbidden-error-not-sure-why
Thank you!
Dear Team, I am encountering a issue on my theme panel. I am not able to save theme panel setting. i am getting a error failed to load resource: the server responded with a status of 403 https://todaymyindia.com/en/wp-admin/admin-ajax.php?td_theme_name=Newspaper&v=12.7.1 Can you help me please to resolve this issue.
Hi, thanks for your reply. I set up Google map API and it works. Unfortunately I can’t open your imgur screens becaues of {“data”:{“error”:”Imgur is temporarily over capacity. Please try again later.”},”success”:false,”status”:403}
Hello,
A “403 Forbidden” error means that the server understands your request but refuses to authorize it, usually due to insufficient permissions. This is a client-side error, meaning the problem is usually with your access or settings, not the website itself, although it could also be a server-side issue.
How to fix the “403 Forbidden” error in 2025
Thank you!
My website https://sadaatimes.com/ when I open admin is perfectly work but when I goto website show 403 error
please resolve this issue this is a news portal website
Hello,
Thank you very much for your response and support.
I also appreciate your advice about checking the browser inspector — that was really helpful.
When I looked into it, I found that access to “/wp-admin/admin-ajax.php?td_theme_name=Newspaper&v=12.7.1” was returning a 403 error.
After some investigation, it turned out that the request was being blocked by the hosting provider’s WAF settings.
I’m sorry for the trouble caused due to my lack of initial investigation.
Thank you again for your assistance!
Hi,
A 403 status means “Forbidden”, meaning something is blocking the request. Here are the most likely causes and fixes:
– Security Plugins or WAF (e.g. Wordfence, Sucuri, Cloudflare)
– ModSecurity (Server Firewall)
– Incorrect File Permissions, file should be 644.
– Theme or Plugin Conflict, do a test using only the main theme and tagdiv plugins.
Thank you!
load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,wp-hooks&ver=6.8.1:5 JQMIGRATE: Migrate is installed, version 3.4.1
/wp-admin/admin-ajax.php?td_theme_name=Newsmag&v=5.4.3.3:1
Failed to load resource: the server responded with a status of 403 ()
Error Message:
Failed to load resource: the server responded with a status of 403 ()
Hi,
Please check the browser console for any errors. If you see something like this: https://i.imgur.com/iiBOHwP.png, head over to the Network tab, click on the error, and then check the Preview section to see what is blocking it.
It’s possible the issue is coming from your server host—maybe a 403 or 404 error. This forum thread has some helpful suggestions that might point you in the right direction:
– https://forum.tagdiv.com/topic/wp-editor-for-text-with-title-and-column-text-not-updating-content/
Thank you
Hi,
Please check the browser console when you open the content editor. If there’s an error like this: https://i.imgur.com/iiBOHwP.png, go to the Network tab, select the error, and then click on the Preview section.
The issue might be caused by the server host. I suspect it could be a 403 or 404 error.
Please review this topic for suggestions:
https://forum.tagdiv.com/topic/wp-editor-for-text-with-title-and-column-text-not-updating-content/
Also, make sure to clear/purge all cache, as caching issues can sometimes cause this behavior.
Here’s another thread with a similar error that might help:
https://forum.tagdiv.com/topic/err_http2_protocol_error-on-go-daddy-hosting/
Thank you!
