Yep - this is affecting my sites too, resulting is support calls from dissatisfied customers, and requiring a manual visit to each and every page to insert a copy of the module from the original page. I hope someone has an aswer for this soon.

Cracked it - well sort of.

When you unset the 'show on all pages' flag, the Data Access Layer iteratively calls stored procedure DNN_DeleteTabModule for every tab OTHER then the current tab, and sets the softdelete flag. The procedure then sets the matching dnn_tabmodules entries isdeleted flag, but is ALSO sets the versionguid to newid - which is what I guess is breaking it when you unset the flag.

The solution is to simply hard delete those rows. I assumed this can be done without breaking any referential integrity, since it is exactly what the stored procedure above does when the soft delete parameter is NOT set.

I tried this, and my module started appearing on all pages again!

So the solution to make a module that refuses to appear on all pages do so (which I intend to code into an XModPro module so I can do it through a new admin page) is simply this:

1. Go to the page on which it does appear and click the edit settings button

2. Determine the module id from the url on the resulting screen, which will end with 'moduleid/1157' for example

3. Make sure 'show on all pages' is off - if not, turn it off and update the page.

4. Run the SQL delete dnn_tab_modules where moduleid=1157 and isdeleted = 1

5. Go back into module settings and turn 'show on all pages' on again - the module will then do exactly what it says on the tin (sorry: an expression from a British advert :-)

IMPORTANT: use your actual moduleid, and NOT the 1157 shown in the above examples

Now if someone can figure out the 'proper' way to fix that version guid, we can come up with a more elegant solution!

HTH

Steve