I would be better, if:

$custom_links = array(
"<a href=\"index.php\">home</a>",
);

Could change to use function l() or at least use function url() so it respects clean url's..
So, it would be like this:

$custom_link = array(
l(t("Title of link"), "destination/address", array("title" => "Alt text")),
);

But unfortunatly, drupal keeps yellin' that it can't find function l()... Can't seem to find out why...

Another idea is to make a more graphical interface (module), for this.. So we can define the links, it's alt texts, their destination and their attributes...

Comments

moshe weitzman’s picture

moshe weitzman commented

the $custom_links array is being phased out. I don't think any theme in the core uses it anymore, though i could be wrong. if so, we should remove the array from conf.php and link_page() function.

a gui for link management would be nice.

Stefan Nagtegaal’s picture

Stefan Nagtegaal commented

Any idea how this should look like? What it should do, and what features it should have?
I think:
- link name;
- link destination;
- weight of link (to (re)organize);
- link title-attribute;
- selection enabled/disabled;
- integration with module generated-links? (blogs, book, forum, feedback, image, events, etc, etc);
- Any other?

I would like to have some more features before i begin writing such big and hard thing as this. Any idea's suggestions, code, usability-stuff is welcome..

moshe weitzman’s picture

moshe weitzman commented
Title: $custom_links should use l() or at least url() » A link management module

You should start with Ax's module. It's ancient now, but worked well well at one time - http://cvs.drupal.org/viewcvs/contributions/sandbox/ax/links/?diff_forma...

dries’s picture

dries commented

I agree that we need a central place to manage top-level links and that the $custom_links concept could do with being removed.

ax’s picture

ax commented

Screenshots and mockups for my old link.module mentioned by moshe. especially, take note of link_admin_3.htm

skip’s picture

skip commented

I've uploaded a Navlinks Module that I started working on, but it's only doing part of what needs to be done. Please let me know what you think.

I should have "page" link management soon, but I agree with what others have mentioned... that the whole way that links are coded should be modified.

What about consolidating everything into the menu.inc file (the page and node links)?
If there was an extra argument in the menu() function for type we could use menu() for all links in the module_links() hook.
Then the path, title, and callback would be separated out so that the links could be styled in any way needed (through a theme function).

I haven't really thought the details... just throwing out ideas.

moshe weitzman’s picture

moshe weitzman commented

menu management handles most of this now. please open a new case if more features are desired.

Anonymous’s picture

(not verified) commented