config.inc.php problems on upgrade to 1.0.1

The above is the error I am getting on an upgrade to 1.0.1 I have never seen this error before on any MODx version, install type, or server environment. I have had 0.9.6.3 up and running for a while in an IIS environment running DotNetPanel. I decided it was way past due for an upgrade, but this damn error is in my way. I have tried making it writable in the back end, but it still shows it as not writable. The hosting co is looking into it, but it doesn’t look good.

Is there some kind of work around I can do on my end?

Thanks in advance

http://modxcms.com/forums/index.php/topic,32957.0.html

The third post in the above thread looks promising. If my hosting co can’t solve this problem, I will give it a try.

Ask your web host to right click the file in windows and unselect the read only option.



Aaron

I tried that route, but I guess the weekend crew is stupid. I went ahead and tried the method from the link I gave in my second post, but I set the perms to write. It worked, and I can’t believe it. I am now in the manager.

Damn it, now I have a 500 error. This should be one the hosting co can solve.

See if anything here helps (though much of it is not for IIs): http://bobsguides.com/modx-installation-faq.html

Ya, thanks Bob. I have turned to your great guides many a time. I really appreciate the time you have taken to create/maintain them, as they are really helpful. I have a feeling my current issue is a permissions deal. I will let the hosting co take a crack at it, since I am not an IIS guy.

Quote from: deniro0311 at Oct 24, 2009, 07:26 PM

Ya, thanks Bob. I have turned to your great guides many a time. I really appreciate the time you have taken to create/maintain them, as they are really helpful. I have a feeling my current issue is a permissions deal. I will let the hosting co take a crack at it, since I am not an IIS guy.

Thanks for the kind words. I hope you get it sorted.

No problem. My 500 error was coming from the ajax search snippet. I removed the instance that I was using, and the error is gone. I need to do a little trouble shooting to see why that was happening.