Certain path always shows up as "page not found"
archard - October 9, 2007 - 17:03
I just moved my site from development on a subdomain to a live site, and now a path (called "recordings") simply will not work. Despite the fact that there is an alias set up for this path, it always returns as a "page not found" error. This should not happen because there is a node that exists with the correct alias set up and it worked fine on my development site. I have no idea what's wrong.
In addition, everytime i go
In addition, everytime i go the path "recordings" drupal adds a trailing slash to the url in addition to it showing up as a page not found error. This is very funky behavior and I have no idea why it's happening.
silly suggestion
in case it is just a case of gremlins...
i am assuming that the path being aliased still works (node/?), "clean" and "unclean"? if so, maybe take the alias out, then put it back? could be a stuck bit somewhere...
Did you ever get anywhere with this?
I am absolutely pulling my hair out with the same issue...
I have a node that should be at the path www.example.com/echo - I have the URL alias set up, the node exists, but I always get a 403 - Page Not Found.
More details:
I CAN access the page using the node path: www.example.com/node/344
I CAN access the page using the Drupal URL: www.example.com/?q=node/344
I CANNOT access the page using the alias: www.example.com/echo
I CANNOT access the page using Drupal alias: www.example.com/?q=echo
I CAN change the URL alias to ANYTHING ELSE (well, that I've tried) and it all works.
Here's an interesting bit: I have a view that takes an Term Name argument - if you pass a garbage term name, the view just shows an empty list. BUT if you pass in "echo" as the term name, you get the 403 Page Not Found error.
Same for a search: www.example.com/search/node/echo gives 403 Page Not Found
Yikes!
I have searched the database for all instances of the word "echo" and it simply does not occur except on the page that I'm trying to set up.
To make matters worse - I cannot reproduce this problem on my development platform - only on the production site, so I can't just start disabling modules willy nilly.
Any ideas greatly appreciated - I'm going out of my mind here 8^@
I had forgotten about this
I had forgotten about this issue and learned to live with it until you posted this. Then I decided to look into a bit more and found this node:
http://drupal.org/node/121366
Problem solved :) It was because there was a physical folder with the same name as the path that was giving me issues. It also explains why a trailing slash was being added on the 404 page.
thanks... but
thanks archard - how good that you found a solution to your problem after all these months!
Unfortunately, it didn't help me - my issue seems to be more widespread - ANY path that ends in the term "echo" on my site returns a 403 Page Not Found (note: 403 rather than 404).
For example, if you search for "echo", Drupal sends you to the path:
http://www.example.com/search/node/echo
which returns Page Not Found.
The log simply reports
type: "page not found"
message: "403.shtml"
I carefully checked all the paths on my server and there are no directories or files named echo. As I said, I can't reproduce this on my development server, so it's really hard to de-bug
Oddly, everything else works (well, everything I've tested), including any permutation (e.g., "echo_" )
In any case, thanks so much for looking into this again, and getting back to me. Perhaps I'll start a new thread since this seems to be a different problem.
Here's a lead...
Just found this:
http://drupal.org/node/164989
Looks like the mod_security settings for my host might be blocking "echo", which is a unix command... I'll report back for others that follow if I find anything.