-
- 8 Posts
I installed the software on another server and go it to work.
The installation was successful however, when I got ready to
login at the mydomain.com/manager/ location it get a 500 internal
server error. I assume this mean a permission is worng somewhere,
but where?
Any help is appreciated?
-
- 8 Posts
Here is my server information.
Web Server:
----------------
PHP version: 4.4.0
MySQL version: 4.1.13-standard
Operating System and version:
Apache version: 1.3.33 (Unix)
Browser/Client:
-----------------
Browser name and version: firefox 1.0.7
Operating System and version: Winxp Home version 2002
I’ve gotten that twice and both times it was a bad .htaccess file. The one in Manager has to turn mod_rewrite off.
Was it a fresh MODx install, or did you try to copy over your exsiting install to a new server?
Did you install version 0.9.0?
I’ll go with Susan’s guess on the .htaccess not being supported on the server. Got that myself last night in fact.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
- 7,075 Posts
Good to know Zi, but strange... I had only renamed the one in root and it just worked... I changed the one in /manager but when you check it it contains a Rewrite Engine Off directive... Anyway, what is the point of having SEF urls in the backend ?
.: COO - Commerce Guys - Community Driven Innovation :.
MODx est l'outil id
-
- 302 Posts
The .htaccess file in the manager turns OFF the rewriting so it doesn’t mess up the backend. It isn’t creating SEFURLs for the backend.
Standard Disclaimer
I could be totally wrong.
-
- 7,075 Posts
Ok good to know thanks a lot
.: COO - Commerce Guys - Community Driven Innovation :.
MODx est l'outil id
.htaccess files are inherited, so the /manager and all its subfolders inherit from the one in the / root. So if you want something different in a subfolder you have to explicitly put in another .htaccess file in that folder with what you want.