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.

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.

Hi,
thank you for your reply.

I understand that Facebook has recently changed some crawler behaviors, however the issue remains isolated specifically to this Newspaper installation.

The same server infrastructure, PHP stack and Facebook crawler access are working correctly on many other WordPress websites hosted on the same machine, which strongly suggests a compatibility issue related to this specific setup.

At this point we will proceed with a migration to a different theme architecture.

Thank you for your time.

Hello everybody.
I’m experiencing the same problem: when Yoast SEO is enabled, the “save” icon spins and spins and never stops.
If I refresh the page, the system alerts me about the losing the modifies, but it already saved it, without the confirmation (Success).

Sorry for my bad english, I’m italian.
I saw that this thread is from may 2020. Do you have found a solution?
My system is up to date.

Thanks.
Roberto