[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-website] WordPress broken images [urgent]

It seems like this is due to CSP (Content Security Policy).

In the meantime, as a workaround, disabling the use of WordPress CDN is
the way to do.

However, this feature is managed by the Jetpack extension and I cannot
change this setting because of a FetchNetworkError. [1]

Removing the CSP check, content referer check and CORS from Firefox,
does remove the CSP issue response, however, now, I'm not receiving any
answer and the setting still cannot be modified either. The
FetchNetworkError persists.

Can someone try to remove that Jetpack setting? Otherwise disable
JetPack completely? Disabling Jetpack will only break comment content
subscription, which isn't a big deal compared to the lack of images in



William Gathoye
Hyper<hack>tive volunteer for LibreOffice
Proud member of The Document Foundation
Member of LaMouette - French based association promoting ODF and LibreOffice

To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/website/
Privacy Policy: https://www.documentfoundation.org/privacy

[libreoffice-website] WordPress broken images [urgent]"William Gathoye (LibreOffice)" <william.gathoye@libreoffice.org>
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.