Posted by tevih on July 16, 2009 at 2:40am
2 followers
Jump to:
| Project: | me aliases |
| Version: | 5.x-1.2 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Hello,
First of all, great module! I wish this ease of use was included in core.
My question is how to replace locked links? For example, "my account" menu item can be created by using a path of "user/me", but the original my account menu item is locked, and therefore still present in the default location. I would like to completely replace the original link with the new one. The with the "My blog" menu item - I would like to not just create a new menu item, but completely replace the previous one with my new one.
I know that this isn't really an issue with the module, but I imagine that this type of process is why many people like this module, so I'm hoping someone can answer this question for me.
Thanks so much!
Tevi
Comments
#1
I'm not sure I fully understand this question. Are You asking how the module manages to completely replace the locked links?
#2
sorry, no. I'm asking how I can get rid of links to things I have recreated with this module. Say I use this module to create a new link to "My Blog", the original "My Blog" link is locked and still present, and I'm wondering how to remove the original link.
#3
Why are you re-creating a link that already exists? The me module already changes the "My blog" link to work as blog/me. Same with the my account link. All you should need to do is edit the locked link and perhaps change its title, and maybe which menu it is in.
Would this not solve your issue?
#4
yes that would - but you answered your own question. I can't edit a locked link because it's locked!! That's why I wanted the 'me' module.
Hence my question...
#5
How is the link locked? I've never come across a completely locked link before. The only part the "my account" link, and others like it that I have never been able to change is the path.
#6
Oh wait.. this is for Drupal 5? I'm sorry, I was thinking it was Drupal 6. I should learn to look at the version of an issue. :) I'll have a look into this.. I'm not too sure regarding Drupal 5.
#7
That's the third time someone did that! I know, I must be a dinosaur using D5! There were modules I needed which were not yet up to speed for D6.
No worries, thanks for looking in to it.