The config/ and files/ directories must be writable by your web server.

Permalink
Hi all,
please help me with this.

I am doing new installation of 5.1.0 RC1 Concrete on my Apache/2.2.3. CentOS server. I have uploaded files, chmoded files/ and config/ dir (tryed 755 & 757 & 777). Any of those mods still give me error "not writeable" and instalation won't procede.

---

Also, I get "Search indexing requires the mbstring and iconv PHP extensions, and PCRE support." but in my phpinfo() I see all of those extensions enabled.

PHP version is 5.1.6

I really appriciate any help I can get. Thank you.

View Replies:
eOne replied on at Permalink Reply
Same problems with this version too.

I must mention that I have virtualmin installed on server so if someone know if I have omit something in setup ...
ScottC replied on at Permalink Reply
ScottC
If you can, try using php version 5.2.6. I have always ran c5 using this version and aside from upload issues I really haven't had any problems.
eOne replied on at Permalink Reply
That I believe would be little bit of problem. Also, for fact I know concrete5 is working with this PHP version as I have another site on almost the same server configuration.

I have tryed these concrete setups: 5.1.0RC1, 5.1.1, 5.2.0RC1 and they all fail.

After trying 5.2. all is messed up, images are not shown not even on this startup install page.

examples:
http://simundza.com/510RC1/
http://simundza.com/511/
http://simundza.com/520RC1/

these folders contain only unziped concrete instalation files. config/ and files/ are 777 and html*.py is 755 as requested.

---
I have tryed and restored backup of other, working site, and retrieve it on this server. It is working here too.
This means it is probably something with installation process of concrete itself or human error (more likely :D)

any ideas anyone?
eOne replied on at Permalink Reply
here is what my provider found:

if you change:
if (defined('MULTI_SITE') && MULTI_SITE == 1) {
define('ASSETS_URL_WEB', BASE_URL);
} else {
define('ASSETS_URL_WEB', DIR_REL);
define('MULTI_SITE', 0);
}

into
if (defined('MULTI_SITE') && MULTI_SITE == 1) {
        define('ASSETS_URL_WEB', BASE_URL . DIR_REL);
} else {
        define('ASSETS_URL_WEB', DIR_REL);
        define('MULTI_SITE', 0);
}

and


# Path to the base directory of THIS install
define('DIR_BASE', dirname($_SERVER['SCRIPT_FILENAME']));

into
# Path to the base directory of THIS install
define('DIR_BASE', dirname($_SERVER["ORIG_SCRIPT_FILENAME"]));


instalation can procede as no errors are reported anymore.
andrew replied on at Permalink Reply
andrew
very interesting...

To be honest I'm not sure the first set of changes are necessary....but it looks to me like the second might be. Perhaps the server places what we're expecting to see in script_filename in the orig_script_filename server variable...
eOne replied on at Permalink Reply
help please.

I have tryed upgrading 5.2.0.RC1 fixed as mentioned before into latest 5.2.0. version and everything broke down.

some folders cannot be found and many other errors.
as I've left it in maintenance mode, there is nothing to see. But if you want me, I can try to reproduce it again.

any advices ?