HI,

I am somewhat new to DNN, and have recently created a fairly simple DNN module to allow people to make online credit card payments through my website.  The module seems to work great when I am logged in as host or any other administrator user.  Unfortunately, when I am logged in as a regular user, or not logged in at all, the module doesn't seem to load properly, and is VERY inconsistent in its behavior.

Now, the main problem that I am having doesn't seem to have anything to do with my module per se.  What I mean by this is that when I fill out all the information on my module, and click 'Submit Payment', it "seems to" do a postback, except that no breakpoints on my module fire, including at the top of page_load, or on the submit button click event.  After clicking back and forth between different menu items like home, login, etc. and going back to my module page, it SOMETIMES will fire the breakpoint, and then therefore do what it is supposed to, but it is very inconsistent.  Again, as soon as I am logged in as an admin user, it works 100% always.

Has anyone ever experienced this before? What could be the potential causes for such a behavior?

Any help with this situation would be most appreciated!

Thanks for the reply Ian,

Unfortunately, this did not seem to solve my problem.. I cleared all the browser history/cache from firefox and ie, and tested the module, but no luck..  Even before I do anything it seems to only load once [in a while].. I mean to say that I have a breakpoint on the page_load for my module, and it breaks at my breakpoint the first time, but if I click onto another link, and click back to a page that has my module, it does not throw a breakpoint, but yet the module still shows up on the page.. To me this does seem like it would be caching the data, except that I have turned off caching for my module via the instructions you gave, and also in ie I have it set to, 'Check for newer versions of stored pages: Every time I visit the webpage', so caching should not even be turned on at all..

I am sure that this issue is something silly that I overlooked while creating the module, but I just cannot figure out what could cause this.. Again, if anyone has any further suggestions, they are most appreciated!

Great! That definitely seems to have fixed the issue!

Thanks so much Ian and Hooligannes for your help!

I do have a follow-up question, if anyone can point me in the right direction.. Is there anyway in the code of my module to force a cache value of zero for when I update the module and re-add it to my site?  It would be nice if I didn't have to remember to set the cache value manually everytime..