menu

Có khá nhiều module trình bày menu theo ý mình, như Simple Menu, Nice Menus, Taxonomy Menu... nhưng chúng quá cồng kềnh. Trong Drupal lại có chức năng theme rất mạnh, có thể dùng để trình bày lại menu. Nhưng mà không biết làm cách nào ?

Hi, I've written a simple module to page tabular query results but I get different results depending on login. The main callback from the menu works great but some other functions don't fire for anonymous users. Do I need to register all these in the menu? Or use a different system?

Also, can any item be added to the Drupal 5 menu with drupal_goto as a callback? We'd like to add some dynamic menu items for admins. Is there a wildcard for paths?

I recently come across the problem when I was porting one static site to drupal. Drupal will automatically provide a unique class id for every menu items. This is good but it is also very inconvenient to use css to customize the look of every menu item, especially if one wishes to use pictures instead of plain texts for menu items. I did it by add a snippet into the theme.

So I think a module that enable user to customize the menu class id DIRECTLY is useful. This module is also responsible for checking the existing class IDs of menu items to ensure that every id is unique.

I installed phpbb3 and phpbb module.

"Forum stuff" block shows 3 links: private messages, unread topics, unread posts. Links to topics and posts work, but "private messages" links to a "forum/inbox" which doesn't exist. But inbox exists, I can use it from the forum.

Why?

There is a tutorial up at alldrupalthemes explaining how to "create and awesome looking taxonomy menu, using Imagecache, Taxonomy Image, Views, and some SQL."

http://alldrupalthemes.com/blog/6-steps-fancy-custom-taxonomy-menu-term-...

This seems like a good feature to implement in a photo gallery.

"Relationship" I understood as relationships between fields (nodes are many relationships, which are subject of more advanced process).

Wanted features:

1. Powerful and without limitation thanks to the most abstract (see: "everything is a field", compare this to: Global CCK fields, A controversial(?) point: store translations as nodes).
2. Build-in categorization features.
3. Build-in views features (listing fields, not necessary nodes).
4. Build-in menu features.
5. Support for Semantic Web/Microformats/similar.

Observations about current situation: