If you want to
remove
the ‘
Search
Web’ and ‘
Search
Site’ radio buttons from your DotNetNuke instance, you will have to open up the ascx for whatever skin you are using, and change the markup for the skin object like so:

[code:2qscbsur]
<dnn:SEARCH runat="server" id="dnnSEARCH" showWeb="False" showSite="False" />[/code:2qscbsur]

I had a need to delete all records in a certain table which matched some specific criteria, in this case, a PortalID. There were over 300 records, so using the GUI SQL Manager wasn’t going to cut it.

Here’s the code I used:

(Be sure to change the DatabaseName to match your own.

Table name: Modules, Field name: PortalID

DELETE FROM [DB_DATABASENAME].[dbo].[Modules] WHERE [PortalID] = 5[/code:4nd9nyef]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 1: Download and Extract DotNetNuke 4.5.1 Source Package into your local drive[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5]
[size=100:2a0r3ix5]Log in (or register) to DotNetNuke.com and get the latest source package available from Downloads page. Note that; you should download 4.x versions for ASP.NET 2.0 and 3.x versions for ASP.NET 1.1.[/size:2a0r3ix5][size=100:2a0r3ix5]After downloading source package extract it to a folder on your Desktop (for example Godaddy Practice folder).[/size:2a0r3ix5][size=100:2a0r3ix5]Now review the directory structure on extracted folder. You need to check Website folder under extracted folder. We are going to create many virtual directories to make it run at root level. Now, lets continue with next step.[/size:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 2: Godaddy Account Management[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5][size=100:2a0r3ix5]1) Click [/size:2a0r3ix5][url=http://www.godaddy.com/:2a0r3ix5][size=100:2a0r3ix5]here[/size:2a0r3ix5][/url:2a0r3ix5][size=100:2a0r3ix5] to open [b:2a0r3ix5]Godaddy.com[/b:2a0r3ix5]. Login to your account.[/size:2a0r3ix5]

[size=100:2a0r3ix5]2) Choose [b:2a0r3ix5]Hosting Servers > My Hosting Account[/b:2a0r3ix5] from main navigation menu.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]3) [b:2a0r3ix5]Manage Hosting[/b:2a0r3ix5] page will open. From there you will be able to pickup your hosting packages for listed domains. In this example I’ll be using my domain name, [url=http://www.mikroproje.net/:2a0r3ix5]mikroproje.net[/url:2a0r3ix5] as an example.[/size:2a0r3ix5]

[size=100:2a0r3ix5]4) Click [b:2a0r3ix5]check box[/b:2a0r3ix5] button and click on your domain name. Page will refresh with [b:2a0r3ix5]Hosting Account Details[/b:2a0r3ix5] like following picture.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]5) Click [b:2a0r3ix5]Open[/b:2a0r3ix5] button near your domain to open up [b:2a0r3ix5]Control Panel[/b:2a0r3ix5] for your hosting account. [b:2a0r3ix5]Hosting Manager [/b:2a0r3ix5]window will be open in a new window.[/size:2a0r3ix5]

[size=100:2a0r3ix5]6) In this window review important sections like [b:2a0r3ix5]Account Summary[/b:2a0r3ix5], [b:2a0r3ix5]Settings > ASP.NET Runtime[/b:2a0r3ix5] and make necessary changes if you need any.
[b:2a0r3ix5]It’s important that using ASP.NET 2.0 for DotNetNuke 4.x.[/b:2a0r3ix5]
[/size:2a0r3ix5]
[size=100:2a0r3ix5]7) Ensure that [b:2a0r3ix5]FrontPage Extensions[/b:2a0r3ix5] (under Settings tab) is not installed. (I have forgotten to mention about this requirement at first revision of this tutorial)

If installed, [b:2a0r3ix5]FrontPage Extensions[/b:2a0r3ix5] may prevent you from managing [b:2a0r3ix5]directory permissions[/b:2a0r3ix5].[/size:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step [/size:2a0r3ix5][/SIZE][/b:2a0r3ix5][b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]3: Virtual Directory Management
[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5][size=100:2a0r3ix5]In [b:2a0r3ix5]Hosting Manager[/b:2a0r3ix5] click on [b:2a0r3ix5]Content > Directory Management[/b:2a0r3ix5] button. [b:2a0r3ix5]Home > Content > Directory Management[/b:2a0r3ix5] page will open. Also open up [b:2a0r3ix5]Website[/b:2a0r3ix5] folder from extracted source package.[/size:2a0r3ix5] [size=100:2a0r3ix5]We are going to create [b:2a0r3ix5]Virtual Directories[/b:2a0r3ix5] and assign [b:2a0r3ix5]permissions[/b:2a0r3ix5] to these directories.[/size:2a0r3ix5] [size=100:2a0r3ix5]Click on [b:2a0r3ix5]Create Directory[/b:2a0r3ix5] button at bottom pane. (If you can’t see Create Directory button ensure that FrontPage extensions are not installed. If installed, simply uninstall them from Settings tab of Hosting Manager)[/size:2a0r3ix5] [b:2a0r3ix5][size=100:2a0r3ix5]Create a Custom Directory[/size:2a0r3ix5][/b:2a0r3ix5][size=100:2a0r3ix5] wizard page will open. Complete the form with following information:
[/size:2a0r3ix5]
[size=100:2a0r3ix5][b:2a0r3ix5][color=#a0a0a0:2a0r3ix5]Step 1: Enter a name:[/color:2a0r3ix5][/b:2a0r3ix5] [b:2a0r3ix5]_sgbak[/b:2a0r3ix5]
[b:2a0r3ix5][color=#a0a0a0:2a0r3ix5]Step 2: Select permisions:[/color:2a0r3ix5][/b:2a0r3ix5] [b:2a0r3ix5]Read, Write[/b:2a0r3ix5]
[/size:2a0r3ix5]
[size=100:2a0r3ix5]Click on [b:2a0r3ix5]Continue[/b:2a0r3ix5] and click on [b:2a0r3ix5]Add[/b:2a0r3ix5] buttons in order.[/size:2a0r3ix5] [size=100:2a0r3ix5]This is an example directory. [b:2a0r3ix5]_sgbak[/b:2a0r3ix5] contains [b:2a0r3ix5]visual studio template[/b:2a0r3ix5] file for DotNetNuke (DotNetNuke.vstemplate.2007-01-23.15-05-04.2416) (The numbers may differ)

Let’s make virtual directory creation process easier for further reading:[/size:2a0r3ix5][size=100:2a0r3ix5]Create [b:2a0r3ix5]App_Code[/b:2a0r3ix5], [b:2a0r3ix5]App_Data[/b:2a0r3ix5], [b:2a0r3ix5]App_Browser[/b:2a0r3ix5], [b:2a0r3ix5]bin[/b:2a0r3ix5], and [b:2a0r3ix5]Config[/b:2a0r3ix5] directories with [b:2a0r3ix5]Read & Write[/b:2a0r3ix5] permissions.[/size:2a0r3ix5] [size=100:2a0r3ix5]Create [b:2a0r3ix5]App_GlobalResources[/b:2a0r3ix5], [b:2a0r3ix5]Components[/b:2a0r3ix5], [b:2a0r3ix5]controls[/b:2a0r3ix5], [b:2a0r3ix5]DesktopModules[/b:2a0r3ix5], [b:2a0r3ix5]images[/b:2a0r3ix5], [b:2a0r3ix5]Install[/b:2a0r3ix5], [b:2a0r3ix5]js[/b:2a0r3ix5], [b:2a0r3ix5]Portals[/b:2a0r3ix5] and [b:2a0r3ix5]Providers[/b:2a0r3ix5] directories with [b:2a0r3ix5]Read, Web [/b:2a0r3ix5]and[b:2a0r3ix5] Write [/b:2a0r3ix5]permissions.[/size:2a0r3ix5][b:2a0r3ix5][size=100:2a0r3ix5]Update:[/size:2a0r3ix5][/b:2a0r3ix5][size=100:2a0r3ix5] You also need sub virtual directories for [b:2a0r3ix5]DesktopModules[/b:2a0r3ix5] and [b:2a0r3ix5]App_Code[/b:2a0r3ix5] directories.[/size:2a0r3ix5] [size=100:2a0r3ix5]Create [b:2a0r3ix5]DesktopModules\HTML[/b:2a0r3ix5] and [b:2a0r3ix5]DesktopModules\Links[/b:2a0r3ix5] directories with [b:2a0r3ix5]Read[/b:2a0r3ix5], [b:2a0r3ix5]Web[/b:2a0r3ix5] and [b:2a0r3ix5]Write permissions[/b:2a0r3ix5].[/size:2a0r3ix5] [size=100:2a0r3ix5]Create [b:2a0r3ix5]App_Code\HTML[/b:2a0r3ix5] and [b:2a0r3ix5]App_Code\Links[/b:2a0r3ix5] directories with [b:2a0r3ix5]Read[/b:2a0r3ix5] and [b:2a0r3ix5]Write[/b:2a0r3ix5] permissions.[/size:2a0r3ix5] [size=100:2a0r3ix5]Create [b:2a0r3ix5]godaddyroot[/b:2a0r3ix5] directory with [b:2a0r3ix5]Read[/b:2a0r3ix5], [b:2a0r3ix5]Web[/b:2a0r3ix5], [b:2a0r3ix5]Write[/b:2a0r3ix5], [b:2a0r3ix5]Set Root[/b:2a0r3ix5] permissions.[/size:2a0r3ix5] [size=100:2a0r3ix5]Check your settings again and click [b:2a0r3ix5]Add[/b:2a0r3ix5] button.[/size:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 4: Creating a MSSQL Server Database[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5][size=100:2a0r3ix5]In [b:2a0r3ix5]Hosting Manager[/b:2a0r3ix5] page, click on [b:2a0r3ix5]Databases[/b:2a0r3ix5] > [b:2a0r3ix5]SQL Server[/b:2a0r3ix5] button.

[/size:2a0r3ix5][size=100:2a0r3ix5]At [b:2a0r3ix5]MS SQL Server Databases[/b:2a0r3ix5], click on [b:2a0r3ix5]Create New Database[/b:2a0r3ix5] button.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]In [b:2a0r3ix5]Create SQL Server Database Wizard Instructions[/b:2a0r3ix5] page; write a simple description about your database at [b:2a0r3ix5]SQL Server Database Information[/b:2a0r3ix5] > [b:2a0r3ix5]Description[/b:2a0r3ix5] field. Check that [b:2a0r3ix5]Create DSN [/b:2a0r3ix5]option check box is signed. Provide your username and password at [b:2a0r3ix5]SQL Server Database Connection Information[/b:2a0r3ix5]. Make sure that [b:2a0r3ix5]Select Installation Option[/b:2a0r3ix5] > [b:2a0r3ix5]Install Schema Features[/b:2a0r3ix5] checkbox is signed. Click on [b:2a0r3ix5]Continue[/b:2a0r3ix5] button.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]In [b:2a0r3ix5]Verify SQL Server Database Changes Wizard Instructions[/b:2a0r3ix5] page, review your configuration and click on [b:2a0r3ix5]Create Database[/b:2a0r3ix5] button.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]System will process your request.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]After submitting your request you will see a message like following:
[b:2a0r3ix5]Successfully Submitted Information for Creation of SQL Server Database![/b:2a0r3ix5]
Notice that your newly created database’s status is currently [b:2a0r3ix5]Pending Setup[/b:2a0r3ix5].

[/size:2a0r3ix5][size=100:2a0r3ix5]This states that your request is being processed by Godaddy. Please wait approximately 15 minutes before continue.

After a break, lets continue with Database section. Your session may become ended. So may need to re-login to [b:2a0r3ix5]Control Panel[/b:2a0r3ix5].[/size:2a0r3ix5] [size=100:2a0r3ix5]Now check that your database status changed to [b:2a0r3ix5]Setup[/b:2a0r3ix5] mode.
[/size:2a0r3ix5]
[size=100:2a0r3ix5]This means your database is ready for usage.[/size:2a0r3ix5] [size=100:2a0r3ix5]You will see three icons at [b:2a0r3ix5]Actions[/b:2a0r3ix5] tab. Click on [b:2a0r3ix5]View Connection Strings icon[/b:2a0r3ix5] at Actions tab.[/size:2a0r3ix5] [size=100:2a0r3ix5]A [b:2a0r3ix5]pop-up[/b:2a0r3ix5] window will display your database connection strings. These strings are important and we need to implement connection strings to [b:2a0r3ix5]web.config[/b:2a0r3ix5] file. Copy the [b:2a0r3ix5]SqlConnection (.NET)[/b:2a0r3ix5] connection string and paste it into a [b:2a0r3ix5]notepad[/b:2a0r3ix5] file.[/size:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 5: Creating web.config File and Configuring Connection Strings and Other Settings (for SQL Server 2000/2005)[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5]
[size=100:2a0r3ix5]Locate the extracted [b:2a0r3ix5]Source[/b:2a0r3ix5] package and navigate to [b:2a0r3ix5]Website[/b:2a0r3ix5] folder. Find [b:2a0r3ix5]release.config [/b:2a0r3ix5]file and rename it to [b:2a0r3ix5]web.config[/b:2a0r3ix5].[/size:2a0r3ix5] [size=100:2a0r3ix5]You need to change [b:2a0r3ix5]Connection Settings and Application Settings[/b:2a0r3ix5] strings to enable the [b:2a0r3ix5]communication[/b:2a0r3ix5] between DotNetNuke and [b:2a0r3ix5]SQL Server[/b:2a0r3ix5]. Open up notepad file that contains [b:2a0r3ix5]SqlConnection (.NET)[/b:2a0r3ix5] connection string and implement it to your [b:2a0r3ix5]web.config[/b:2a0r3ix5] file like following example:
[/size:2a0r3ix5][b:2a0r3ix5]
[B][size=100:2a0r3ix5]Default Connection and Application Strings:[/size:2a0r3ix5][/b:2a0r3ix5][/B]
[code:2a0r3ix5]
<connectionStrings>
<!– Connection String for SQL Server 2005 Express –>
<add
name="SiteSqlServer"

connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;
AttachDBFilename=|DataDirectory|Database.mdf;"
providerName="System.Data.SqlClient" />
<!– Connection String for SQL Server 2000/2005
<add
name="SiteSqlServer"
connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;"
providerName="System.Data.SqlClient" />
–>
</connectionStrings>
<appSettings>
<!– Connection String for SQL Server 2005 Express – kept for backwards compatability – legacy modules –>
<add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;
User Instance=True;AttachDBFilename=
|DataDirectory|Database.mdf;"/>
<!– Connection String for SQL Server 2000/2005 – kept for backwards compatability – legacy modules
<add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>
–> [/code:2a0r3ix5]

[size=100:2a0r3ix5][b:2a0r3ix5]Custom Connection and Application Strings for SQL Server 2000/2005[/b:2a0r3ix5] [/size:2a0r3ix5]
[size=100:2a0r3ix5](Works at Godaddy Hosting Packages – You need to modify Connection Strings with servername, database, username and password values – change this entries from notepad file that contains account specific information)[/size:2a0r3ix5]

[color=#a0a0a0:2a0r3ix5][size=100:2a0r3ix5][code:2a0r3ix5]
<connectionStrings>
<!– Connection String for SQL Server 2005 Express
<add
name="SiteSqlServer"
connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;
AttachDBFilename=|DataDirectory|Database.mdf;"
providerName="System.Data.SqlClient" /> –>
<!– Connection String for SQL Server 2000/2005 –>
<add name="SiteSqlServer" connectionString="Server=godaddydatabaseservername;
Database=databaseid;uid=databaseloginusername;pwd=databaseloginpassword;"
providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<!– Connection String for SQL Server 2005 Express kept for backwards compatability – legacy modules
<add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;
User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>
–>
<!– Connection String for SQL Server 2000/2005 – kept for backwards compatability – legacy modules –>
<add key="SiteSqlServer" value="Server=godaddydatabaseservername;Database=databaseid;
uid=databaseloginusername;pwd=databaseloginpassword;" />[/code:2a0r3ix5][/size:2a0r3ix5][/color:2a0r3ix5]

[color=#000000:2a0r3ix5][size=100:2a0r3ix5]If you have trouble viewing code you can download sample web.config file from following link:[/size:2a0r3ix5]
[/color:2a0r3ix5][url=http://www.mynetnuke.com/Portals/3/docs/godaddy.zip:2a0r3ix5][color=#000000:2a0r3ix5][size=100:2a0r3ix5]Godaddy Sample Web Config File[/size:2a0r3ix5][/color:2a0r3ix5][/url:2a0r3ix5][color=#000000:2a0r3ix5][COLOR=#c0504d][size=100:2a0r3ix5][I DID THIS][/size:2a0r3ix5][/color:2a0r3ix5] [/COLOR]

[size=100:2a0r3ix5]You also need to disable [b:2a0r3ix5]Compression[/b:2a0r3ix5] feature from [b:2a0r3ix5]httpModules[/b:2a0r3ix5] section.[/size:2a0r3ix5] [size=100:2a0r3ix5]Find following entry:[/size:2a0r3ix5]

[code:2a0r3ix5]
<add name="Compression" type="DotNetNuke.HttpModules.Compression.HttpModule,
DotNetNuke.HttpModules.Compression"/> [/code:2a0r3ix5] [size=100:2a0r3ix5]And change it to:[/size:2a0r3ix5][code:2a0r3ix5]
<!– <add name="Compression" type="DotNetNuke.HttpModules.Compression.HttpModule, DotNetNuke.HttpModules.Compression"/> –> [/code:2a0r3ix5]
[size=100:2a0r3ix5][b:2a0r3ix5]Update – Important Step:[/b:2a0r3ix5] You must also change [b:2a0r3ix5]UseInstallWizard[/b:2a0r3ix5] value to [b:2a0r3ix5]False[/b:2a0r3ix5] from [b:2a0r3ix5]appSettings[/b:2a0r3ix5] section. (Default value is true)[/size:2a0r3ix5]

[size=100:2a0r3ix5]Find the following entry:[/size:2a0r3ix5]

[code:2a0r3ix5]
<add key="UseInstallWizard" value="true"/> [/code:2a0r3ix5] [size=100:2a0r3ix5]And change it to:[/size:2a0r3ix5][code:2a0r3ix5]
<add key="UseInstallWizard" value="false"/> [/code:2a0r3ix5]

[size=100:2a0r3ix5]If you won’t disable the [b:2a0r3ix5]UseInstallWizard[/b:2a0r3ix5] feature, you will get [b:2a0r3ix5]permission[/b:2a0r3ix5] errors, and [b:2a0r3ix5]installation wizard[/b:2a0r3ix5] will warn you that it can’t continue.[/size:2a0r3ix5]
[size=100:2a0r3ix5]
By disabling Install Wizard you are going to make an [b:2a0r3ix5]advanced DotNetNuke install[/b:2a0r3ix5].

[b:2a0r3ix5]Optional:[/b:2a0r3ix5] You may need to [b:2a0r3ix5]register your app_code subfolders to generate granular assemblies during compilation[/b:2a0r3ix5] (following example contains information about how to apply subfolders for [b:2a0r3ix5]HTML[/b:2a0r3ix5], [b:2a0r3ix5]XML[/b:2a0r3ix5] and [b:2a0r3ix5]Survey[/b:2a0r3ix5] modules.

[b:2a0r3ix5]Note:[/b:2a0r3ix5] If you want to install these modules you must include their subdirectories under [b:2a0r3ix5]web.config[/b:2a0r3ix5] like following example. Some modules are problematic under [b:2a0r3ix5]medium trust[/b:2a0r3ix5] environments, but the workaround is simple. (However this solution does not always work with third party modules – eg: Bi4ce GoMap)

Find following entry:[/size:2a0r3ix5]

[code:2a0r3ix5]
<!– register your app_code subfolders to generate granular assemblies during compilation
<codeSubDirectories>
<add directoryName="sub-directory name"/>
</codeSubDirectories> –> [/code:2a0r3ix5]

[size=100:2a0r3ix5]And change it to:[/size:2a0r3ix5]

[color=#a0a0a0:2a0r3ix5][size=100:2a0r3ix5][code:2a0r3ix5]
<!– register your app_code subfolders to generate granular assemblies during compilation –>
<codeSubDirectories>
<add directoryName="HTML" />
<add directoryName="Survey" />
<add directoryName="XML" />[/code:2a0r3ix5][/size:2a0r3ix5][/color:2a0r3ix5]

[size=100:2a0r3ix5][b:2a0r3ix5]Optional:[/b:2a0r3ix5] If you want to [b:2a0r3ix5]upload large files[/b:2a0r3ix5] with [b:2a0r3ix5]DotNetNuke[/b:2a0r3ix5], you must configure web.config to allow large file uploads.

Default section is allows you upload a maximum of 8192 kb (8 MB)[/size:2a0r3ix5]

[color=#a0a0a0:2a0r3ix5][size=100:2a0r3ix5][code:2a0r3ix5]
<!– allow large file uploads –>
<httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" requestLengthDiskThreshold="8192"/>
<httpCookies httpOnlyCookies="true" requireSSL="false" domain="" />[/code:2a0r3ix5][/size:2a0r3ix5][/color:2a0r3ix5]

[size=100:2a0r3ix5]I’m using a custom string configured for allowing large file uploads – a maximum of 262144 kb (256 MB):[/size:2a0r3ix5]

[color=#a0a0a0:2a0r3ix5][size=100:2a0r3ix5][code:2a0r3ix5]
<!– allow large file uploads –>
<httpRuntime executionTimeout="400000" useFullyQualifiedRedirectUrl="true" maxRequestLength="262144" requestLengthDiskThreshold="262144" />[/code:2a0r3ix5][/size:2a0r3ix5][/color:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 6: Sending Website Folder to FTP[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5]
[size=120:2a0r3ix5][b:2a0r3ix5]Update:[/b:2a0r3ix5] [b:2a0r3ix5][color=#a0a0a0:2a0r3ix5]Prevent Other Users to Access Host and Admin Accounts After Upload[/color:2a0r3ix5][/b:2a0r3ix5] [/size:2a0r3ix5]
[size=100:2a0r3ix5]Now navigate to local [b:2a0r3ix5]Website[/b:2a0r3ix5]\[b:2a0r3ix5]Install[/b:2a0r3ix5] folder from Windows Explorer
For example: [b:2a0r3ix5]C:\Documents and Settings\Administrator\Desktop\DotNetNuke_4.5.1_Source\Website\Install[/b:2a0r3ix5]
And open up DotNetNuke.install.config file with a text editor (like notepad) and change host and admin user account passwords. (default host password is: dnnhost and default admin password is: dnnadmin)
Save the file and close the application.

After finishing previous steps you need to upload your files to the web server via FTP. You may want to use a free client like[url=http://filezilla.sourceforge.net/:2a0r3ix5]Filezilla[/url:2a0r3ix5] for uploading your files to web server.
[/size:2a0r3ix5][b:2a0r3ix5]
[size=100:2a0r3ix5]Lets explain how to use Filezilla for your hosting account.[/size:2a0r3ix5][/b:2a0r3ix5]
[size=100:2a0r3ix5][b:2a0r3ix5]Download[/b:2a0r3ix5] and [b:2a0r3ix5]install[/b:2a0r3ix5] latest version of [b:2a0r3ix5]Filezilla client[/b:2a0r3ix5] and run it. Use [b:2a0r3ix5]CTRL+S[/b:2a0r3ix5] combination to open up [b:2a0r3ix5]Site Manager[/b:2a0r3ix5] window. Create [b:2a0r3ix5]new website profile[/b:2a0r3ix5] for your website (you may skip this step if website profile already exists).[/size:2a0r3ix5]

[size=100:2a0r3ix5]In [b:2a0r3ix5]Site Details[/b:2a0r3ix5] section enter your domain at [b:2a0r3ix5]Host[/b:2a0r3ix5] field. [b:2a0r3ix5]Default port[/b:2a0r3ix5] value is [b:2a0r3ix5]21[/b:2a0r3ix5]. Do not change this value unless told otherwise. Default value for [b:2a0r3ix5]Server type[/b:2a0r3ix5] field is [b:2a0r3ix5]FTP[/b:2a0r3ix5]. Do not change this field too. Choose [b:2a0r3ix5]Normal[/b:2a0r3ix5] as [b:2a0r3ix5]Logon Type[/b:2a0r3ix5]. Provide your [b:2a0r3ix5]username[/b:2a0r3ix5] and [b:2a0r3ix5]password[/b:2a0r3ix5] at [b:2a0r3ix5]User[/b:2a0r3ix5] section. Click on [b:2a0r3ix5]Save and Exit[/b:2a0r3ix5] button to record changes.

Use [b:2a0r3ix5]CTRL+S[/b:2a0r3ix5] again to open up and connect to newly created Website. Choose your website and click on [b:2a0r3ix5]Connect[/b:2a0r3ix5] button.[/size:2a0r3ix5]

[size=100:2a0r3ix5]After connecting you will see storage area at right pane. [b:2a0r3ix5]Remote site[/b:2a0r3ix5] field should include your website account username (for example: /username). Also you should see the virtual directories created at [b:2a0r3ix5]Step 3[/b:2a0r3ix5].

Now navigate to local [b:2a0r3ix5]Website[/b:2a0r3ix5] folder (extracted from source package at [b:2a0r3ix5]Step 1[/b:2a0r3ix5]) from [b:2a0r3ix5]Local Site[/b:2a0r3ix5] field at left pane.[/size:2a0r3ix5]

[size=100:2a0r3ix5]For example: [b:2a0r3ix5]C:/Documents and Settings/Administrator/Desktop/DotNetNuke_4.5.1_Source/Website[/b:2a0r3ix5].

[b:2a0r3ix5][color=#a0a0a0:2a0r3ix5]Important note:[/color:2a0r3ix5][B]Upload all folders[/b:2a0r3ix5] (!) in the [b:2a0r3ix5]/DotNetNuke_4.5.1_Source\Website[/b:2a0r3ix5] directory to [b:2a0r3ix5]/username/[/b:2a0r3ix5] directory at FTP server. But do not upload [b:2a0r3ix5]files[/b:2a0r3ix5] yet.
[/B]
[/size:2a0r3ix5]
[size=100:2a0r3ix5]Upload all remaining files (!) to /username/godaddyroot/ directory at FTP server.[/size:2a0r3ix5]

[size=100:2a0r3ix5]Since we cannot change root permissions of our username directory, we need an alternative way. It comes at next paragraph.

After finishing uploading files, read following section carefully!!!
Navigate to /username/godaddyroot/ directory from FTP client. Select all files with pressing CTRL+A keys. Move (you can use drag and drop feature) all of the files to parent directory (/username/ directory).

Navigate to /username/Config/ directory from FTP client. Simply select Compression.config, SiteUrls.config and SolutionExplorer.oml.config files and drag and drop them to parent directory (/username/ directory).[b:2a0r3ix5]

[B][color=#a0a0a0:2a0r3ix5]Knowledge Base: The difference between Copy and Move actions.[/color:2a0r3ix5][/b:2a0r3ix5]
[/B]Copying files between directories do not keep file permissions. The files inherit new permissions of directory. But moving files keeps file permissions. So in this example we practiced how to fight with Godaddy.

Lets say we have two directories called Directory A, Directory B.
Directory A is a parent directory and has only read permission.
Directory B is a sub directory and has read, web, write and root permissions.

If we copy files at Directory B and paste them under Directory A, effective permissions of the files will be only read. Because files will inherit permissions of Directory A.
But if we move files from Directory B to Directory A file permissions will remain.

You can practice this example with your operating system (Windows XP, Windows 2000, Windows Server 2003 and Windows Vista) (With NTFS permissions) [/size:2a0r3ix5]

[b:2a0r3ix5][size=120:2a0r3ix5][SIZE=130]Step 7: Installing DotNetNuke[/size:2a0r3ix5][/SIZE][/b:2a0r3ix5]
[size=100:2a0r3ix5][b:2a0r3ix5]Lets continue with last step to install DotNetNuke over Godaddy root directory[/b:2a0r3ix5].
After moving files from [b:2a0r3ix5]/username/godaddyroot/[/b:2a0r3ix5] to [b:2a0r3ix5]/username/[/b:2a0r3ix5] you should be able to install [b:2a0r3ix5]DotNetNuke[/b:2a0r3ix5] without any errors.

[b:2a0r3ix5]Browse[/b:2a0r3ix5] http://www.yourwebsiteaddress.com/Insta … de=Install and [b:2a0r3ix5]DotNetNuke[/b:2a0r3ix5] installation will start. Ensure that installation completes without any errors. Once installation completed you should immediately change your [b:2a0r3ix5]Host[/b:2a0r3ix5] and [b:2a0r3ix5]Admin[/b:2a0r3ix5] accounts’ passwords.

If you have any errors while installing DNN, please read this [b:2a0r3ix5]documentation[/b:2a0r3ix5] again. If you believe this installation documentation misses some important step, contact me privately at (labfxdx at gmail dot com). Also you may want to discuss other issues about Hosting companies like Godaddy at our tech support forum (beta).

[b:2a0r3ix5]About this article:[/b:2a0r3ix5] This article is based on Official DotNetNuke Installation Guide (comes with Documentation Guide) and Unofficial [url=http://www.mikroproje.com/DotNetNukeArticles/tabid/283/articleType/ArticleView/articleId/79/Default.aspx:2a0r3ix5]How to Install DotNetNuke to Godaddy Root Folder[/url:2a0r3ix5] article (written by [url=http://www.mikroproje.com/:2a0r3ix5]Ismet Dumlupinar[/url:2a0r3ix5]) and contains important steps about installing DotNetNuke 4.5.0 and DotNetNuke 4.5.1 to Godaddy Root Folder.

[b:2a0r3ix5]My next article will contain following information.[/b:2a0r3ix5][/size:2a0r3ix5]
[size=100:2a0r3ix5]How to upgrade Godaddy Hosted DotNetNuke 4.4.1 to DotNetNuke 4.5.1.

This article will be based on Mitchell Seller’s articles.
[url=http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/55/DotNetNuke-Upgrade-Tips-Lessons-Learned.aspx:2a0r3ix5]DotNetNuke Upgrade Tips[/url:2a0r3ix5]
[url=http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/22/Default.aspx:2a0r3ix5]Upgrading DotNetNuke from Previous Versions[/url:2a0r3ix5]
[/size:2a0r3ix5]

So Apple wants you to pony up $14.99 for Pixar’s Cars when you already own the DVD? Nuh-uh. Don’t think so. Seems like you should be able to copy that DVD right to your iPod.

You can, provided you have the right tools and some time to kill. With free software and this tutorial, you can copy almost any DVD in your library to your iPod for on-the-go viewing. Let’s get ripping.

Lucky Mac users

Mac users have an easy solution in the form of open source gem http://handbrake.m0k.org/Instant HandBrake, which not only rips DVDs but also converts them to the iPod-friendly MPEG-4 format. (Hurry up with the Windows version, developers!) If you need help using it, try http://howto.diveintomark.org/ipod-dvd-ripping-guide/.

The Windows two-step

Windows users will need two programs:

http://www.mrbass.org/dvdrip/DVD Decrypter, which we’ve http://lifehacker.com/software/dvd/how-to-back-up-a-dvd-171504.phpfeatured in http://lifehacker.com/software/dvds/hack-attack-oneclick-dvd-rips-208866.phpnumerous how-to articles; and http://www.videora.com/en-us/Converter/iPod/Videora iPod Converter.
To summarize the process, you’re going to use DVD Decrypter to “rip” the contents of a DVD to your hard drive and Videora to convert those contents to a format the iPod likes–namely, MPEG-4. When all that’s done, you’ll use iTunes to copy the movie to your iPod, as you would any other video file.
http://lifehacker.com/assets/resources/2007/02/dvddecrypter1.png[/img
Step 1: DVD Decrypter[/size[list=1
Insert your DVD and start DVD Decrypter.
Click the Mode menu and choose IFO.
Click the Tools menu, select Settings, and then choose the IFO Mode tab.
In the Options section, click the File Splitting field and set it to None. Click OK to exit the Settings dialog.
In the right-hand section of the interface, click the Stream Processing tab and check the Enable Stream Processing box.http://lifehacker.com/assets/resources/2007/02/dvddecrypter2.png
Immediately below that box, uncheck everything except for the first video and audio items. In other words, only two boxes should be selected.
Back on the left side, in the Destination section, click the folder icon to determine where DVD Decrypter should place your ripped files. (I’m usually in favor of something like My Documents > My Videos > Movie Title.)
Finally, click Decrypt and be prepared to wait 20 minutes or so while the software does its thing.[/list:o[size=130Step 2: Videora iPod Converter[/size[list=1
Fire up Videora iPod Converter.
Click Setup, then click Browse next to the Output Videos field. This is where you’ll choose where to deposit your converted movie. I recommend My Documents > My Music > iTunes > iTunes Music > Movies, but only for sake of organization. You can output the movie anywhere, so long as you know where it’s going to land. Click Save to finish the operation.
Click Convert, and then click the Transcode New Video button.http://lifehacker.com/assets/resources/2007/02/videora1.png
Navigate to the folder on your hard drive containing the movie you just ripped. You’re looking for a file with a name like VTS_01_1.VOB. Select the file and click OK.
In the Title field, enter the name of the movie.http://lifehacker.com/assets/resources/2007/02/videora2.png
Finally, click Start and be prepared to wait upwards of two hours (the time varies depending on the speed of your PC, the length of the movie, etc.). Don’t be concerned if the progress meter gets to 100% and the software still appears to be running. It’ll finish when it’s finished.[/list:o[size=130Step 3: iTunes[/size
When Videora is done, all that remains is to start iTunes. If you followed my suggestion above, the newly converted movie should be in your Movies folder. If not, you’ll need to import it. (http://lifehacker.com/software/ipod/ultranewb-how-to-copy-videos-to-your-ipod-233275.phpHere’s how.) From there, just copy the movie to your iPod and start watching!
Before I go, let me pass on a few final tips. First, if you encounter a DVD that gives DVD Decrypter trouble, try http://www.dvdshrink.org/where.htmlDVD Shrink instead. Second, whenever possible, choose full-frame (rather than widescreen) versions of the movie. The video iPod’s screen is small enough already without losing more of the image to letterboxing.

For quite some time TomTom devices have been shipped with no software disk, the only copy of the map is the one loaded to your device.

Should things go wrong, or through modifying/customising your device you accidentally delete some files you must have a backup of the data to recover the situation.

The backup should be done before you do anything to the device, this way you can always recover the unit to the exact same standard it was when purchased. Read more »