mmxxi

Thanks a bunch.

I figured it would be something like that. But wouldn’t even know where to look for the right tags.

Thank you Diane.

I should have mentioned i was referring to Twenty-Twenty-One, where it’s not actually a block by default i don’t think. So that css would have to be added somewhere else.

I’m not entirely sure yet if i’ll be using Twenty-Twenty-Two, because it was a little broken when i first tried it. But i see that the full site editing makes it real easy to change indeed.

• This reply was modified 2 years, 6 months ago by mmxxi.

At least they’re putting in genuine effort. I only get links to general support articles, depending on keywords in my questions probably. This guy has SSL issues, here’s an article about SSL!

Support suggested adding these lines to the htaccess file:

RewriteEngine On
RewriteCond %{HTTP:X-Forwarded-Proto} !https
SetEnvIf X-Forwarded-Proto "https" HTTPS=on
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

But this didn’t solve anything for me. I already had a Force SSL option enabled as provided by the hosting, so it shouldn’t actually make a difference.

Maybe WP’s scripting just manages to bypass the rules.

@pftsoi It could of course be that you were dealing with a different issue that had the same effect. Because the error message is not the same.

I have attempted to do so as well, but well lets just say it’s pretty clear that i went with the budget option. And it’s nighttime here now anyway.

I have no idea, but that’s very interesting.

Gives us a workaround at least.

Would prefer to keep using a subfolder though!

Is WP to blame here, or the hosting?

Dat is dan wel heel toevallig. Aangezien het lijkt of we de enige zijn met dit https probleem in de editor en we zitten allebei bij Vimexx. Ik had al contact opgenomen, maar helaas is het weekend.

@jvdbol Zit je toevallig op Vimexx?

Makes sense. The error (for me) is caused by a http request on a https site. If the site is already http-only, then there is no error.

But we should really use https/SSL in 2022.

Maybe something can be inferred from the htaccess?

This is what WP has created for me:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /wp/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wp/index.php [L]
</IfModule>

Not for me, and i don’t think i’ve made custom changes.

It look like this, even if i let WP 5.9 create a new one:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /wp/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wp/index.php [L]
</IfModule>

Yes i will,

But are we in agreement that something in Worpress’ coding is doing this, or can it still be something else? Could the ‘Force SSL’ option of my hosting be lacking?

Also note that i have a topic about it here:
https://www.ads-software.com/support/topic/site-editor-loading-insecure-resource-http/

Seems it is not related to Twentig, at least for me. But something in WordPress’ coding causing it to try and load the editor without SSL (on my hosting).

Also, installing a SSL plugin does not help. Not surprising i guess since there isn’t any user content to fix, and the hosting is already forcing SSL.

OPcache disabled, browser cache cleared.

It’s not WordPress specific hosting.

Varnish is for premium users only, and RedisCache has not been enabled.

It’s always been using/forcing SSL, and the site editor didn’t even exist before this. So I’m not sure why any cache would be the issue. Did i mention it’s the same with a clean installation and database (in a different subfolder)? :/

• This reply was modified 2 years, 9 months ago by mmxxi.