Hi Darrin,

I'm sorry to hear that your site was "hosed" and offer any assistance I may provide to get it going again. The ePrayer module has been installed on many test sites and several dozen church production sites without problems but once in a while things can go wrong during a DNN module install.

Regarding source code being included in the .zip package - as this is a dynamically compiled module rather than a WAP (compiled) project, all source code has to be included making an install package identical to a source package. When I offer ePrayer commercially, there will be a separate compiled install package.

As far as troubleshooting your site's failure, please provide the following information:

1. Version of DNN? Is AJAX enabled in the host settings?
2. Was this a first time install of the ePrayer module or an update of a previously installed version?
3. Were any errors encountered during the install of the module or did the problem occur after the installed ePrayer module was added to a page of the site? If the latter, was it added to the home page?
4. What do you mean by your site being "hosed". Unhandled application error, error on page where module was installed, errors in EventViewer, etc.?  Please provide the entire error message shown including any stack trace.
5. Please check your web.config to see if the following line was added to the < codeSubDirectories> node during the install:

< add directoryName="WESNet_EPrayer" />

6. If you are not able to remedy the problem yourself, would it be possible to obtain admin or preferably host access to the site temporarily?

Feel free to email me at bill at wesnetdesigns dot com with your reply.

Bill