Currently, i am in the middle of a process and i would like to mention about the problem that happened while i was testing the application.

Here is the scenario.

Install a DotNetNuke 4.8.2,

Upgrade it to DotNetNuke 4.8.4

Then create a child portal and use an alias like childportal

After creating child portal, login to that portal as childportal admin account and create some pages with content.

Now try to logout, and login with host account, try to logout and login with childportal admin account this time.

If you follow the URL's in address bar, you will notice that while logging in or loggin out, childportal alias not being displayed.

I will present the problem via images or a video later.

DotNetNuke 4.8.4 has been released which fixes 3 low security issues. These issues are related to cross-site attacks. Please check following bulletins to get more info about security fixes.

• Security Bulletin No 18
• Security Bulletin No 19
• Security Bulletin No 20

It's highly recommended to upgrade DotNetNuke to latest security release which is currently v4.8.4. If you don't know how to upgrade your portal, please read following blog post.

How to Upgrade DotNetNuke to 4.8.4 Release

Since DotNetNuke 4.8.3 released last week, it is time to make another touch to my tutorials for shared hosting users of Godaddy.

I don't like them at all, but they provide good options for low price, such as:

• Great Disk Space/Bandwith
• Good Control Panels, once you use it, you will get used to use it
• With some effort you can run multiple websites with your own unique domains under same hosting account.

These are basic features and option 3 is best one i like. However it has disadvantages as well.

If you are planning to host multiple websites under same hosting account to save money, please be aware of shared database issue. Although Godaddy provides huge disk space and bandwith, they don't give customers enough database size to host big-sized websites. This does not mean, you can't host small-business websites under same account.

If you plan to create multiple websites that can share a database size up to 200 megabytes, then please consider using DotNetNuke.

I am also using this method to save bucks, this blog (www.mynetnuke.com) is actually a sub-portal of www.mikroproje.com.

I also have many clients that hosts multiple sites under same account. I'm not going to clearly publish their names here, but i can say that one of my clients hosting following sites under one account:

• French restaurant website
• Advocate & Law for Canadian people
• Furniture & Decoration portal

Basically all three sites are sharing same database, but users, pages, designs and locales can be different. This is a greate feature for those, who cannot afford to pay a large amount per month.

As many of you noticed, DotNetNuke 4.8.3 release (a.k.a Security Release) published last week.

What does Security Release mean?

From title, you may think that previous releases were not secure. Yes, you are right.

After checking various topics on DotNetNuke forums and some other discussion platforms, i also realized  that something was going on with security issues.

Finally, the problem mentioned on public places and topic became an offical problem.

See following blog posts:

DotNetNuke Security Notice

Security Lessons Learned

DotNetNuke Security Update

What i can suggest is, immediately upgrade your DotNetNuke portals to latest available secure release (which is currently DotNetNuke 4.8.3)

I would like you to follow Security Bulletins as well.

How to upgrade DotNetNuke

In previous tutorials, i have mentioned about:

• How to Setup Godaddy Windows Hosting Account
• Install DotNetNuke via Hosting Connection
• How to Move DotNetNuke 4.8 to Root Path

You may want to take advantage of latest version of DotNetNuke framework. Which is currently DotNetNuke 4.8.2 (as for March 28, 2008)

In this tutorial, i am going to cover all required steps for upgrading dotnetnuke instances. This tutorial will have different methods compared to other tutorials, as we might have permission problems if default instructions would followed. We will also take a look at other tutorials for maximum success level. I strongly recommend read first before applying suggestions, once you complete reading at least once, you can start applying my instructions. This helps you to keep your website safe from critical issues.

Let's begin :)

How to move DotNetNuke installation to root path

In this tutorial, i am going to cover how to move your auto-installed DotNetNuke portal to root path of your hosting account.

You may need to download a FTP client in order to transfer content between locations. I strongly suggest Mozilla Filezilla as a free ftp client.

How to install DotNetNuke 4.8 via Godaddy Hosting Connection

In this tutorial, i am going to cover installing DotNetNuke 4.8 with auto-install feature of Godaddy Hosting Connection. Current offical release of DNN is 4.8.1 but Godaddy provides 4.8 while i prepared this tutorial. So you may want to upgrade your portal after installing DotNetNuke 4.8.  I will cover this steps with another tutorial.

You should have at least following in order to install DNN via Hosting Connection.

• Godaddy Deluxe Windows Plan or Premium Windows Plan subscription.
• Unique Top Level Domain Name (e.g www.mywebsite.com)
• Empty MSSQL 2005 Database (Deluxe plan comes up with two empty databases, Premium Plan has three MSSQL 2005 databases)

If you need more help about Godaddy Windows Hosting Accounts you can read following article:

How to Setup Godaddy Windows Hosting Account

In this tutorial, i am going to present how to setup your new Windows Hosting Account.

Godaddy currently provides three types of Windows Hosting accounts. Those are:

• Economy Hosting
• Deluxe Hosting
• Premium Hosting

For a new DotNetNuke user, purchasing a Deluxe Hosting package would be a good start.

Some users asking about why not Economy Hosting package? Because, you may encounter issues with MS Ajax under Economy hosting package. Also it does not let you host multiple websites under a single windows hosting account.

Remember that our goal is;

• Hosting DotNetNuke at root level
• Hosting Multiple Websites using single DotNetNuke Instance

DotNetNuke 4.8.1 finally released. Some of you might remember; i have blogged about major bugs that prevents Turkish users to use DotNetNuke succesfully. I checked Change Log and luckly some of them seems fixed. However, i couldn't test DotNetNuke 4.8.1 release yet.

I'm assuming this will be final release before DotNetNuke 5.0, maybe another release (DotNetNuke 4.8.2) comes first.
Chris Hammond published list of bug fixes in a blog post. You can view details by clicking following link:
DotNetNuke 4.8.1 What's New and What is Fixed?

As an active user of DotNetNuke, i strongly recommend taking backups before making a production site upgrade. Also, it's one of the best practises to wait a few days (maybe a week) before switching on new release.

I'm going to upgrade my DotNetNuke Tutorials for Godaddy users in upcoming weeks. I think, not much thing changed since DotNetNuke 4.8 but, Godaddy has new features for their customers which means i should mention how to use them to get maximum benefit. Please visit http://www.dotnetnuke.com/tabid/125/default.aspx to download latest release of DotNetNuke.

P.S: Some users have reported an issue regarding MSSQL Server 2000 database. You will notice spakinz's comment on blog post and DotNetNuke team refreshed download packages after this report.

KODHEDZ DOTNETNUKE FIRESALE EVENT
I just noticed that Kodhedz running a firesale event today. If you are interested please browse http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/112/threadid/196037/scope/posts/Default.aspx or
http://firesale.kodhedz.com/Specials/tabid/2205/Default.aspx for more information.

How to move DotNetNuke installation to root path

In this tutorial, i am going to cover how to move your auto-installed DotNetNuke portal to root path of your hosting account.

You may need to download a FTP client in order to transfer content between locations. I strongly suggest Mozilla Filezilla as a free ftp client.

How to install DotNetNuke 4.7 via Metropolis

In this tutorial, i am going to cover installing DotNetNuke 4.7 with auto-install feature of Godaddy Metropolis. Current offical release of DNN is 4.8 but Godaddy provides 4.7 while i prepared this tutorial. So you may want to upgrade your portal after installing DotNetNuke 4.7.  I will cover this steps with another tutorial.

You should have at least following in order to install DNN via Metropolis

• Godaddy Deluxe Windows Plan or Premium Windows Plan subscription.
• Unique Top Level Domain Name (e.g www.mywebsite.com)
• Empty MSSQL 2005 Database (Deluxe plan comes up with two empty databases, Premium Plan has three MSSQL 2005 databases)

How to upgrade DotNetNuke

In previous tutorials, i have mentioned about how to use auto-install feature of Godaddy Hosting Connection (a.k.a Metropolis and how to move auto-installed dotnetnuke portal to root path of your hosting account. You may want to take advantage of latest version of DotNetNuke framework. Which is currently DotNetNuke 4.8.0 (as for January 5, 2008)

In this tutorial, i am going to cover all required steps for upgrading dotnetnuke instances. This tutorial will have different methods compared to other tutorials, as we might have permission problems if default instructions would followed. We will also take a look at other tutorials for maximum success level. I strongly recommend read first before applying suggestions, once you complete reading at least once, you can start applying my instructions. This helps you to keep your website safe from critical issues.

I'm using Active Forums v3.7 at my Turkish Community portal. And last night one of portal users reported that he cannot post a new topic to forums.

I investigated issue and finally understand why all users are replying via quick reply to existing topics instead of creating a new topic.

It was a template or HTML editor problem. Actually Post New Topic, or Post a Reply  templates are corrupted.

Finally i decided to send a support ticket to Active Modules team. Here is a short summary of what happened.

I am experiencing issues with Active Forum 3.7 release.
To simulate the issue;

1) Install DNN 4.8
If you experience issues with Turkish locale for DNN 4.8 you can check following blog post and apply the fix;
http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/271/How-to-Fix-GetOrdinals-Exception.aspx

2) Install Active Forums 3.7 (latest)

3) Add Forum module to a page;

4) Go to Forum Control Panel and add a forum group (e.g Main Forum Group) via Forum Groups. Ensure that Allow HTML checkbox is signed and select Default DNN Editor or Active Editor from dropdown list.

5) Click on Forums and add a forum (e.g Test Forum, ensure that it inherits settings from main forum group)

6) Go to Forum as a normal user, or as a admin & host user,

You will notice that, you wont be able to enter your post into Body area, because it is empty.

This problem does not happening if you select TextBox from #4

7) If user submits a reply via Quick Reply moderator cannot see Body area, after he clicks on Moderate button. Other fields are ok.

Please help me to get this sorted out.
Thanks.

Final Notes: I thing this bug is happening to Arabic and Azeri clients as well, i hope it gets solved in a short while.

DotNetNuke 4.8 looks like does not work as expected after applying Turkish Locale. I'm pretty sure this happens with Azeri and other countries that use special characters in locales.

While searching how to fix this error, i reported issue at DotNetNuke Support Tracker.

The bug report source:

http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=6896&PROJID=23

I also posted a notification post for Turkish Community saying "never install dnn 4.8 on a live site before it gets fixed".

Resource: http://www.mikroproje.com/Blog/tabid/144/articleType/ArticleView/articleId/266/Default.aspx

Luckly Bulet Fahri Cavan commented on my blog and posted a temporary solution.

I am going to mention about how to fix the issue but now, lets start with how DNN looks like with this bug.

Another bug with DotNetNuke 4.8 release comes up when you install Media module via browsing Host > Module Definitions page.

After succesful installation wait for a while and you will end up seeing following error in Admin > Event Viewer.

To fix this problem i made some research and found a discussion at following topic. According to John's post, this error happens because of Media module is trying to upgrade itself from a previous version of Image module. However DNN 4.8 Installation package does not contain old Image module.

Source: www.dotnetnuke.com/Community/Forums/tabid/795/forumid/42/threadid/134732/scope/posts/Default.aspx

To gain more info, i opened up EventQueue table in my database by connecting to MSSQL Server 2005 via Microsoft SQL Server Management Studio and noticed that one of the Application_Start event has IsComplete flag set to false. In my environment it has 14 as EventMessageID. I simply set IsComplete flag for this entry to true. Then saved my changes.

It has been 2 hours since this last change and it seems like error gone :)

I also reported this issue to Gemini for permanent solution.

http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=6916&PROJID=23