I have a curious question based on some testing I have done.

There appears to have been a change from 5.x to 6.x regarding the 'Allow Print' function for a module.

I have tested this on multiple sites but as I stated previous, the more I learn the more I forget - so help me remember/understand where I have gone wrong.

In 5.6.x and versions prior, in the module settings (HTML module) for example.. When you tick the checkbox for 'Allow Print', most containers would display a printer icon in the upper or lower right corner (with some obvious variations) and this would allow any user the ability to select this option to print the content of the module.

In version 6.0.1 with the default DNN skin and nothing more installed other than the default template (CE edition), this appears to have changed.

Again using the CE default Minimal Extropy skin and containers on the 'Home' tab - in 6.x, under the new 'Manage' menu there is multiple sections: Edit, Admin, Move.

The print function appears under the Admin section in 6.x and when the container is ticked on and the Allow Print is ticked on, you can not see the print icon when not logged in as an Administrator or are given the appropriate Edit permissions.

Prior to 6.x ticking the Container check box and the Allow Print check box, would show the printer icon if the container author had included those bits in their code (I am assuming to use the default DNN skin which contains all of these features in their containers.

QUESTION - why the change? Why should 'Print' be an admin function on a module and more relevant, how would one work around it?

I think that the Dark Knight containers to not include "those bits" to implement the print and visibility (expand/collapse) functions. You will need to change containers, or add to the DK containers to include them.

I hope that's the case, but I have tried multiple other skins and had the same results.
I would be interested in additional test.