Friendly urls result in a 404 error

Quote from: sottwell at Aug 21, 2009, 12:02 PM

Here’s what mine looks like:

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

No trailing / in RewriteBase, and no leading slash in RewriteRule.

Yeah, Susan, I tried deleting the trailing slash in my RewriteBase, and it still works just as well - good call

still a no go here no matter what...
# For full documentation and other suggested options, please see
# http://svn.modxcms.com/docs/display/MODx096/Friendly+URL+Solutions
# including for unexpected logouts in multi-server/cloud environments

Options +FollowSymlinks
RewriteEngine On
RewriteBase /new

# Fix Apache internal dummy connections from breaking [(site_url)] cache
RewriteCond %{HTTP_USER_AGENT} ^.*internal\ dummy\ connection.*$ [NC]
RewriteRule .* - [F,L]


# Rewrite domain.com -> www.domain.com -- used with SEO Strict URLs plugin
#RewriteCond %{HTTP_HOST} .
#RewriteCond %{HTTP_HOST} !^example\.com [NC]
#RewriteRule (.*) http://example.com/$1 [R=301,L]

# Exclude /assets and /manager directories from rewrite rules
RewriteRule ^(manager|assets) - [L]

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

# Reduce server overhead by enabling output compression if supported.
php_flag zlib.output_compression On
php_value zlib.output_compression_level 5

You can try turning off MultiViews. I know it’s been a problem with some hosts in the past.

Just change "Options +FollowSymlinks" to "Options -Multiviews +FollowSymlinks"

still no go...this is crazy

Have you checked the apache error log to see if it yields any clues?

Did you receive my email? I sent it to [email protected]. I don’t know that I can really help, but I’d be glad to try.

Why don’t you just move the site to the root of the domain?

Is there any advantage or reason of you having the MODx site stored in /new/ ?

Just tipping another thought in the pot

have a look at the template and the base href setting - have you got one and is it set correctly?

Hey guys,

This should be closed. The problem was solved, and I thought he was coming back to mark it as such.

The error was a mistake in the .htaccess file name, so none of the contents of that file were being read.

Aaron, good call - I’d made the same recommendation about moving the site to the root, which is what ended up happening, and everything went well.

If a moderator sees this and wants to mark it as solved (or delete it, since it turned out not to be a modx-related issue at all), go for it.

That’s great news and thanks for letting us know the fix.

I will mark this as Solved.