I'm trying to set the default page to my/home. All I end up with is "page not found". Also for my/blog and so forth. I suspect that I simply am not installing or enabling some needed module.

Which module provides this functionality?

Thanks!

Comments

vm’s picture

are you using the path.module ? (part of core)

documentation for this can be found in the handbooks under core modules => path
_____________________________________________________________________________________________
give a person a fish and you feed them for a day but ... teach a person to fish and you feed them for a lifetime

shap’s picture

Path is configured, but nothing has been set up in it. That may indeed be what is wrong, but I think not. This all started because I was looking at the drupal installer howto, which sets site_frontpage to "my/home" and clearly expects to be able to use "my/blog", "my/events", and so forth.

Now it may be that they are using pathauto and forgot to include something in their configuration. There were other bugs in that example, so that wouldn't surprise me. But I have seen other places recommend changing site_frontpage

vm’s picture

Path is configured, but nothing has been set up in it. That may indeed be what is wrong, but I think not

I assure you it is what is wrong. you cannot have url aliases from node/some# to /news or /support without it.

I know not what installation instructions are are referring to because you did not link to them.

pathauto, only automates some things with regards to the path.module
_____________________________________________________________________________________________
give a person a fish and you feed them for a day but ... teach a person to fish and you feed them for a lifetime

shap’s picture

Sorry about the missing link. I have been attempting to modify the installation profile at http://drupal.org/node/67921, using the gojoingo sample as a model (though one that I am now very skeptical about). If you look at the list of modules at the top, you will not find pathauto being installed. There is no hint of pathauto being installed, but if you look down below (search for "my/", you will find the assumption that various paths are going to be normalized.

Because of your suggestion, I have been trying to get pathauto working without success. I am running Drupal 5.2. I am logged in as superuser, but I have also enabled (for testing) the "administer pathauto" permission for any authenticated user. When I go to the site configuration/Pathauto page, I get the general settings, but I do not see any place where rewrite rules can be put in. The page I am seeing definitely does not match images I have seen on various howto pages. It almost looks like pathauto is attempting to iterate over the modules and failing.

Oh. I should say that this is running pathauto 5.x-2.x-dev... uh oh. Crud. I hadn't noticed that. Hang on while I go install the beta, which is the "official" release... Yep, That at least gives the expected fields in the form so that I might enter the aliases, but I still don't comprehend what the heck the gojoingo guys thought they were doing. I'm happy to set up pathauto, but any clues what was up with their example?

shap’s picture

Okay, I now have pathauto installed, and this is definitely not a pathauto thing. I see the patterns and I think I understand what pathauto does. What gojoingo is doing is something else entirely. What they seem to be doing is automatically mapping the path "my/home" onto "users/

What a horrible bug in the most recent pathauto: http://drupal.org/node/167787 -- it seems to affect nearly all versions of fedora. Why phppcre was compiled without unicode support I do not quite know.

Oh! Okay, I stumbled completely out of the blue into this page (http://drupal.org/node/45954) which may provide a clue. The gojoingo sample installer profile alleges to set up primary menu links, actually touches the secondary links if you look at the code, and apparently got that wrong as well.

I'm thinking that Pete may have this right, and that gojoingo may be doing something very strange with paths that works for them but not in general.

In the meantime, it was still useful to get pathalias working, so let me go apply the RE patch.

pbarnett’s picture

Hi shap.

Yeah, a link to the offending document might help...

IIRC, there's a a sequence of patterns that Drupal looks for given a particular URL; if the string after the site name matches the name of an alias set up by the path module, you'll get http://mysite.com/alias rather than http://mysite.com/node/42 or whatever.

If the string is the name of an enabled module, then control is passed to that module with any further qualifiers like http://mysite.com/modulename/this/that resulting in this and that being passed as arguments to the module's modulename_page function.

The above depends on whether clean URLs are enabled, there's a ?q= after the site name otherwise.

I'm not an expert on this; these are the bits that I've used :-)

Pete.

shap’s picture

Sorry -- I don't know how to reply to two people at once, but I wanted you to see my reply above also.