I had a problem while using Telerik's RADEditor. I type too fast while creating a blog post. This results sometimes content loss because of accidental...

[Read the rest of this article...]

Wow, what a surprise, i remember the old days that i used DNN 2.x and 3.x series. Now, everything goes smoothly and i think we will have monthly up...

[Read the rest of this article...]

Ok guys, hearing your feedback i decided to move back my hosting to United States with PowerDNN.Once i finish my tasks, i will post here new tutorials...

[Read the rest of this article...]

I have been trying to install Telerik DNN Modules Trial zip package over a fresh DotNetNuke 5.2.1 installation. However, it keeps me away from it.You ...

[Read the rest of this article...]

You might notice, DotNetNuke 5.2.0 is released recently. However there are some outstanding issues that prevent us to have it nicely. The first and m...

[Read the rest of this article...]

In my previous articles i have explained how DotNetNuke can save you from hosting fees, now i want to share a good news. My blog is getting popular ea...

[Read the rest of this article...]

Since i have launched a personal blog, i thought it would be a best practise to list my recent projects there under a photogallery, for those wonderer...

[Read the rest of this article...]

Until now, i have been asked to prove, why DotNetNuke can be used to save hosting fees. Well, i have already discussed it billion times with my visito...

[Read the rest of this article...]

My blog visitors always ask questions like "when you gonna release new language pack?" and so on... For those Turkish Community members, i would like....

[Read the rest of this article...]

Seems like i am lucky. While checking my personal blog and doing some work, i noticed New version available message through control panel. After...

[Read the rest of this article...]

My visitors keep asking me about the status of content on this blog. Altough titles of blog posts referencing to old releases of DNN, i can assure you...

[Read the rest of this article...]

I was not be able to post new entries to this blog since moving to a new dedicated server, located at Turkey. Last weekend, i had to upgrade DotNetNu...

[Read the rest of this article...]

DotNetNuke 5.0.1 C.E released today. You can find key notes and major highlights below:

• Added the ability to automatically update user roles without requiring the user to logout and log back in.
• Changed the user deletion code to use a soft-delete rather than removing the user record. This ensures that modules like the Forums behave correctly for a previously "deleted" user.
• Added IP logging to the User's table to capture the last IP address from which a user logged in.
• Fixed breaking change with case sensitivity in the name of skin panes. This fix restores the case-insensitivity of previous DotNetNuke releases.
• Fixed breaking change with ModuleId in DotNetNuke 5.0 which changed ModuleId to a readonly value.
• Fixed breaking change in CBO.FillDictionary to restore previous behavior.
• Fixed breaking change which prevented legacy skins from being installed when using the auto-install option.
• Fixed breaking change which prevented updated DLLs from being replaced when repairing a module installation.
• Fixed breaking change in HumanFriendlyUrls which prevented querystrings from being properly read when using HumanFriendlyUrls
• Fixed breaking change in legacy modules which would not store a zip file which was not designated as a resource file.
• Fixed breaking change in legacy modules which ignored zip directories. DNN 5 changed this behavior.
• Fixed breaking change in default.css which resulted in changes to existing skin layouts.
• Fixed issue with roles module which prevented users from delegating role administration to a non-admin user.
• Fixed issue which prevented some users from logging out due to the inability of the system to detect their country.
• Fixed issue with Module Action Menu which prevented it from opening links in new windows.
• Fixed issue that results in an error when the Cache logs an error under the new CACHE_ERROR event type
• Fixed a packaging issue with FCKEditor which caused the LinkEditor to cause an unhandled exception.
• Fixed an issue which resulted in the system not being able to display the portalaliases screen

Security Fixes

• Fixed version information leakage issue in the install wizard

 

Updated Modules/Providers

The following modules and providers have been updated in the 5.0.1 packages. Please see the specific project pages for notes on what bugs or enhancements were corrected with each release.
Modules

• Forms and List 05.00.00

 

Providers

• FckHtmlEditorProvider 2.0.3
• AD Provider 05.00.01

[Read the rest of this article...]

You might have noticed the downtime of my website a few days ago. I was actually trying to upgrade website components to newer releases. However, upgr...

[Read the rest of this article...]

Previously, i have talked about how to install DotNetNuke 5.0 to your hosting account. What if you are using an old release of DotNetNuke? You must upgrade your existing websites to newest release. According to security bulletins out there, old releases have issues with security roles. An attacker could access to your site and gain access to private roles. This is a security hole and an important issue.

The solution is upgrading your DotNetNuke Installation. With this tutorial, you will have no hesitation during an upgrade process.

Let's get started.

I'm going to cover all required actions to upgrade a DotNetNuke installation hosted by Godaddy. If you would have followed default upgrade instructions on a custom installation, it would most likely to have some problems. It's best practice to read full tutorial first and apply instructions then.

Before Begin:

It's recommended to have following software before upgrading your website.

• Visual Web Developer 2008 Express Edition (Service Pack 1 Upgrade enabled) [get it here] [register here]
• Mozilla Firefox (optional) [get it here]
• Mozilla Filezilla (optional) [get it here]
• Winzip or WinRAR Compression Utility (optional) [get Winzip] [get WinRAR]

[Read the rest of this article...]

After reading this article, you will be able to install DotNetNuke 5.0.0 release (currently latest DNN release available) application to root directory under of your Godaddy hosted environment. Before go on reading, make sure that you are using one of Godaddy (Deluxe or Premium) Windows plans.

View Highlights of DotNetNuke 5.0.0

Update:  A friend reported that Economy plan is enough to install at root level. However i wont support this plan since i haven't used it recently.

It is very important that, i cannot accept any liability if this tutorial breaks your live environment, notice that this tutorial only works for new installations, not for upgrades. You also should backup your files before replacing them.

As default, Godaddy does not allow customers to install DotNetNuke to root level. See offical KB Article at following link:
Can I Install a DotNetNuke in my Root Folder?

However with some effort, you can install DNN to root. I know it's not simple. But i had installed almost all releases from early DNN 4.x to DNN 4.9 release to root path with a good strategy.

[Read the rest of this article...]

Yes, you can install DotNetNuke 4.9 release to your hosting account root path (if hosted with Godaddy, maybe even with all shared hosting providers) w...

[Read the rest of this article...]

I have read a blog post from Mitchel Sellers calling new team members for DotNetNuke Documents module, and i have submitted my application a few weeks...

[Read the rest of this article...]

DotNetNuke 4.9 release fixes several security issues. Some of them marked as low and two of them are marked as critical. You are strongly advised to ...

[Read the rest of this article...]

DotNetNuke 4.9 release firstly announced as a replacement for DotNetNuke 4.8.5 release.  Then, core team was working on a few security issues and...

[Read the rest of this article...]