<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>Tutorials, Bug Fixes, Subscriber Articles, Hosting DotNetNuke at Godaddy</title><link>http://www.mynetnuke.com</link><description>RSS feeds for Tutorials, Bug Fixes, Subscriber Articles, Hosting DotNetNuke at Godaddy</description><ttl>60</ttl><creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license><image><link>http://creativecommons.org/licenses/by-nc-sa/3.0/</link><url>http://creativecommons.org/images/public/somerights20.gif</url><title>Some Rights Reserved</title></image><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/mynetnuke" type="application/rss+xml" /><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/312/DotNetNuke-501-Community-Edition-Released.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=312</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=312&amp;PortalID=28&amp;TabID=525</trackback:ping><title>DotNetNuke 5.0.1 Community Edition Released</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/jQPn3UpTx4I/DotNetNuke-501-Community-Edition-Released.aspx</link><description>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

&amp;#160;
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

&amp;#160;
Providers

    FckHtmlEditorProvider 2.0.3
    AD Provider 05.00.01
</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Thu, 26 Feb 2009 07:51:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:312</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/312/DotNetNuke-501-Community-Edition-Released.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/311/What-Happened-Recently.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=311</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=311&amp;PortalID=28&amp;TabID=525</trackback:ping><title>What Happened Recently</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/VL3OKi3i5ng/What-Happened-Recently.aspx</link><description>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, upgrade failed for some reason and i wasn't able to restore content and database backup quickly.

Although i had verified backups (lessons learned from early mistakes) i could restore it after a few attempts.

When a major release published i find it a bit difficult to upgrade from earlier releases of DotNetNuke. Maybe they should add test cases for Upgrades and they shouldn't make last minute changes on packages. This can be somewhat painful for new DotNetNuke users.

Currently i have to follow upgrade path again in order to apply things in my mind. I hope this time everything goes smoothly.

Please keep in mind to check DotNetNuke forums if you are willing to upgrade to DotNetNuke 5.</description><dc:creator>Ismet Dumlupinar</dc:creator><enclosure url="http://www.mynetnuke.com/Portals/28/images/Articles/badge3.gif" type="image/gif" length="6354" /><pubDate>Mon, 02 Feb 2009 09:04:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:311</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/311/What-Happened-Recently.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/310/How-to-Upgrade-Existing-Installations-to-DotNetNuke-5-Release.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=310</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=310&amp;PortalID=28&amp;TabID=525</trackback:ping><title>How to Upgrade Existing Installations to DotNetNuke 5 Release</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/BuRPGKaC71k/How-to-Upgrade-Existing-Installations-to-DotNetNuke-5-Release.aspx</link><description>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]
</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Sun, 25 Jan 2009 20:27:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:310</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/310/How-to-Upgrade-Existing-Installations-to-DotNetNuke-5-Release.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/309/How-to-Install-DotNetNuke-50-to-Godaddy-Root-Path.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=309</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=309&amp;PortalID=28&amp;TabID=525</trackback:ping><title>How to Install DotNetNuke 5.0 to Godaddy Root Path</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/yuMpMYfiTHk/How-to-Install-DotNetNuke-50-to-Godaddy-Root-Path.aspx</link><description>
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:&amp;#160; 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.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Sun, 25 Jan 2009 20:21:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:309</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/309/How-to-Install-DotNetNuke-50-to-Godaddy-Root-Path.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/308/How-to-Use-Telerik-RadEditor-with-DotNetNuke-500-Release.aspx#Comments</comments><slash:comments>5</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=308</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=308&amp;PortalID=28&amp;TabID=525</trackback:ping><title>How to Use Telerik RadEditor with DotNetNuke 5.0.0 Release</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/nhf6vTFT73I/How-to-Use-Telerik-RadEditor-with-DotNetNuke-500-Release.aspx</link><description>NOTE:&amp;#160;Telerik DNN&amp;#160;Modules currently does not work with DotNetNuke 5.0.0 release when you try to install Telerik.DNN.Modules_2008_3_1125_trial.zip file from Host &amp;#160;&amp;gt;&amp;#160;Module Definitions page. To make it work i wrote a simple tutorial for DotNetNuke and Telerik users. I will add images to make it clearly understandable.

1) Download and install DotNetNuke v4.9.1 Release first.
2) Install Telerik Modules (Telerik.DNN.Modules_2008_3_1125_trial.zip) as a host user to DotNetNuke 4.9.1
3) Make sure it works by adding a page to DotNetNuke 4.9.1 installation called Editor Settings and insert a RadEditor Provider module from Control panel and switch FCK Editor to RadEditor and test it with any Text/HTML module instance on this portal.
4) Download and install DotNetNuke 5.0.0 Release
5) Do not install Telerik.DNN.Modules_2008_3_1125_trial.zip yet. Please read through the guide.
6) Copy the App_Code\TelerikWebUI directory (with contents) located under 4.9.1 release to same location at DotNetNuke 5.0.0 installation.
e.g for 4.9.1 installation my directory is: (E:\Webs\dnn491\App_Code\TelerikWebUI)
I copied the directory above to (E:\Webs\dnn500\App_Code\TelerikWebUI).
Note: dnn491 and dnn500 are the virtual directory names that i have created while installing dnn.
7) Copy Telerik.Web.UI.dll file from bin directory of 4.9.1 installation to bin directory of 5.0.0 installation.
8) Copy DesktopModules\TelerikWebUI directory of 4.9.1 installation to DesktopModules\TelerikWebUI of 5.0.0 installation.
9) Login to DotNetNuke 5.0.0 installation and navigate to Host &amp;gt; Module Definitions.
10) Select Create New Module from menu.
11) Using New Extension Wizard of DotNetNuke 5.0 you can create your module. Type RadEditorProvider at Name field.
12) Type RadEditor Provider at Friendly Name field.
13) Type Telerik RadEditor HtmlEditorProvider for DotNetNuke 5.x at Description field.
14) Select 5.0.0 as version and click to Next button.

15) Ensure that Business Controller Class field is empty and click to Next button.

16) Fill the Owner Details Wizard (i am not sure this step is required) and click to Next button.

17) Now you will be redirected to Host &amp;gt; Module Definitions page. Find RadEditor Provider from list and click pencil icon next to it. This will let you edit extension.

18) At Configure RadEditor Provider Extension Settings &amp;gt; Module Definitions, click to Add Definition button.

Type Telerik RadEditor Provider to Friendly Name field and ensure that Default Cache Time is set to 0. Click to Create Definition button.

19) Now navigate to Module Controls section and click to Add Module Control button.

At Edit Module Control Wizard, type RadEditorWebUI for Title and select DesktopModules\TelerikWebUI\RadEditorProvider\RadEditorWebUI.ascx from drop-down list. Don't change other fields and click to Update button.

20) Now add a new page to your DotNetNuke 5.0 installation and name it like Telerik Settings.
21) From top control panel, add RadEditor Provider to ContentPane.

22) Now you should be able to switch between RadEditor and FCK from this panel. Select RadEditor Provider from list and click to Enable This Editor button.

23) Ensure that RadEditor Provider works by editing any Text/HTML module content.
</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Sun, 04 Jan 2009 16:45:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:308</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/308/How-to-Use-Telerik-RadEditor-with-DotNetNuke-500-Release.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/306/How-to-Backup-DotNetNuke-via-Hosting-Control-Center.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=306</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=306&amp;PortalID=28&amp;TabID=525</trackback:ping><title>How to Backup DotNetNuke via Hosting Control Center</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/smrm4Jh3WrA/How-to-Backup-DotNetNuke-via-Hosting-Control-Center.aspx</link><description>Sometimes we need to take backups of application database plus file structure and copy &amp;amp; move it to another location to troubleshoot problems or test new features. DotNetNuke does not have built-in backup module yet. Assuming you are using Godaddy for hosting your DotNetNuke portal, i thought about writing a simple tutorial about how to backup dotnetnuke from your hosting control panel.
Before Begin

    Ensure that you are using one of Godaddy Windows Hosting Plans (Economy Plan does not apply for this tutorial)
    Install Java Runtime Environment (this will help you to browsing files without the need of installing third party FTP Client)*
    Install a FTP Client (e.g Mozilla Filezilla)

Here We Go Again
Open Godaddy website and login to your account.
Navigate to Hosting - My Hosting Account page.

Click to Manage Account button for the domain you want to check. Hosting Control Center will be opened in a new window (or tab).


Click to Databases &amp;gt; SQL Server


Click to pencil icon that is located under Action tab. This will let you to view/edit details of selected database.
Find Backup button on the panelbar and hit it. Then click OK button.


Note:&amp;#160;Ignore Pending Packup text at the image above. I was just taking a backup at that time.
You may have to overwrite existing backup if Confirm File Override pop-up displays. If you don't want to override existing backup file with newly created one, then you should connect to your ftp account via a FTP Client (this is the first time Filezilla takes action) and rename existing backup file. If you don't have any FTP Client installed then you can use built-in File Manager&amp;#160; (requires JAVA to be installed) from Hosting Control Center.

Optionally rename existing backup file to prevent data loss. (e.g rename &amp;#160;DB_1002731.bak to&amp;#160; Existing_DB_1002731.bak

NOTE: I will add a short video for this step.


Hosting Control Center modules will backup your database and this process will take up to two hours.

After the operation you can find your backup file at db_backups directory at your FTP Account.

NOTE 2: I will also add another video which will be useful to learn entire backup process with Godaddy.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Mon, 29 Dec 2008 16:33:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:306</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/306/How-to-Backup-DotNetNuke-via-Hosting-Control-Center.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/302/Can-I-Install-a-DotNetNuke-in-my-Root-Folder.aspx#Comments</comments><slash:comments>2</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=302</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=302&amp;PortalID=28&amp;TabID=525</trackback:ping><title>Can I Install a DotNetNuke in my Root Folder</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/p8LoeVwqe4M/Can-I-Install-a-DotNetNuke-in-my-Root-Folder.aspx</link><description>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) with reading following tutorial.
How to Install DotNetNuke to Root Path of Your Hosting Account
I just updated my old tutorial and changed instructions for latest release of DotNetNuke and Godaddy Control Panel (Hosting Center).
I'm also going to update other Subscriber Tutorials. Keep an eye at this blog :)</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Wed, 24 Sep 2008 20:00:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:302</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/302/Can-I-Install-a-DotNetNuke-in-my-Root-Folder.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/301/DotNetNuke-Documents-Module-Has-New-Team-Member.aspx#Comments</comments><slash:comments>3</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=301</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=301&amp;PortalID=28&amp;TabID=525</trackback:ping><title>DotNetNuke Documents Module Has New Team Member</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/zFAjZ-rMjAM/DotNetNuke-Documents-Module-Has-New-Team-Member.aspx</link><description>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 ago.
My application has been accepted by project leaders.
Most of my readers know that i don't have expert developer skills, thats why i only selected "Localization, Testing and Documentation" tasks.
So far, i really enjoyed working with a team since it was a great experience for me to take role at a part of an open source application.
I hope to contribute more soon.
&amp;#160;</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Mon, 15 Sep 2008 11:56:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:301</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/301/DotNetNuke-Documents-Module-Has-New-Team-Member.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/300/Get-Latest-Release-of-DotNetNuke.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=300</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=300&amp;PortalID=28&amp;TabID=525</trackback:ping><title>Get Latest Release of DotNetNuke</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/k0S1pFiaGw8/Get-Latest-Release-of-DotNetNuke.aspx</link><description>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 upgrade your DotNetNuke installations to newest release.
Remember to take backups before proceeding.
I'm going to upgrade my tutorials to have competibility with new release of application.</description><dc:creator>Ismet Dumlupinar</dc:creator><enclosure url="http://www.dotnetnuke.com/DesktopModules/LinkExchange/Reciprocate.aspx?linkid=276" type="text/html; charset=utf-8" length="51489" /><pubDate>Sat, 13 Sep 2008 06:40:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:300</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/300/Get-Latest-Release-of-DotNetNuke.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/299/DotNetNuke-49-Published.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=299</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=299&amp;PortalID=28&amp;TabID=525</trackback:ping><title>DotNetNuke 4.9 Published</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/jt8ceh7dVD4/DotNetNuke-49-Published.aspx</link><description>DotNetNuke 4.9 release firstly announced as a replacement for DotNetNuke 4.8.5 release.&amp;#160; Then, core team was working on a few security issues and bug fixes for 4.8.5 release, now they decided to release a major package in order to provide better security and performance options.
You can review quick notes for bug fixes and enhancements by visiting DotNetNuke Blog.
Some Highlights from DotNetNuke 4.9 Package
&amp;#160;&amp;#160;&amp;#160; *&amp;#160; URL Rewriter issues fixed with new validation. Users will not be able to create duplicate pages in same level if Friendly URL Provider used.

&amp;#160;&amp;#160;&amp;#160; * Web Farm issues with File Based Caching Provider has been resolved. Invalid logic handled and code rewritten to fix the issue.

&amp;#160;&amp;#160;&amp;#160; * Dictionary errors handled. Those issues were causing low performance with caching.

&amp;#160;&amp;#160;&amp;#160; * Skin and XHTML competibility mode issue related to DIV based panes fixed. Now Turkish users can add modules to panes even they use XHTML skin packages.

&amp;#160;&amp;#160;&amp;#160; * A New Default Theme for installation.

&amp;#160;&amp;#160;&amp;#160; * A well looking new default installation template.

&amp;#160;&amp;#160;&amp;#160; * New skin object lets you have localized text at your skins.

&amp;#160;&amp;#160;&amp;#160; * Styles improved.

&amp;#160;&amp;#160;&amp;#160; * Search skin object now has Web and Site options as drop-down list.

&amp;#160;&amp;#160;&amp;#160; * New feature lets you know when a new language pack for your locale is ready for download.
New Releases of Modules packaged with DotNetNuke 4.9

    &amp;#160;&amp;#160;&amp;#160; Documents 04.01.00
    &amp;#160;&amp;#160;&amp;#160; Events 04.00.02
    &amp;#160;&amp;#160;&amp;#160; Help 03.00.02
    &amp;#160;&amp;#160;&amp;#160; HTML 04.08.01
    &amp;#160;&amp;#160;&amp;#160; Links 04.00.01
    &amp;#160;&amp;#160;&amp;#160; NewsFeeds 04.00.00
    &amp;#160;&amp;#160;&amp;#160; Repository 03.01.15
    &amp;#160;&amp;#160;&amp;#160; Survey 04.50.00
    &amp;#160;&amp;#160;&amp;#160; UserDefinedTable 03.05.01
    &amp;#160;&amp;#160;&amp;#160; Wiki 04.01.00

View full list of issues via change log.
&amp;#160;</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Sat, 13 Sep 2008 06:15:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:299</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/299/DotNetNuke-49-Published.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/297/DotNetNuke-490-Release-Dogfood.aspx#Comments</comments><slash:comments>2</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=297</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=297&amp;PortalID=28&amp;TabID=525</trackback:ping><title>DotNetNuke 4.9.0 Release Dogfood</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/Rys5AWJQ2Ck/DotNetNuke-490-Release-Dogfood.aspx</link><description>DotNetNuke 4.9.0 RC1 Dogfood
A replacement for DotNetNuke 4.8.5 release has been announced by Joe Brinkman. DotNetNuke team targeted to backport critical fixes for 4.x releases and i think this will be final release of DotNetNuke 4.x series.

 
DotNetNuke 4.9.0 release recenlty dogfooded at DotNetNuke offical website yesterday. I think we may see latest release at Downloads page in a few days.

DotNetNuke 4.9 Platform will make easier for community users to switch upcoming DotNetNuke 5.0 Cambrian platform.

Joe Brinkman blogged about Major Highlights, Updated Modules/Providers at following link:

DotNetNuke 4.9 Release Candicate</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Fri, 15 Aug 2008 21:19:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:297</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/297/DotNetNuke-490-Release-Dogfood.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/296/How-to-open-Navigation-Menu-items-in-a-new-window.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=296</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=296&amp;PortalID=28&amp;TabID=525</trackback:ping><title>How to open Navigation Menu items in a new window?</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/JC5bvAVNojA/How-to-open-Navigation-Menu-items-in-a-new-window.aspx</link><description>Open in new window for navigation menu items
Mauricio Márquez recently blogged about an option to have menu items open in a new browser window via a simple trick. He might think this is useful for some DotNetNuke users. I agree in most cases. But sometimes, it might cause other unexpected problems with custom modules.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Fri, 15 Aug 2008 20:06:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:296</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/296/How-to-open-Navigation-Menu-items-in-a-new-window.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/295/Hosting-Connection-Updates.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=295</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=295&amp;PortalID=28&amp;TabID=525</trackback:ping><title>Hosting Connection Updates</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/P8Ni1exm1Dg/Hosting-Connection-Updates.aspx</link><description>Hosting Connection Updates
Godaddy finally upgraded some auto-install applications to recent releases. Previously Hosting Connection would let us install DotNetNuke 4.8.0 automatically via My Applications page.
       
Now, when you browse Hosting Connection page, you will have option to install DotNetNuke 4.8.4 release automatically.
You can also upgrade your existing automatic installations, if you had kept existing settings of installation.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Fri, 15 Aug 2008 17:57:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:295</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/295/Hosting-Connection-Updates.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/294/Status-Update.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=294</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=294&amp;PortalID=28&amp;TabID=525</trackback:ping><title>Status Update</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/0GhbzBJeans/Status-Update.aspx</link><description>Currently i have been trying to present better instructions for my tutorials. Since Godaddy staff blamed me and banned me for advertising my website at their Hosting Connection forum, i am unable to read discussions located there. Anyway, i will continue publishing new tutorials.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Fri, 08 Aug 2008 23:02:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:294</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/294/Status-Update.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/293/How-to-Upgrade-to-DotNetNuke-484.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=293</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=293&amp;PortalID=28&amp;TabID=525</trackback:ping><title>How to Upgrade to DotNetNuke 4.8.4</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/5m7iCdObfbg/How-to-Upgrade-to-DotNetNuke-484.aspx</link><description>How to upgrade DotNetNuke to 4.8.4
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.4 (as for August 9, 2008) Currently DotNetNuke 4.8.4 fixes several security issues and it is strongly recommend to upgrade to this release.

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.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Fri, 08 Aug 2008 22:41:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:293</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/293/How-to-Upgrade-to-DotNetNuke-484.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/292/Portal-Alias-Disappears-after-Log-Out.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=292</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=292&amp;PortalID=28&amp;TabID=525</trackback:ping><title>Portal Alias Disappears after Log Out</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/tAOHXCoYJxI/Portal-Alias-Disappears-after-Log-Out.aspx</link><description>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.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Sun, 22 Jun 2008 22:34:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:292</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/292/Portal-Alias-Disappears-after-Log-Out.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/291/DotNetNuke-484-Fixes-3-Low-Security-Issues.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=291</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=291&amp;PortalID=28&amp;TabID=525</trackback:ping><title>DotNetNuke 4.8.4 Fixes 3 Low Security Issues</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/jjHJ6enQEMM/DotNetNuke-484-Fixes-3-Low-Security-Issues.aspx</link><description>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</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Sat, 21 Jun 2008 06:09:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:291</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/291/DotNetNuke-484-Fixes-3-Low-Security-Issues.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/288/New-Tutorials-Great-Features-Coming-Soon.aspx#Comments</comments><slash:comments>10</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=288</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=288&amp;PortalID=28&amp;TabID=525</trackback:ping><title>New Tutorials Great Features Coming Soon</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/bcFnlcdkrnU/New-Tutorials-Great-Features-Coming-Soon.aspx</link><description>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 &amp;amp; Law for Canadian people
    Furniture &amp;amp; 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.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Mon, 02 Jun 2008 20:25:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:288</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/288/New-Tutorials-Great-Features-Coming-Soon.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/287/DotNetNuke-483-Security-Release-Published.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=287</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=287&amp;PortalID=28&amp;TabID=525</trackback:ping><title>DotNetNuke 4.8.3 Security Release Published</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/4W1TgabxKiI/DotNetNuke-483-Security-Release-Published.aspx</link><description>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&amp;#160; 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.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Mon, 02 Jun 2008 20:09:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:287</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/287/DotNetNuke-483-Security-Release-Published.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/286/How-to-Upgrade-to-DotNetNuke-482.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=286</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=286&amp;PortalID=28&amp;TabID=525</trackback:ping><title>How to Upgrade to DotNetNuke 4.8.2</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/tEWs0GjAAQQ/How-to-Upgrade-to-DotNetNuke-482.aspx</link><description>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&amp;#160;instances. This tutorial will have different methods compared to other tutorials, as we might have permission problems if default instructions&amp;#160;would&amp;#160;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 :)</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Sat, 15 Mar 2008 14:35:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:286</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/286/How-to-Upgrade-to-DotNetNuke-482.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/285/How-to-Move-DotNetNuke-48-to-Root-Path.aspx#Comments</comments><slash:comments>18</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=285</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=285&amp;PortalID=28&amp;TabID=525</trackback:ping><title>How to Move DotNetNuke 4.8 to Root Path</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/rRDLgH1OaY0/How-to-Move-DotNetNuke-48-to-Root-Path.aspx</link><description>How to move DotNetNuke installation to root path
In this tutorial, i am going to cover&amp;#160;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.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Mon, 10 Mar 2008 20:59:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:285</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/285/How-to-Move-DotNetNuke-48-to-Root-Path.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/282/How-to-Setup-Godaddy-Windows-Hosting-Account.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=282</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=282&amp;PortalID=28&amp;TabID=525</trackback:ping><title>How to Setup Godaddy Windows Hosting Account</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/XFp0qEowdbc/How-to-Setup-Godaddy-Windows-Hosting-Account.aspx</link><description>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
</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Sat, 08 Mar 2008 20:59:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:282</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/282/How-to-Setup-Godaddy-Windows-Hosting-Account.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/280/DotNetNuke-481-Released.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=280</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=280&amp;PortalID=28&amp;TabID=525</trackback:ping><title>DotNetNuke 4.8.1 Released</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/yVY4_cOBsWI/DotNetNuke-481-Released.aspx</link><description>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&amp;#160;Server 2000 database. You will notice spakinz's comment on blog post and DotNetNuke team refreshed download packages after this report.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Sun, 02 Mar 2008 20:06:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:280</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/280/DotNetNuke-481-Released.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/279/Kodhedz-DotNetNuke-Firesale-Event-Scheduled-Today.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=279</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=279&amp;PortalID=28&amp;TabID=525</trackback:ping><title>Kodhedz DotNetNuke Firesale Event Scheduled Today</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/ZRidHD63IyU/Kodhedz-DotNetNuke-Firesale-Event-Scheduled-Today.aspx</link><description>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.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Tue, 15 Jan 2008 08:39:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:279</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/279/Kodhedz-DotNetNuke-Firesale-Event-Scheduled-Today.aspx</feedburner:origLink></item><item><comments>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/277/How-to-Move-DotNetNuke-47-to-Root-Path.aspx#Comments</comments><slash:comments>15</slash:comments><wfw:commentRss>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=525&amp;ModuleID=1091&amp;ArticleID=277</wfw:commentRss><trackback:ping>http://www.mynetnuke.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=277&amp;PortalID=28&amp;TabID=525</trackback:ping><title>How to Move DotNetNuke 4.7 to Root Path</title><link>http://feedproxy.google.com/~r/mynetnuke/~3/YcLYU4ISk-s/How-to-Move-DotNetNuke-47-to-Root-Path.aspx</link><description>How to move DotNetNuke installation to root path
In this tutorial, i am going to cover&amp;#160;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.</description><dc:creator>Ismet Dumlupinar</dc:creator><pubDate>Mon, 07 Jan 2008 09:13:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:277</guid><feedburner:origLink>http://www.mynetnuke.com/Blog/tabid/525/articleType/ArticleView/articleId/277/How-to-Move-DotNetNuke-47-to-Root-Path.aspx</feedburner:origLink></item></channel></rss>
