Hope someone can help me with an issue I'm having while copying one page from another.  I have a page, Page A, with a Links module on it, already populated with content.  Let's say this is the data related to the module:

Module ID: 733
Module Title: My Links
Links:
Google
Yahoo
MSN

Now, I create a new page, Page B, and choose to copy it from Page A.  While I'm doing this, I make sure I choose NEW for the Links module, rather than REFERENCE.  This means a new module will get created for Page B:

Module ID: 740
Module Title: Links
(Empty)

And I can verify this by directly querying the database.  But when I go back to Page A, suddenly the Links module is empty!  If I click on "Add Link," I can quickly see why; the URL shows that the module I'm trying to edit is 740, not 733.  Somehow Page A  has been tied to the module that was created for the new page instead of the correct one!

Querying the database confirms that all of module 733's data is still there, and what's more, Page A is still properly related to module 733. 

The most perplexing thing is that I can log out, clear my session data, close my browser, even visit the page on ANOTHER MACHINE, and the error still occurs.  But eventually, if I simply wait long enough, I can visit Page A again and everything is fine.  Obviously, something is going wrong in the persistent application data, not in the database or in session data.

I sure hope someone's run into this before and can tell me where to begin tracking down the problem!

I'll bump this one more time in the (ever diminishing) hope that someone knows a solution.

Please do tell me if my explanation is too confusing (or just plain too long to bother reading!)

Essentially, my problem is that in the application environment itself, relationships between pages and their modules get screwed up after a page copy.

This seems to be a caching issue, which DNN version are you running? AFAIR there has been an issue in DNNN 4.6.0 or 4.7.0 that should be corrected meanwhile.