FrankZoid wrote:
It may be doable, but there is not a standard way to associate the module with the content item; modules are associated with menu items.
I'm afraid I don't understand. I'm new to this and
I must be missing some very basic concept. What would be the point of including a 'related item' module and 'Table-Content Category' in the core release if all related item does when you visit an item from the 'Table-Content Category' is displays the phrase "related item"? There are much simpler ways of doing that.
It would be one thing if the module and menu updates only worked from menu items where I've manually specifically designated that the menu link display the module, but
it works in other generated links (if you click on the link generated by the related item module it displays all of the content that I want associated with the item) why wouldn't it work in the link generated to display on the 'Table-Content Category'?
jumla/mambo 'Table-Content Category' already generates the list, generates the links in the list, gives me the great filter and sort options, and jumla/ mambo has the ability to call a page that displays all of the content (as evidenced by the related items module), why would the filtered sorted list in the 'Table-Content Category' point to only 30% of the intended content instead?
I know I can force this to work by simply manually creating a new menu and manually adding the desired links and their behaviour to it, creating a new template with a spot for the new menu below the content item, and a script to sort and filter the menu, but I thought the ability to update,
cross-reference,
sort,
organize, and
present content items without manually creating a menu for each iteration was the point of CMSs.
That can't possibly be missing from jumla/mambo?
The emperor must have clothes!
Sorry for the rant, it's late and I've been struggling with this for a while.