Are you running on .Net 3.5 SP1 or .Net 4.0, which is stricter with compile errors?

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

There are several serious issue with the 04.01.00 BETA release of the links module. The immediate error will be logged in the Event Viewer each time the Site Search Scheduler task runs to index site content (every 30 minutes by default). In Links 4.01.00 BETA the module was changed from a WAP or compiled web application project having two dll assemblies located in the site's \bin folder to a WSP or dynamic website project which does not deploy compiled assemblies. Unfortunately the < businesscontroller > node in the module's .dnn manifest was not updated to reflect the change. The value for the business controller class needs to be changed (preferably before install) from "DotNetNuke.Modules.Links.LinkController, DotNetNuke.Modules.Links" to simply "DotNetNuke.Modules.Links.LinkController". If done after install, the value can be changed by editing the module's definition from the Host-->Extensions page.

If you site is using a non-blank objectQualifier when accessing the database, there are missing {objectQualifier} tokens in the dnnLinks_GetLink, dnnLink_GetLinks and dnnLink_UpdateLinks stored procedure definitions. While the module will install without those tokens, an missing database object error will be thrown when placing the module on a page. Ideally (if your site uses a database objectQualifier) those should be corrected in the SqlDataProvider script prior to installation but may also be corrected in the database post install.

Remember that this is a BETA version and should not be used on a production site. I did not have a chance to test the 05.00.00 BETA.

---

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