I assume you are developing your module in a local instance of DNN. You should be able to troubleshoot your module in a local DNN 5.0.1 instance. Are you able to do so?

---

John Eimer

There are several possible reasons that a module does not show up when placed on a page. Here are a few things you can check:

1. Verify that the module's default view control has been assigned a blank ControlKey in the module's definition. If none of the module's controls have a blank ControlKey, the module when placed on a page will be invisible and no error will be generated.

2. Check the site's Admin-->Event Viewer to see if an error has been logged when the module was placed on the page and/or errors when ever the page is loaded. Usually, but not always, a failed to load module message will be show on the page but occasionally, the error will be such that there is no visible sign of the error on the page - just a log entry.

3. If you can debug you module's source code in VS 2005/2008, etc. try setting a break point at the top of the default module control's Page_Load handler to see if it is getting hit. If so, step through the page load code to see where it breaks.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner