Hello Nikos in order for your code to work you need to assign this item to a menu item.

Then assign the module to that particular menu item and at the
nuMuzik_Component position

Krikor, while assigning menu to items/categories etc.. i see no option to assign this specific module..
how should i do it?

is for some reason k2 item blocking other js from running?

Hello Nikos,

Have you entered this position in your templatedetails.xml as well?
You can also type it in the text field and it will also render.

For your second question K2 is not blocking any JS scripts. Make sure you are not using a 'Tidy' plugin or something of that sort,

the code from k2 forum, adding a new position in item.php didn't work either..

i was almost convinced that it was a module issue..but on the other hand on a quick test on beez5 default template, had as a result the module to operate normaly even within k2 item with {loadposition customposition}

i really don't know how to deal with this..it seems that probably the module is not a "state of art" in terms of bulletproof code but on the other hand i can't explain how it is possible to work ok on beez5

so far the only viable solution has been to position it absolutely but tbh i m not happy with this solution..

and the weirdest of all is that it generates no js errors in the console..

if you feel it like a "case study" on what could possibly be the issue module vs template i have no problem to provide the module for examination

*edit:just to clarify because sometimes when writing could be misunderstood, i m not expressing a dissatisfaction regarding the template, just a kind of warning of a potential issue..

The problem with checking jQuery code with the beez template is that that template does not use jQuery so you can't check for multiple instances of jQuery and other conflicts.

I can see the module is force loading an older version of jQuery (1.7) so the conflict lies in the multiple instances of the jQuery.

Disabling the 1.7 version and keeping the 1.8 version or downgrading to 1.7 will resolve your issues.

i think i ve ended up with a solution..
after disabling behaviour.js i found that the module worked properly..
so i returned back to module core files and replaced anonymous functions and all $ instances with my own var after having it defined as jquery.noconflict now it seems to operate as expected..
it had been really tricky..!!!