"Object not found" when accessing Sub-Page (Pretty URLs, mod_rewrite)

Permalink
Hey guys.

We recently "finished" out site and put it online. It was online before but we moved it from a subdomain to the real domain.

After doing so, we're experiencing some minor issues with accessing Sites via PrettyURLs path.

Our sitemap is not reachable using its PrettyURLs-Name "sitemap". But using the good old cID=XXX works very well.

It seems like C5 isn't even interested in doing something - the "Object not found" is directly delivered through the server - it's not my page_not_found.php.

Has anyone ever had this issue?

Could it be mod_reqrite related? (actually unedited):
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME}/index.html !-f
RewriteCond %{REQUEST_FILENAME}/index.php !-f
RewriteRule . index.php [L]
</IfModule>
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/rss+xml


BTW: Another bug that occures sometimes is that after creating a new Sub-Page to home, it was not accessable through the "Visit"-Button in the backend - probably due the same issue.

Thanks!
Slap

SlapY
 
mhawke replied on at Permalink Reply
mhawke
Can you post the exact error message that refers to the 'Object not found'?

Also, things I check after I move a site.

1) Clear concrete5's cache.
2) Turn off all caching until it's working.
3) Turn off Pretty URL's and then turn them back on again.
4) Delete all files below '[root]/files/cache' leaving the cache folder in place but empty.
SlapY replied on at Permalink Reply
SlapY
Hay MHawke!

Thanks for your reply, I cleared the cache and toggled Pretty URLs right before my post.

But I think we've just found it.

Seems like my boss uploaded a "sitemap.xml" and a "sitemap.xml.gz" for Google.

I think that caused the problem.

After I changed the .htaccess to this
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^(.*)$ - [L]
RewriteRule ^(.*)(\.html|\.php)$ $1 [R=301,L]
RewriteRule ^(.*)$ index.php/$1 [L]

, according to the Best Answer over here:
http://www.concrete5.org/community/forums/customizing_c5/mod_rewrit...

it spit out the XML file directly.

I now renamed the page to "site-map" and the error disappeared.

But we're still having some issues. Still investigating.

Thanks!
mhawke replied on at Permalink Reply
mhawke
I'm no expert in .haccess but that answer you linked to was trying to solve a very specific requirement. If you don't have that requirement, I think that solution is overkill. When I'm in trouble, I always try to simplify things first. I would rename your existing .htaccess file for future reference and let c5 create a new, clean .htaccess file by toggling Pretty URLs. Only then would I start trying to solve issues that crop up.