News

Sometimes a simple change and all of a sudden your module is mysteriously showing errors in strange places. Here's are a couple of tips to keep some of these scenarios from affecting your modules, and how to recognize them if they do.

We've released the next Alpha release of the Engage: Events module for DotNetNuke. Try it out and let us know what you think and what you'd like to see from this module.

We've been hard at work to create a new DotNetNuke module to manage your website's events. Take a look and let us know where you want us to go with it.

 

We at Engage Software have just released the latest update to our DotNetNuke Jobs Listing module, Engage: Employment, version 1.3.  This is a module you can use on your company's DNN site to list the job openings you have available at your various locations, and accept and sort applications and applicants.

Have you ever used the DefaultButton property on an ASP.NET Panel, only to find that it doesn't work in Firefox? Here's an easy way to use DotNetNuke's ClientAPI to achieve the same result for more than just IE.

As a developer, and specifically as a DotNetNuke developer, there are a number of directories that I have to navigate to regularly.  In particular with DotNetNuke, I'm going to C:\inetpub\wwwroot\DotNetNuke\Website\DesktopModules quite a bit.  So, instead of having to try to type that in all the time, or navigate through the folder structure, I've defined an environment variable "dm" that is defined as that path to my Desktop Modules folder.  I can just type %dm% into an explorer prompt and be there without any hassle.  I've also setup a %wwwroot% shortcut, though it gets used much less often.  It's a lot like keeping a shortcut around in your dock/quick launch toolbar, but you can also use it in dialogs.  Hopefully this can help you trim off a few more seconds/minutes of monotony throughout your day.

We have released a major update for Engage: Employment, our DNN job listing module.  In version 1.2, we have added a number of new features and fixed all known bugs from version 1.1.

If you're DotNetNuke portal isn't sending emails as you would expect you likely haven't configured your SMTP settings properly. To configure your SMTP settings try the following.

Best practices for developing DotNetNuke modules dictates that we use the development.config as our web.config, which includes running our development sites under Medium Trust.  This is necessary so that we don't inadvertently introduce code that requires Full Trust into our module and thereby restrict it to customers running in Medium Trust.