New Revo install - brick wall

I was looking for a "post all your newbie install questions here" thread, but didn't see it. If one exists, I'm sure this'll get moved there.

Here's the steps that work fine:

- unzip and upload

- rename ht.access tiles to .htaccess (in, I think, 3 places)

- talk to host, db is set up, confirm details

- reset permissions to 766 for several core directories as noted http://rtfm.modx.com/display/revolution20/Basic+Installation#BasicInstallation-PreInstallationChecks here.

- my host sublets from GoDaddy, so got full name of database instead of 'localhost'.

- Installation Summary is all green lights. hit 'install.' Watch it all unpack.

- next page has URL ". . . setup/index.php?action=complete", but displays only a 500 error "site temporarily unavailable."

__________________________________

I clearly have more troubleshooting to do, but I don't know where to start and am open to suggestions. Thanks in advance for pointers.




Unix server. Don't know what else is helpful re: it.

PHP 5.3.10.

Can you post your url? have you tried accessing the manager (www.sitename.com/manager) ?

Don't modify the .htaccess till after you get it up and running. You need to set the FURL's in the site settings before .htaccess is deployed. Rename .htaccess, login to the manager and change the site settings.

Then, re-enable .htaccess. If you still get 500 errors, disable the options in .htaccess and re-enable one by one to see what's wonky.

@blackflow - yes, manager gives the same 500 error;

URL is http://greathugethings.com/modx-2.2.2-pl/

@Frogabog - thanks for that suggestion - will knock down .htaccesses and try install again.

(I don't know if this matters, but when my host first moved to GoDaddy a couple of weeks ago, the .htaccess file that I had in my regular directory was a problem - they had to disable it to get my stuff to work correctly.)

.htaccess wonkiness always throws a 500 error in my experience. Every time I muk it up there's a 500 page either both at manager and site or just site. Either way, it's .htaccess doing the wonking.

You can load the .htaccess file with everything commented out, and then un-comment, see what happens.

On your main site, chances are you still need the .htaccess file for some reason. Just disabling it probably isn't the answer, but it depends on what you intend the root to do. Is there any site or other cms install in the root?

If you post the contents of your .htaccess files and define how your root site and root/modxSubfolder should work it might help.

***on my main site, it's not essential - it was there for ease of development, so that (for example) if I stuck ten images in a directory, It would be easy to grab the links via a browser. Just lazy.

***
???

Whatever *** is, if you put your images into an images directory on the root it'd be about as easy and won't muck up MODX at all. Still easily accessible. Then install MODX at the root. That way you won't have to modify the .htaccess at all to display the site as yourSite.com instead of yourSite.com/modxInstall

Additionally, once you get to working in MODX you can call any image rather easily by setting up a placeholder in the settings for the images folder in assets such as:

Then, when you want to call up an image from your images folder, all you need to do is insert the tag followed by the image file name itself rather than a full url.

Sorry. I meant *** to mean "this isn't what I'm really on about, and thanks for the input, and here's why that important thing (.htaccess) wasn't really important to me, even though I might want to learn more about it next week, once I get this install worked out'

SOLVED!

Putting this here so other people can learn from it.

When my host (who subcontracts from GoDaddy) set up the DB on my behalf, we entered one field that was called "DB name / User" and another that was called "Read-Only Username." The DB name was a cipher that would make sense to me (say, modx222) and the username was a human name (say, johnsmith).

When I set up my MODX install (and, later, a WordPress install), entering the credentials modx222 / johnsmith got me in the door and got the process started. But once the install was underway, MySQL rejected all hte installs b/c 'johnsmith' had read-only access.

The correct solution was to use

db:modx222
user:modx222

along with the secure password I'd set up.

Are you sure you want your DB credentials posted in a public forum?

Hopefully, those are not the real ones. If they are, you might want to change them.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html