Hi, I've often wondered about this, but now I need to solve it. I'm building a site and have certain modules configured to show on every page e.g. footers, links modules etc.

All works fine until the skin is required to display the entry form of a  DNN core module e.g. Register, Login, Update profile etc. In this case the modules that should show on every page disappear.

It's easy to demonstrate...go to www.reform.co.uk, click the login link and you'll see the footer disappear.

Anyone know a way around this so that 'show on every page' module continue to display?

Thanks in advace

Phil

Your other option is to move - the appear on every page elements into your skin.

We built a custom module for a client a while back that let them place skin objects on their skin - that were controlled by a module we placed in the admin menu. On the skin they placed simple markup <wst:HTML runat="server" id="wstHTML001"  />  in the spots where they wanted global page elements.

And in the admin module we created there was a HTML edit page that let u select the markup block you wanted to edit .

Westa

As of some stage in 5.x the User Account module was changed to automatically get installed into it own real page ... on a new install ... it should already be receiving - show on all pages modules.  

Just a note though - the way dnn manages the show on all pages concept is not that elegant - it basically copies an instance of each module onto each tab/page - which results in lots of additional module entries in your database - one for each page - in a large site this can get rather messy ... I would really suggest looking at other options such as the custom skin object concept if you want to keep a clean site.

It also make deleting such modules a pain - since you need to manually delete the module from EACH page if you decide to want to delete one.
yes the content of each module is linked since they are set as an instance but not all the settings are currently kept consistent  - permissions are copied to all instances - but the module title for example is not.

Westa