Wednesday, October 15, 2008 5:59 PM
Last week I was asked to come up with a way to use the Page Icon in DotNetNuke as a source for a multi lingual enabled image on a page. Although this could have been done by creating a skinobject, I decided to pull this one off by creating an "inline" skinobject.. by lack of a better term.
Wednesday, October 15, 2008 3:47 PM
Just another day in the live of a (ASP.NET) developer. If you are anything like me that you spend a considerable time of your day researching, and of course... Google is one of the tools of choice here.....Or is it?
Monday, September 22, 2008 2:54 PM
Just recently i answered a question on the DotNetNuke forums about re installing the Search Results module. This is somewhat tricky as you cannot do it by hand.. it can only be done by sql script
Wednesday, September 17, 2008 3:15 PM
Where it comes to using SQL Server features, I am a very late adopter. Not by choice, for all the DotNetNuke modules I create, I'd like to maintain backwards compatibility as much as possible, especially since DotNetNuke also fully supports MS SQL Server 2000.
Monday, September 15, 2008 8:51 PM
I've spent a few days on a strange issue i had with a new VS2008 install: no available AJAX extensions
Sunday, August 24, 2008 10:23 PM
This blog is long overdue. In DotNetNuke 04.06.00 the language skinobject was beefed up to be much more versatile. Apart from just a dropdown menu, it can also display links to languages. Even though Lorraine blogged about the new appearance, there is much more to the skinobject than meets the eyes!
The skinobject supports 2 display modes: dropdown menu and template based repeater (you can even use both at the same time). Apart from that, there is a common header and a common footer available (both templatable).
All templates of the skinobject use the DNN core TokenReplace functionality as template engine. This means that you can control visible appearance of the language skin object to a great extent.
Tuesday, March 11, 2008 12:00 AM
Today I had to upgrade an old DNN 3.2.2 multiportal installation to DNN 4.8.1. There are 3 major areas that changed in the past DotNetNuke versions:
New contstraints and unique indexes on Files table
DNN Membership provider
Consolidation of http handlers in one assembly
Wednesday, March 05, 2008 12:00 AM
... or how I learned an old lesson: always check whether the name of the module you release doesnt actually exist somewhere else.
Tuesday, March 04, 2008 12:00 AM
A while ago i created a small utility that allowed me to easily switch between users in a portal. This is extremely usefull if you are developing a module or a site and you want to test different permissions for different users.
The current version of the module allows you to select whether host users can be switched to as well. Doing this means that you will never have to log on to your site again...
NB: Never use this module in a live environment, as it will make your site VERY insecure!
You can download this module from http://www.codeplex.com/userswitcher, and vote for it on the DNN Forge Page
(cross posted from my blog on...
Thursday, November 15, 2007 2:03 PM
While DotNetNuke 4.4.x already validates emails in the user profile with a regular expression, this regular expression could not be changed by portal admins. In DNN 4.5, the regular expression used to validate email address can be altered in the User Settings Page