1 gerardp Dec 06, 2018 19:55
3 gerardp Dec 07, 2018 04:28
Hi Francois,
What would my life be without you kicking my ass every once and a while?
Hahaha kind of love it by now
If I had seen a blue box with the word support, believe I would have clicked on it...
We host is site ground, and I'm running php 5.6.
I took the site off-line with $maintenance in basic_config because as far as I know everybody could see screenshot one.
The URLs are standard, I.e. blog.gerardprins.com/installer/index.php.
All others generate a 500 error.
And just to clear that one up: I was at no time blaming B2evo; i am fully aware that this is server side.
Which is why your help is even more appreciated
THANKS
4 gerardp Dec 07, 2018 16:22
- Hi Francois
- Problem fixed
- As it turned out, a whole bunch of directories had 775 permissions on them even when cpanel was showing 755.
- I am clueless why, but my hosting service fixed it and the install finished in seconds.
- As I have confirmed once again, bevo install is a very robust process.
- Thanks for the hard work!
- Looking forward to the next time you kick my butt
- D
5 fplanque Dec 07, 2018 16:54
@gerardp I'm glad it's fixed.
You should change the default file permissions on this page: https://b2evolution.net/man/file-settings
so you don't get the same problem again next time.
6 amoun Dec 07, 2018 21:24
As I've had the same problem .i.e. permissions needed changing, although this only happened doing an auto upgrade, can you confirm that the default file/folder settings as per your link are the ones to keep
- All boxes checked
- Folders 775
- files 664
In between we have added a blue box on the "new support request" from. You ignored most of it.
Your screenshots show no URLs. So it's guesswork and I hate it. I am assuming the last screenshot is what you see when you try to access the install directory to finish your upgrade. ---> Name of your webhost?
Your screenshot seems to show correct permissions yet this error is still generated... by the CPanel on your webhost. NOT by b2evolution. ---> have you asked your webhost why that error occurs despite correct permissions?
Is there a way to check owner and group of files in addition to just the permissions (ie 755) ?