Wednesday, January 21, 2009 2:25 PM
When you need to upgrade multiple DotNetNuke websites it is sometimes hard to figure out what version a specific site is. Of course, you could logon to all your sites, but that takes quite some time.
If you have installed the databases of your sites in one sql server instance, there is another option available. You could open all databases, open the Version table, and check the highest version number in that table. This is still a lot of work though… however, it is something that can be automated with a little effort.
Thursday, January 08, 2009 7:10 PM
DNN 5 now has the option to give non admins access to admin modules. You can just put any admin module on a new page and give users access to that. An even easier thing to do is to just give non admins permissions to use a specific admin page.
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.