Well it has been considerable time since I last blogged on this site and for anyone who viewed my site previously it was developed in BlogEngine.net. The sofware is a very capable piece of software but I had some issues in the upgrading of the site and my XML files started giving me some issues.
I was brought in to work on an asp.net web site recently that had been written by another company. I was asked to add some features to their current site as well as to fix some bugs that had been left by the previous developers. Once I had the site ready I moved this web site project to my staging server and then started receiving this error on a couple of pages. Now I had chosen to publish the website instead of just doing a copy of the site with the code-behind files as well. ...
While setting up an installation of DNN for a client I ran into an issue of not being able to display the Image Gallery from within the FCK Editor on an HTML/Text Module. My first instinct with this was that I did not have read permissions on the "/Portals/0/" folder within the DNN architecture.
One of the big complaints that I have seen over the years with DotNetNuke has been the horrible URL’s that get produced by the framework. This is a problem that is part of most dynamically created content on the web, not only DotNetNuke.
Paul Scarlett of tressleworks.ca has created a Visual Basic Script to re-package DNN 4.0 skins into the new format for DNN 5.0.
On November 11, 2008, DotNetNuke Corporation announced that they would be releasing a commercially supported version of their open source content management system. DotNetNuke Professional Edition will provide access to expert technical support and value added network services that simplify and optimize the maintenance of DNN Web sites.
The announcement stated that the first release of their professional edition would be based on the current 4.9 core release.
DotNetNuke Corporation ...