I got a problem with a submenu-module on the yaml-position left and I'm not sure if it's related with the k2-tag-page that it doesnt work:

minecraft-heads.com/heads/alphabet
It's the menu starting with Alphabet, Animals etc on the left side (obviously).

Right now, it should be shown on all pages but startside, faq and impressum. But as soon as you leave the category-view and go to a tag-view it's gone.

Somehow I think it has to do with the baseentry and the first used menu in the setting, but that's just a guess.
If I set it to one it works, if I set it to two it doesnt work anymore.

Here's the setting:
i.imgur.com/JYlEOyZ.png

If the tags do not belong to any menu item, the module will not have any menu items to display. Since it is starting from the second level the top level items are not available.

A solution would be to either map these tags into menu items (if you only have a handful of them) or create a new empty K2 category menu item (leave the category selection empty), call it eg: content and have all orphan tags render through that menu item. This way you can control which modules are published on that menu item.

I created a hidden menu (just a menu, there's no module which shows the menu) which got all tags as menu-entry on the first level.

I tried to modify the menu so the tags are on the second level and the first level is just one unused bracket but the module from the category-menu still dont show up.

That means I got you wrong somehow - and that's not surprising since I didnt compleatly get your solution proposal. Can you go a bit more into detail?
Especially the "have all orphan tags render through that" sounds interesting if it is a solution so I dont have to create a menu-item for every tag.

I think I got it.

I added a new menupoint on the second level in the last position of the menu.
Then I added all tags under this new menupoint on the third level.

Then I hide the single menupoint from the module via CSS:

.dropdown-vertical li.item-last {
display:none !important;
}

You think this solution is ok or could there be a problem with that?

It could be an issue if you add a new menu item in bottom. Other than that it should work fine.

Well, in case I do and another entry instead of the one I created appears I'll remember.

So problem solved :)


Only question left: Is there a generic solution for the tags-menu-entries or do I have to create a menupoint for every tag manually?

A solution would be to either map these tags into menu items (if you only have a handful of them) or create a new empty K2 category menu item (leave the category selection empty), call it eg: content and have all orphan tags render through that menu item. This way you can control which modules are published on that menu item.

Check the 'or' solution, an empty K2 categories menu item will work as well.

Well I red the "or"-Solution, but I didnt understand it.

1. Create a empty k2category-menuitem - done

2. Have all orphan tags render through that menu item.

Erm!? I got a category-item, what does this have to do with the tags, and now to "let them render" through it. I just dont get what you mean netiehr what I have to do here...

This method will solve all double content issues. All orphan tags , users and search results now belong to a menu item.

This means that you can publish modules for these views specifically.