A blank screen means PHP is either crashing or not running. What version of PHP is installed on your server?
ACK! Been busy working on said client site as there was a SUPER strange issue; perhaps you could forward it to the powers that be.
There was a web-user writable copy of a previous client’s wp-config.php file that was two directories back from the existing client’s website directory.
I am kicking self for having bad server permissions which would have prevented this, but interesting to note that the vanilla install was going back so many directories.
Thanks for letting us know what it was!
… all the same, interesting that the vanilla install was going back one directory further than the install itself…
How exactly did you do the install? Was it through the hosting provider’s installer or a third-party package?
Install in three parts:
a:ssh to server and change to website install directory
b:wget "ww.wp.xz.cn/latest.tar.gz" --no-check-certificate;tar -xzf latest.tar.gz;mv wordpress/*;rm -rf wordpress xmlrpc.php
c:use browser at domain for website directory
It was via an ssh shell and a browser.
Edit: forgot chown -R www-data:www-data *
And yet wp-config.php would up in a directory different than where it is if you were to download WordPress from https://ww.wp.xz.cn/download/ ?
that is not correct; let me clear it up.
I had put a backup copy in the parent directory of the install. This was a mistake on my part which was compounded by it having web-read/writable permissions outside of where it should have.
ie: 100% MY FAULT, NOT WORDPRESS!
Ah, good. I’m confused then, what was the problem?
/dir/www/blog/
/dir/www/blog/website-a/wp-config.php
/dir/www/blog/website-b/wp-config.php
/dir/www/blog/website-c/wp-config.php
I have 3 copies of WordPress running perfectly fine.
I copy the wp-config.php from website-b to /dir/www/blog/ for ‘backup’, without renaming it [mistake on my part]
Install fresh WordPress at /dir/www/blog/new-site/
The fresh install would read the previously configured wp-config.php that was in the directory below it. This was confirmed as the href links on the new-site/wp-login.php page had were set to website-b, not new-site.
…hope this helps to clear up the mud puddle i made!
Oh! That’s normal, sort of. WordPress is designed to look look one directory higher for wp-config.php as a way to “hide” it.
We generally recommend keeping separate installations in subdomains websitea.example.com, websiteb.example.com, etc, rather than subdirectories for this reason (and a few more).
