No config.inc.php

Hi. I have discovered that the installs of revo 2.0 that I have done recently do not have a config.inc.php

I have been through several iterations of installs of evo 1.04 revo 2rcn and more recently the released 2.0.

The earlier installs of revo that I did I followed ’beginning setup’ from
http://svn.modxcms.com/docs/display/revolution/Fresh+Installation

which has a paragraph about verifying 6 steps to do with ensuring directories are writeable and creating a blank config.inc.php

On more recent installs though I have referred to the more recent doc http://rtfm.modx.com/display/revolution20/Basic+Installation which only suggests doing this if I get a blank screen, which I do not - so I assume the install is sorting this stuff out for me.

Subsequently though I have discovered I have no config.inc.php and one of the sites became inaccessible. So it seems to me that the stuff about ensuring directories are writeable and creating a blank config.inc.php are essential pre-requisites but are not being indicated as such in the documentation - or have I got something wrong here?

Yes, you need your core/config directory writable (or at least a writable, blank core/config/config.inc.php file) before install, although setup should catch the core/config/ not being writable.

Thanks - but that’s kind of my point - that setup doesn’t seem to be catching it, and the doc doesn’t state that you have to do this.

I’ve figured out what I need to do but I’m just flagging that if I follow the letter of the documentation I end up with an install that is incomplete and potentially wobbly - without it being flagged as such.

Just done the third install in as many hours and scrupulously went through making sure directories were writeable and that I had a blank config.inc.php - also writeable

Install went very smoothly and at the end I have a working server with clarity installed but still a blank config.inc.php

Apart from anything else I need the $site_id from this file so I can use provisioner.

Any suggestions?

That’s really odd and in many dozens of installs, I’ve never seen it.

Did you move the core and/or use the advanced distribution?

Are the four config.core.php files correct?

They are in:

§ MODx root directory
§ /manager/
§ /connectors/
§ /setup/includes/

I seem to remember that the default perms on config.inc.php don’t permit reading by any user other than your webserver user, when you say you open it and its blank you may need to set the perms so that the user you are doing this from can read the file.

Thanks Bob. No - just the standard distribution, but I think I will try again with a fresh copy just in case mine got corrupted somehow.

Not sure what you mean by did I move the core. I’m installing on Mamp on OSX 10.6.4. I unzipped into my downloads directory then copied and pasted the expanded fileset to where I want them to be. I am assuming that there are no issues with hidden files that wouldn’t get copied in this manner, but maybe I’ll unzip in place next time.

The four config.core.php files are there and each 4KB in size and I haven’t changed them in any way.

Anyway - I’ll give it another go.

Oh - and while I was writing I picked up the response from shamblett. Thanks for the input but I set it to read & writeable by all (having created a blank file) and it is still writeable by all and size zero.

I’ll try again with a fresh install image.

Revolution allows you to move the core out of the standard location. I was wondering if you had done that. Obviously not, so that’s not the issue.

I meant for you to check the contents of the four config.core.php files to make sure that they all have the correct core path in them.

Right - so I downloaded a fresh install zipfile. I dropped the db and user and created a new db and user. I deleted all the files from within /root of the install, unzipped the install in place into a new directory, renamed to same as old. I amended directory perms to writeable and created a blank config.inc.php and made it writeable.

When I ran setup it defaulted to doing an upgrade install - which it did last time too. Both times I changed to a fresh install but I just wonder what makes it think it is an upgrade when I have deleted the db and all files.

Anyway, as I say, I ran as a fresh install. All went smoothly and I ended up with an apparently good modx install but still with a blank /core/config/config.inc.php

I looked at the error log within the manager and there was quite a bit there. What I found strange was that it had continuity across my various installs. Again I find this odd when I have deleted the files and the db each time. How can this be?

Anyway I attach a copy of the error log (personal info edited). Perhaps someone can shed some light for me?

When I ran setup it defaulted to doing an upgrade install ...

If its doing this its ’finding’ a config.inc.php file and assuming you are upgrading rather than doing a fresh install, so it does exist somewhere, this is also why your site was working OK. It definitely seems to be your local machine somehow.

renamed to same as old..

What happens if you don’t do this, i.e. a completely new install in completely new area.