Hi,

maybe I've overlooked something, but in my installations, Janode nodes are not accessible through the menu, there is simply no menu entry like ./book, ./node, .forum, etc. available. Also, I can't add a menu item like "resources", or "weblinks" to the primary or secondary menu.

Secondly, there seems to be no "start page" for a web catalog where Janode nodes are collected; users expect something similar to the old Yahoo! start page, or like todays Dmoz if they enter a link collection. Even if the page layout of a link collection could be different, the links would have to be categorized somehow. Nothing of this I can do with Janode.

However, besides of this, entering weblinks works fine, and I can add taxonomy terms to the Janode node - I just can't display them together or sorted in a sensible way.

Regards, asb

Comments

AjK’s picture

Category: bug » support
Status: Active » Fixed

The way to get what you want is the same as any other drupal node, that's all a janode is. I didn't bother adding any display code when I created janode as I didn't need anything special.

I just used this snippet, http://drupal.org/node/53085 modified to suit my needs and that gives me a catelogue (by taxonomy) of my janodes. Feel free to add new display code and add to an issue as a patch :)

asbdpl’s picture

Status: Fixed » Closed (works as designed)

> Feel free to add new display code and add to an issue as a patch :)

If I could code something like this, I wouldn't bother with Drupal ;-)

I tried the "Directory" module, wich also seems to have several bugs that render it useless (http://drupal.org/node/164445) end ended up with using the "Book" mechanism from Drupal Core. The resulting lists are pretty confusing and require a lot of manual work, but it's better than nothing.

What occurs to be ugly and highly irritating, is that now the hyperlink itself appears *below* the book's navigational elements (headline - node with description - navigation elements - hyperlink). Users don't understand that the hyperlink belongs to the node, and the navigational elements for the book have nothing to do with the node itself. Hm, maybe I should switch als Janode nodes back to standard node types, currently there seem to be no advantages at all.

Regards, asb

nancydru’s picture

You might try the Get Content Type module.