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

2020-01-07 Thread Italo Vignoli
Hi William, On 1/4/20 4:19 PM, William Gathoye (LibreOffice) wrote: > The concrete impact is that the Jetpack control panel of the extension > cannot be used at all. I have just connected to the french blog from the hotel business center, and I have loaded Jetpack control panel without any

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

2020-01-05 Thread William Gathoye (LibreOffice)
On 04/01/2020 16:19, William Gathoye (LibreOffice) wrote: > This blog will need to be redone in all cases. :) Rereading this sentence now and it appears it can be perceived as a bit harsh. It wasn't meant to. For those of you who begin to know me, it's not in my nature to try to be purposely mean

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

2020-01-05 Thread Guilhem Moulin
On Sat, 04 Jan 2020 at 16:19:08 +0100, William Gathoye (LibreOffice) wrote: > This blog will need to be redone in all cases. :) While I do thing we should try to serve these resources ourselves, this is a priori a trivial change (JQuery and fonts are no-brainers at least), and I think it's

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

2020-01-04 Thread Guilhem Moulin
On Sat, 04 Jan 2020 at 16:19:08 +0100, William Gathoye (LibreOffice) wrote: > On 04/01/2020 16:00, Guilhem Moulin wrote: >> On Sat, 04 Jan 2020 at 15:10:42 +0100, William Gathoye (LibreOffice) wrote: >>> Content Security Policy: The page’s settings blocked the loading of a >>> resource at >>>

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

2020-01-04 Thread William Gathoye (LibreOffice)
On 04/01/2020 16:00, Guilhem Moulin wrote: > On Sat, 04 Jan 2020 at 15:10:42 +0100, William Gathoye (LibreOffice) wrote: >> Content Security Policy: The page’s settings blocked the loading of a >> resource at >>

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

2020-01-04 Thread Guilhem Moulin
On Sat, 04 Jan 2020 at 15:10:42 +0100, William Gathoye (LibreOffice) wrote: > Content Security Policy: The page’s settings blocked the loading of a > resource at > http://fr.blog.documentfoundation.org/wp-json/jetpack/v4/rewind?_cacheBuster=1578146864121 > (“connect-src”). What's the concrete

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

2020-01-04 Thread William Gathoye (LibreOffice)
On 04/01/2020 15:10, William Gathoye (LibreOffice) wrote: > > If you have an account on the FR WordPress and you go at [1], if you try > to disable this CDN, you get the following CSP errors as well. Correction. Actually, we don't need to disable anything in the extension to notice the errors,

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

2020-01-04 Thread William Gathoye (LibreOffice)
On 04/01/2020 15:04, Guilhem Moulin wrote: > On Sat, 04 Jan 2020 at 13:43:46 +0100, William Gathoye (LibreOffice) wrote: >> An incident happened between yesterday evening and today (now). > > The CSP was last changed on Thu Jan 2 round 03:30 UTC, so — assuming the > images resources didn't

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

2020-01-04 Thread Guilhem Moulin
On Sat, 04 Jan 2020 at 13:43:46 +0100, William Gathoye (LibreOffice) wrote: > An incident happened between yesterday evening and today (now). The CSP was last changed on Thu Jan 2 round 03:30 UTC, so — assuming the images resources didn't magically moved to .wp.com — the regression is actually

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

2020-01-04 Thread William Gathoye (LibreOffice)
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

[libreoffice-website] WordPress broken images [urgent]

2020-01-04 Thread William Gathoye (LibreOffice)
Hello everyone, An incident happened between yesterday evening and today (now). All images inserted into all blog posts of the WordPress instance (especially the French version) cannot be loaded any more. It appears the images are actually being mirrored on the WordPress CDN (https://i1.wp.com)