Blog

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.

Read More »

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.

Read More »

On our DotNetNuke module demo site, we have a little selector (pictured above) in the upper right hand corner that lets you pick how wide you would like the site to appear. This is based on a similar mechanism on the DNN site. Folks have been asking about it, so feel free to register on our site and grab it for yourself (for free).

Read More »

Today marks the release of the next version of our content rotation module for DotNetNuke, Engage: Rotator.

Read More »

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.

In this version we have made significant enhancements to searching both within the module and through DNN.  Searches return more relevant results and are now marked to show why they are relevant.  The module is also indexed by DNN's search indexer now, which incidentally also allows for the module to be syndicated...

Read More »

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 acheive the same result for more than just IE.

Read More »

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.

...

Read More »

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.

The most exciting new feature for Employment is the addition of Job Groups, which will allow much more customization and flexibility when using the module.  You can now assign jobs into job groups, and then set up various modules to display and edit specific job groups.  Before now, there was no way to segregate your jobs, every module always showed every job.  Now, you can separate jobs between locations or categories, or any way that you want.  In addition, you can also assign different security permissions to each module to better control who gets to create and update various job listings on your site.

Once you upgrade, you can add the Engage: Employment Job Group Admin module onto a page, and create the groups that you need...

Read More »

It's occasionally tricky/troublesome to pass the current Portald from your DotNetNuke control that inherits PortalModuleBase so that it can be used in your business object logic. A trick that I learned looking at another developer's code recently is to get the current PortalId from PortalController.GetCurrentPortalSettings().PortalId. CurrentPortalSettings is set for every request, so it is always the value that you are looking for.

Hope it helps,