Friendly URLs not working

Hmmm.... dunno if it works with subdomains... haven’t tested that thoroughly, but I bet it will by tweaking the rewrite rule a bit. Someone should have an answer soon.

Try this:

The RewriteRule "/var/CMS/MODx" part is defnitely not right as that’s a filesystem path and mod-rewrite works on URLs.

Most of my development sites are setup using subdomain, but never have any problem in what so ever. It might be a different configuration from your host. DO they have like KB or FAQ? Try to ask support from them, whether do they know any known problem if you setup a subdomain the way you use it. I might be wrong though, it might not be the problem from the server. BUt it won’t hhurt to give it a shot

Okay, I finally tracked it down. Turns out my .htaccess file wasn’t being processed at all! Once I added the following to my httpd.conf file, the friendly URL’s began working as expected.

<Directory "/var/CMS/MODx">
Options FollowSymLinks
AllowOverride All
</Directory>

Thanks for your help.

Aha! That would’ve been a bit of a show stopper. Glad you got it sorted out

I am having a bit of trouble with friendlu URLS. My problem seems to be a bit different than any of the other posts. I have a 1and1 home hosting account, and I have my domain’s destination set to /staging. I’m pretty sure that this is the equivalent of setting the root of the webspace to the /staging subdirectory. When I enable FURL’s and try to access a web page, I get a 500 error : internal server error.
I renamed the .htaccess file. I tried putting the .htaccess file in the root of the webspace or in the /staging sub-dir.

Quote from: joshlfisher at May 24, 2006, 12:13 PM

I am having a bit of trouble with friendlu URLS. My problem seems to be a bit different than any of the other posts. I have a 1and1 home hosting account, and I have my domain’s destination set to /staging. I’m pretty sure that this is the equivalent of setting the root of the webspace to the /staging subdirectory. When I enable FURL’s and try to access a web page, I get a 500 error : internal server error.
I renamed the .htaccess file. I tried putting the .htaccess file in the root of the webspace or in the /staging sub-dir.

See if the 500 error is related to issues described here and in several other posts regarding the php directives and other extras in the .htaccess file.

I actually got it working.
I just rewrote the .htaccess file:

Old wording:

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

New Wording:

RewriteEngine on
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ /index.php?q=$1 [L,QSA]

Changes:
Changed uppercase On to on
added line: RewriteBase /

Just a note for anyone having trouble with FURLS: I got it working on my server by commenting out the 2 lines:

php_flag zlib.output_compression On
php_value zlib.output_compression_level 5

I tried this after checking the httpd log ...did not have time to find out how to change the Apache conf to support these directives.

Quote from: joshlfisher at May 25, 2006, 12:14 PM

I actually got it working.
I just rewrote the .htaccess file:
...
Changes:
Changed uppercase On to on
added line: RewriteBase /

You actually made one more change: added a / before index.php
Both options work: the rewriteBase and the /index.php. I don’t know if adding both will cause some trouble later on. Anyway, this very posting helped me solf the problem I was working at for 3 nights to get MODx working on my subdomain. So, thanks for posting.

None of those syntax changes change a thing, people developing on their test boxes should check the default directory settings and make sure you setup the default dir restrications, otherwise the rewriting engine won’t be activated.

<Directory />
...
AllowOverride All -> or something less restrictive but you want to be able to override the .htaccess
</Directory>

Thought this might help a few folks out there to save some time.