In K2-content i can't choose module position because it opens the list of module position in full windows instead of lightbox. If i click in one position nothing happens. (is not transferred the selection to the module)
The same things happen if i choose the specific item.

In K2-tool instead the module position works fine.

J 2.5.24
K2 2.6.8

php 5.3.28

Template JA-Mixmax

Best regards

Make sure your administrator area does not have any JavaScript errors.
If it is failing with the K2 Content module it will fail with other modules as well.

Open your browser's developer tools and check the console tab.
Error will show there.

Thanks Kirkor, polite as always!


I do not know if I understood well what should I do. However i found this warning in js:

L’utilizzo di getAttributeNode() è deprecato. Al suo posto utilizzare getAttribute(). mootools-core.js:343

]The use of getAttributeNode () is deprecated. In its place, use getAttribute (). mootools-core.js: 343

This is a MooTools error.
More of a warning actually, I do not think this is causing the issue.

Is it happening with other modules as well? Can you publish a non K2 module in an other template's position please?

As a workarounf you can manually type the module position in the field (no need to open the lightbox).

It happen with k2 Content module. If I use (for example) k2 tools module the position works fine!.

I know that I can write the position directly. But always in k2 content module does not work also the choice of the specific item.
Of course, the choice of location also works with other not k-2 modules

Thank you Krikor

I am also using Joomla! 2.5.24 and K2 2.6.8 and I cannot replicate this issue.
On the other hand I am not getting this warning.

The issue is caused most probably from another extension which is printing outdated MooTools code.

Are you using any third party K2 extensions or any module related plugins?

I use k2-mart and some extension embedded with the template

I have K2 Mart istanlled as well and it is working fine on my end.
I would suggest contacting the template developer, pasting the error and the stating this issue and ask them for a hint or a possible solution.