@mmxxi that’s a really good question 🙂
I’m about to ask my hosting about it, will let you know.
Thread Starter
mmxxi
(@mmxxi)
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.
Sometimes, I found that the white page was caused by Chroe Plugins, especially some
Tampermonkey Plugins, just close the plugins may be okey.
I think it is not about the subfolder problem, because installed wp in a subfolder.
Thread Starter
mmxxi
(@mmxxi)
@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.
@mmxxi exactly; @pftsoi as I wrote before I have no plugin at all installed, it’s a pristine installation; so while I agree that wp being in a subfolder shouldn’t change anything, since in my case it does it’s -at least- a starting point for trying and figure the issue out.
If I had to guess I’d say it’s something related to the SSL certificate installed by my hosting, but they haven’t replied yet to my query so… let’s hope and wait (for those who are in my very same situation).
Thread Starter
mmxxi
(@mmxxi)
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.
@mmxxi forcing SSL had not resolved for me neither; my hosting has just asked me to grant them administrator access to wp both in the root and in the subdir, to “further address the issue”. I will not waste time to explain them that I have just one installation, but so be it, I’ll do what they ask and get back if anything new comes out.
-
This reply was modified 4 years, 7 months ago by
Marks1973. Reason: * resolve -> resolved
Thread Starter
mmxxi
(@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!
This is the console error in Chromes’ inspector combined with the blank screen when clicking on te FSE link in the dashboard:
`Mixed Content: The page at ‘https://commppress.nl/camping/wp-admin/site-editor.php’ was loaded over HTTPS, but requested an insecure resource ‘http://commppress.nl/camping/?_wp-find-template=true’. This request has been blocked; the content must be served over HTTPS.
edit-site.min.js?ver=24578b0989e0620b2bc0a97a2cb08556:2 Uncaught (in promise) TypeError: Cannot destructure property ‘id’ of ‘(intermediate value)’ as it is null.
at K (edit-site.min.js?ver=24578b0989e0620b2bc0a97a2cb08556:2:12033)
at K.next (<anonymous>)
at Y (edit-site.min.js?ver=24578b0989e0620b2bc0a97a2cb08556:2:12469)
at Y.next (<anonymous>)
at redux-routine.min.js?ver=6c3ab278bc9641b6f62731e018a4449e:2:9334
VM108:1 XHR is klaar met laden: POST {PH3}.
The latest message from my hosting dates a couple of days ago. It must be quite an effort 🙂
Hello everyone,
my hosting provider kinda solved the issue adding the following line:
Header always set Content-Security-Policy "upgrade-insecure-requests;"
in subfolder’s .htaccess (outside BEGIN/END WordPress of course).
So, just to summarize the things to check (most of them are obvious):
- You should specify your subfolder in root’s index.php require statement
require __DIR__ . '/(your_subfolder)/wp-blog-header.php';
- Root’s .htaccess should be left as it is when WP creates it.
- Subfolder’s index.php should not have the
/(your_subfolder) part in its require statement.
- Subfolder’s .htaccess should contain the line I mentioned at the beginning.
- In WP Settings > General you should state your subfolder’s name in WP’s URL and not state it in website’s URL (as you normally would with a subfolder installation).
For those interested in delving into the .htaccess statement, here’s MDN link.
Cheers!
-
This reply was modified 4 years, 7 months ago by Marks1973. Reason: Formatting adjustments
-
This reply was modified 4 years, 7 months ago by Marks1973.
I am running a clean WordPress 5.9.3 install with no plugins or additions to the database on my local WampServer and yet I stil get the white screen when selecting Appearance and then Editor.
There is no htaccess file and all my other WordPress local sites are running fine using other themes and the same version of WordPress.
My site address is http://127.0.0.1/wordpresstest/ and my site is in the www/wordpresstest folder so why doesn’t the editor work “out of the box”?
So while using this theme and the 6.0 WP build I have noticed the excerpt does not show on the page (post type) even though there is a block to support it for design purposes.
Is this not possible. I also noticed the theme is HTML and not PHP so the old method to add it is not a thing. PLease help as I would like to use this data as a byline for a custom header I created.
I also had this error. My solution was to check .htaccess file. It was empty, so i added default WordPress code there and it worked:
# BEGIN WordPress
RewriteEngine On
RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress
