Archive for October, 2009
As I mentioned a couple of days ago, the move to DotNetNuke 5 has brought about a few changes. Some of them are design decisions that are just frustrating, like not being able to see that a module is viewable by the administrators only. Others are bugs, like not being able to press the ENTER key while searching for a user, like we discussed a couple of days ago.
Today I’d like to alert you to a design decision that may cause you some trouble.
The agile “Task Board,” also known as a “Scrum Board” has become a staple of the agile programming world.
“Getting Things Done” (GTD) is a process for managing task in the business world.
I mostly like what GTD does, but the classic implementation doesn’t fit how I work.
But what if we could adapt the two?
I recently upgraded a DotNetNuke installation and found several issues that are either different from the 4.x series or are now broken.
Most annoying is that there is now no longer any visual indication that a module is viewable by the administrator only. Seems there should at least be a CSS class added to the module so that we can control the visual representation ourselves if we want.
Unfortunately there is nothing we can do about that.
But another issue that showed up is in the user screen.
Now that we’ve assigned roles to our users, we need to assign permissions to the roles.
The easiest way to do this is through the web.config file, which will allow us to control which pages the roles can access.
But how do we control items beyond pages? For that we’ll need to do a bit of “role your own” coding.
Tucked away on the toolbar is a little-used and often overlooked control. Not using this control could be costing you in performance.
The control I’m referring to is the Substitution control. The only time you’d use it would be if you had implemented page caching. You are using page caching, right?