temp has to be CMOD 777 ?
Posted: Wed Apr 10, 2019 9:48 pm
Hi there
I have a CMSMS 2.2.9.1 website that uses two domain names. I had to remove the root definition in config, so that it works well.
But...
When I set config CHMOD lower then 444
the website goes offline (only with the second domain name)
blank page with Permission denied in config.php on line 210 (etc...) warning
I set it to 444, the warning changes to
set write permission to temp/templates_c and cache
(only with the second domain name)
and only when I set those two folders to CHMOD 777 the webiste comes up with the second domain name.
But during all this, the first domain stays working. I can clean caches, reset paths, this all changes nothing.
And there is nothing set regarding domain name in htaccess
I dont understand why the two domainnames are treated differently. Both lead directly to that hosting and in that hosting to the same directory. There is nothing different about them.
No folder should be CHMOD 777 for security reasons, isn't that right?
I have a CMSMS 2.2.9.1 website that uses two domain names. I had to remove the root definition in config, so that it works well.
But...
When I set config CHMOD lower then 444
the website goes offline (only with the second domain name)
blank page with Permission denied in config.php on line 210 (etc...) warning
I set it to 444, the warning changes to
set write permission to temp/templates_c and cache
(only with the second domain name)
and only when I set those two folders to CHMOD 777 the webiste comes up with the second domain name.
But during all this, the first domain stays working. I can clean caches, reset paths, this all changes nothing.
And there is nothing set regarding domain name in htaccess
I dont understand why the two domainnames are treated differently. Both lead directly to that hosting and in that hosting to the same directory. There is nothing different about them.
No folder should be CHMOD 777 for security reasons, isn't that right?