DotNetNuke Hosting with ASPHostPortal.com

BLOG about DotNetNuke CMS, latest technology and Special DotNetNuke Hosting Package with ASPHostPortal.com

DotNetNuke Hosting Tutorial - View Event Viewers in DotNetNuke

clock Julie 11, 2018 12:35 by author Kenny

In this tutorial, you will learn how to view error log exceptions in DNN. You will also able to specify which log exceptions you want to record or ignore.
To view the error logs, you will need to have administrator portal access. Once you have login on the website, please go to the admin menu and you will see there is a menu called Event Viewer.

By default, all the error or event logs will be displayed on the site, you have an option to narrow the result list by specifying the log type by selecting one of the option in the dropdown list.

How to turn off the event logs in DNN?

To turn off specific event logs in DNN is pretty simple, if you scroll further down, you will be able to see there is a button called Edit Log Settings.

To enable or disable the event log, click the pencil edit icon. This will load another window popup and there is a tick box for you to untick it if you want to disable the event log.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com
ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5/month only. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.



DotNetNuke - ASPHostPortal.com :: 10 Tips For DotNetNuke Skins for SmartPhones

clock Julie 28, 2016 20:28 by author Armend

10 Tips For DotNetNuke Skins for SmartPhones

DotnetNuke skinning is changing with the latest trends one of which is building websites for smartphones and handheld devices like iPod, iPad, Android-based smartphones and many more. In this Article I have shared 10 tips which will be extremely useful for DotnetNuke Skinning for smartphones and most handheld devices.

 

Tip #1

basic mobile styles
html, body {
background: #fff;
color: #000;
margin: 0;
padding: 0;
font: 12px/15px sans-serif;
}


Do not rely on support of font related styling

Tip #2

No width content, careful with floats

  • {width: auto;}
  • {float: none;}

Tip #3

Setting the viewport

Add to <head> section
<meta name=”viewport” content=“width=device-width”/>
In DNN, add to default.ascx
<script language=”javascript” type=”text/javascript” >
var script = document.createElement(“meta”);
script.name = “viewport”;
script.content = “width=device-width”;
document.getElementsByTagName(“head”).item(0).appendChild(script);
</script>

Tip #4

keep it simple

  • What are mobile visitors looking for?
  • What information do they want/need?
  • Do mobile visitors have time/interest in all of my tedious sidebar content?
  • With a barebones stylesheet, which elements are clearly superfluous?
  • Which navigational elements are absolutely necessary? Which are redundant?
  • Are there entire regions of my page that would be better off not displayed?


Display only the essential no leftpane or right pane

.leftpane, .rightpane {
display: none;
}

Tip #5

top navigation (vertical)
.mi, .mi .txt {display:block !important; text-align:left; margin:0 !important;}

Tip #6

Control image width

#content img {max-width: 250px;}
or
img {max-width: 250px;}

Tip #7

Slim headings
h1, h2, h3, h4, h5, h6 {font-weight: normal;}

Tip #8

links
Highlight links


a:link, a:visited {
text-decoration: underline;
color: #0000CC;
}
a:hover, a:active {
text-decoration: underline;
color: #660066;
}
Use the tel: de facto standard
<a href=“tel:+1999999999“>Call us!</a>
Avoid target=_blank

Tip #9

Forms

  • Minimum input
  • Do not use tables for layout
  • Use definition lists (dl, dt, dd)

Tip #10

  • Keep URIs of site entry points short
    www.example.org/example.html accept example.org/example
  • careful with color contrasts
  • Use (minimum) web standards
    XHTML 1.0 / HTML 4.01 / XHTML-MP, CSS 2.1, DOM 1, ECMAScript 3
  • Always specify a doctype
  • Use standard media types
    Static: JPEG, GIF, PNG / Dynamic: 3GP, AVI, WMV, MP4

Do not use the following tags

  • × frames
  • × tables for layout
  • × nested tables
  • × image maps
  • × graphics for spacing
  • × horizontal scrolling
  • × do not rely on plug-ins, DHTML behaviors, embedded objects or script

 

 



DotNetNuke - ASPHostPortal.com :: Tips To Make DotNetNuke Sites Run So Fast

clock April 28, 2016 20:08 by author Armend

Overview

First of all I want to start out by saying that a lot of the information that is displayed here can be found in previous blog postings.  Posts such as DotNetNuke Host Settings Explained, DotNetNuke Scheduler Explained, DotNetNuke Performance Settings Explained, and Simple DotNetNuke Performance Enhancements.  Are good starting points for some of the detail behind my recommended changes.

 

The following changes are simply the configurations that I have found to be the best "baseline" configurations.  Consideration is needed in regards to the site setup, update frequency, traffic, hosting environment and users to ensure that you have the proper setup for your specific environment.  I will discuss the settings section by section, simply noting the changes that are made.  Please reference the specific "Detail" document for more information.

DISCLAIMER: Follow these recommendations as a guide only, I am not responsible for any effects of implementing these changes.

Host -> Host Settings Changes

The first place I visit is the Host Settings page.  There are a number of key updates and changes needed in this section.  Again, only changes are noted here.

Appearance

In this section I unchecked the "Show Copyright Credits" box

Advanced -> Authentication Settings

In this section I unchecked "Enabled" for any provider that will not be used in the portal, typically the LiveId and OpenId providers

Advanced -> Performance Settings

In this section I change the "Module Caching Method" to Memory.  the "Performance Setting" to HeavyCaching.  And the "Compression Setting" to GZip Compression.

Advanced -> Other Settings

In this section I change the "Scheduler Mode" to Timer.  I enable the "Event Log Buffer" and I disable the "Auto-Sync File System" option
These are the most common Host Settings changes that I complete.  Depending on the site I'll make a few other small edits.

Host -> Scheduler Changes

The biggest change that I make here is to change the "SearchEngineScheduler" task to run typically once every 12/24 hours.  This reduces a big load on the server.

Other Changes

From a DotNetNuke configuration change that is all that I modify.  Overall those changes typically result in very noticeableperformance improvements, but many times it just isn't enough to keep the sites running as smooth as possible.  So depending on the situation I have a number of other items that I work with.

Regular Purging of Event Log

As most people that have used DotNetNuke have discovered the EventLog table can become a very troublesome hindrance on the performance side of a site.  Enabling the Event Log Buffer helps reduce the effects of a large EventLog, however, the best policy is to clean the EventLog on a regular basis.
I do this one of two ways.  On my own sites I have an SSIS package within SQL Server that truncates the table every 24 hours.  On client sites I utilize my Scheduled SQL Jobs module to keep a 7 day rolling history of the EventLog data.  The key here is that we MUST keep the event log small.

Skin Selection and Menu Provider

The next item of consideration is a multi-part consideration.  I focus on finding CSS based skin layouts that utilize third party menu components such as Telerik and Css NavMenu.  With a simple skin change to sites I have noticed page load times that have reduced by over 50%.
Finding a good designer that creates well laid-out skins with third party menu providers has been a key performance enhancement, at least in the page.  I have NOT benchmarked these numbers though since DNN 4.6.2, so the core menu provider might have better performance.

Compression/Caching Modules

As a last step, if I really need to get the most performance out of a site I will tend to lean towards Snapsis PageBlaster as a good option.  I currently use PageBlaster on this site only and have had very good luck with it, although when configuring the module you must be careful to test all functionality first.  This was another change that once implemented I noticed very visible performance improvements.

Summary

There you have it, that is my secret trick to improving DotNetNuke site performance!  Many people charge a lot of money to make these simple performance tweaks and I just laid them all out on the table for you free of charge.



DotNetNuke Hosting - ASPHostPortal.com : How To Enable Google Analytics on a DotNetNuke Website?

clock Oktober 22, 2015 21:25 by author Kenny

How To Enable Google Analytics on a DotNetNuke Website?

Google Analytics is one of those must-have tools when running a website.  The tasks of tracking traffic sources, browser versions, search terms, etc. are all made easy.  The developers of DotNetNuke have also made using Google Analytics on a DotNetNuke website simple.

Installing Google Analytics in DotNetNuke is a fairly common request from many individuals and I know it can be a quite troubling question for most. The primary questions are how and where can I put the javascript code provided by Google. Well you have a few options. First you could put the code directly in the skin for the site, the advantages to that would be that you will automatically have the code on all pages, however, the disadvantage is that you cannot use that skin as is on another portal due to the site specific Google information. I personally go the route of adding a text/html module to my site and set it to show on every page and insert the script in a very specific location which I will discuss below. There are a few drawbacks to this method. First you will not get any statistics information on traffic to "edit pages" where other modules are not displayed and you also will not receive information regarding administration modules. However, in most circumstances this shouldn't be an issue.

The best way to include this information is to include the information in the Module header of the text/html module. This is to prevent the accidental removal of the script code if you happen to click inside the module as an admin to enter in-line edit mode. Below I will walk you through the steps needed to implement Google Analytics using this method. (NOTE: you can extend this for other javascript integrations if needed).

Step By Step

  • Add a new Text/HTML module to a page of your site, you can position it anywhere, but I recommend the bottom of the page as administrative users will still see the module when they are logged in
  • Edit the text of the module to contain no text
  • Enter the module settings from the SolPart Action Menu
  • Expand the "Advanced Settings" section
  • Check the box next to "Display Module On All Pages?"
  • Insert your Javascript code in the "Header" box. This will ensure that the data is always retained
  • Now under "Page Settings" -> "Basic Settings" un-check the following boxes
    • Display Container
    • Allow Print
    • Allow Syndicate
  • Ensure that the "Cache Time" is set to 0 (Caching appeared to cause issues with this implementation in my testing)
  • Click "Update" to save your changes

This should complete the setup. You may now test to ensure everything is functioning correctly. You can log out as an administrator and view your site and no extra content should be displayed however if you look at the generated source you should see your javacript listed. Google Analytics should update within about 15 minutes to show that they are receiving your data.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.



DotNetNuke Hosting - ASPHostPortal.com : How to Add JavaScript to DNN Page?

clock Oktober 15, 2015 09:51 by author Kenny

How to Add JavaScript to DNN Page?

What is JavaScript?

JavaScript is a programming language used to make web pages interactive. It runs on your visitor's computer and doesn't require constant downloads from your website. JavaScript is often used to create polls and quizzes. JavaScript support is built right into all the major web browsers, including Internet Explorer, Firefox and Safari. Provided that the visitors to your site are using web browsers that support JavaScript (most do) and have JavaScript enabled (it is by default), then your JavaScript will run when they visit the page. JavaScript is an interpreted language, so no special program is required to create usable code. Any plain text editor such as Notepad (one of the Accessories that comes in Windows) is quite satisfactory for being able to write JavaScript. That said, an editor that colorizes the code to make it easier to see what is what makes it easier to find your mistakes.

Step by Step

  1. Navigate to a DNN page where you want to place slideshow
  2. Click on “Edit Page” located at right side of Admin bar and choose “Edit this page”, this will turn page to Edit mode.
  3. Say (you have already setup images) on top of content page, then click Modules menu in Admin bar, then click on “Add new Module”.
  4. Choose HTML Editor Module from the list of modules and drag it below to slide show (location of module not mandatory, but a best practice)
  5. Select settings from “gear” action menu of newly added module and remove value from “Module Title” and uncheck Is Sharable (this will prevent share this content across site) under Advanced Settings then click on “Update”
  6. Select Edit content from “pencil” action menu of new module, this will opens a word like editor.
  7. Choose “Basic Text Box” located in left top corner, this will show plane textbox, type relevant JavaScript code here.
  8. Finally choose “Raw” as Render mode located at bottom of the editor and Click on “Save”. This will attach our Script code with page.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.



DotNetNuke Hosting - ASPHostPortal.com :: What's New in DotNetNuke 7.4.2?

clock Oktober 8, 2015 12:19 by author Kenny

What is New in DotNetNuke 7.4.2?

The latest version of DotNetNuke is 7.4.2. This version has been released at October 6th 2015. This release is maintenance release, bug fixes and support for incremental updates.

SECURITY ISSUES

This release resolves the following two security issues:

  • 2015-06 (Low) Potential XSS issue when using tabs dialog
  • 2015-07 (Medium) Users are getting registered even though User Registration is set to None

What started out as a relatively small maintenance release has turned into one of their largest maintenance releases ever. They spent a lot of time working to resolve a number of password management and multi-language issues along with a few performance enhancements. In total, they ran well over 5000 manual and automated tests on this release with a 99% pass rate.

MAJOR HIGHLIGHTS

  • Added upgrade support from beta release
  • Fixed issue with lists in custom registration form
  • Fixed issue with ignore words in Italian and French
  • Fixed issue with site export in multi-language site
  • Fixed issue where parameters in return URL were malformed
  • Fixed issue in sitemap for multi-language site
  • Fixed issue where control panel did not render links correctly in SSL offload environments
  • Fixed issue where pages with future start date were inaccessible
  • Fixed multiple password reset issues
  • Fixed issue where site settings could be duplicated
  • Fixed issue where dismissing all notifications removed messages as well
  • Fixed issue where file link for missing file caused exception
  • Fixed issue where localized portal settings were not getting applied when switching languages
  • Fixed issue where admin was unable to change interface language
  • Fixed issue where page name uniqueness was applied cross language
  • Fixed multiple scheduler issues

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.



DotNetNuke Hosting - ASPHostPortal.com :: How to Create a Backup of DNN and The Database

clock September 23, 2015 07:51 by author Kenny

How to Create a Backup of DNN and The Database

This topic is very important and requires a bit of planning, especially if you do not have direct access to your database server to perform your own backups. In the following sections I will first talk about what you must backup and why some of those items are very important. I will then discuss how to perform a DNN backup and SQL Server backup.  Finally I will discuss options available for third party modules for performing backups for individuals that do not have direct access to their servers.

What to Backup?

Simply put, it is a best practice to backup your entire DotNetNuke directory on the web server as well as a full backup of the database. Some people will say that you can get by with only backing up the "portals" folder, this is not correct! To successfully restore a DotNetNuke installation you must ensure that you have all module .dll and other code files you also must have the same validation and decryption keys.  I have found that the only real method to keep your data safe is to create a backup with all files.  Given the limited file size of the core DNN installation I have not found this to be a hinderance, especially since the additional files that exist in my website are all related to the content available within and is something I must have a backup.

Performing The Backup

Performing a backup of DotNetNuke is a fairly easy two step process. First I will discuss backing up the DNN installation directory, then I will discuss options available for backing up the database.

Backing up The DotNetNuke Directory

You have two options when backing up the DotNetNuke directory. If you have direct access to the server, you can simply right click on the DotNetNuke directory and select "Send To:" -> "Compressed (Zipped) Folder". This applies for most versions of the windows operating system. You will then have a file named dnn441.zip where dnn441 was your directory name. This zip file will contain all needed backup files, you will want to store this in a safe location.

If you do not have direct access to the server and can only access it via FTP you will have an additional step to obtain a zip file for your site. You will want to connect to your FTP site and COPY all files to a temporary location on your local computer. Once all files have been copied you will want to create a zip file including ALL files and folders that were just downloaded.

NOTE: if using a program such as WinZip for zipping, ensure that the "Use Folder Names" option is enabled so that the folder structure is preserved within your zip archive.

Backing up The DotNetNuke Database

To backup the database you must have access to the database server and the file system of the database server. If you are in a hosted environment you will need to rely on your hosting provider to obtain a backup, or you will need to look into a potential third party solution to backup the database from within DotNetNuke. If you have full access to the server please use one of the below sets of instructions to backup your database..

Backing up a Database with SQL Server and Enterprise Manager

Follow the below steps if you wish to create a databse backup file from Enterprise Manager for SQL Server using Enterprise Manager.

  • Navigate to your specific database in Enterprise Manager
  • Right click on the database and select "All Tasks" -> "Backup Database.."
  • Ensure that "Complete" is selected for the backup type
  • Click the "Add" button in the "Destination" section
  • In this section provide a full file path to the desired backup file, typically named databasename.bak where databasename is your database name
  • Click "Ok" to generate your backup, you will receive a success notice upon completion
  • You will now have a full backup file containing all tables and data for your database.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.



DotNetNuke 7.4.1 Hosting - ASPHostPortal.com :: How to Use the Text DotNetNuke Skin Object

clock Augustus 28, 2015 11:54 by author Kenny

How to Use the Text DotNetNuke Skin Object

DotNetNuke is a web content management system based on Microsoft .NET. The DNN Platform Edition is open source. DNN is designed for multi-tenancy and supports an unlimited number of websites, either as root websites or for portals in a parent-child configuration. The platform's skinning feature separates content from design-related files for easier customization. Skins make it simple to maintain a common look and structure across related sites without advanced programming knowledge. DNN's core functionality can be expanded with modules for common elements, such as those for e-commerce. The software enables parent-child website resource sharing and management using specially-formed symbolic links.

How to Use the Text DotNetNuke Skin Object

What is a Skin Object?

First of all, a skin object is an ASP.Net user control that is used in DNN skins to provide a limited feature.  For example, the search box, menu, login link, copyright statement, and more, are all skin objects.  They allow a skin designer to include dynamic content without having to know how to build the content itself, or knowing any programming.

Other than the previous description, this post will assume that you know how to create and package your own skin.

Text Skin Object

The Text skin object itself is a very useful feature in skinning, as it allows you to include localized text, while not having to create a copy of the skin for each language, or using any other number of workarounds.

For example, if you have static text next to your login skin object that says, “Welcome, “ then you might want to have alternatives for another language, if you plan to support it.

I am going to use that example for the rest of this post.

The Code

There is minimal code needed to implement the Text skin object.  If you’re using an HTML skin, then you would simply need to do the following:

<object id="dnnTEXT-Welcome" codetype="dotnetnuke/server" codebase="TEXT">
    <param name="Text" value="Welcome, " />
    <param name="CssClass" value="NormalBold" />
    <param name="ResourceKey" value="Welcome.Text" />
    <param name="ReplaceTokens" value="False" />
</object>

If you are using a ASCX skin, then you would need two updates.  First, put this line of code into the top section of the source:

<%@ Register TagPrefix="dnn" TagName="TEXT" Src="~/Admin/Skins/Text.ascx" %>

Next, put this code into the appropriate spot of the source in the skin:

<dnn:TEXT runat="server" id="dnnTEXT-Welcome" Text="Welcome, "
CssClass="NormalBold" ResourceKey="Welcome.Text" ReplaceTokens="False" />

Resource Files

Next, you need to make sure your skin has resource files.  In your skin package, you should have a folder namedApp_LocalResources.  This folder will contain the necessary files to tell your skin the appropriate text to use for the skin object when the specific language is asked for during page request life cycle.

If your skin file is named index.ascx or index.html, then your default resource file for English would be namedindex.ascx.resx.  If your additional supported language is French, your filename might be index.fr-FR.ascx.resx.

The English file code would be something like this:

<?xml version="1.0" encoding="utf-8"?>
<root>
  <data name="Welcome.Text">
    <value>Welcome, </value>
  </data>
</root>

The respective code for the French language file might look like this:

<?xml version="1.0" encoding="utf-8"?>
<root>
  <data name="Welcome.Text">
    <value>Accueil, </value>
  </data>
</root>

Text Skin Object Properties Explained

There are a few properties that you’ve seen in the previous examples that you might be wondering about.  Here is an explanation of those properties:

  • Runat – (required, ASCX only) The value must be ‘server’ 
  • Id – (required) This is a unique name for the tag, much like in standard HTML 
  • Text – (optional) This value will be used as the default, should an appropriate resources file for the current language not be found 
  • CssClass – (optional) This value is the name of a CSS class that will be available to the rendered HTML page to stylize the text in the web browser 
  • ResourceKey – (required) This value references the id (name) of the text to retrieve from the resources file 
  • ReplaceTokens – (optional) This true/false value will tell DNN to look for system tokens and replace them with the appropriate text


DotNetNuke Hosting With ASPHostPortal :: How to modify DotNetNuke Login Page? The Easy Way

clock Maart 16, 2015 05:42 by author Mark

The DNN login page is the most forgotten part in all DNN users and even some professional DNN portals like PokerDiy.com and neoteo.com. There are few modules that allow you to have a simplified login or pop up login like digg.com but you need to pay or it and it is not cheap and easy to change the design.
dnn-login-sample

In order to make changes to your DNN Login page, you have to understand the components in the login module. The DNN Login module consists of 4 parts which is the DNN Membership Authentication System, The Authentication Provider, The Login Module itself and the Language Resources Files (.resx).

The linkage of these components are as below:
Login Module loads Authentication Provider(s) into it and the provider as a gateway to the DNN Membership Authentication System. For example, if a user using LiveID to login your DNN Portal, the LiveID Authentication Provider redirect the user to MSN LiveID Gateway and then pass the credential back to your DNN Portal and match it with the DNN Membership Authentication System.

Login Structure

However, DNN Membership Authentication System also consist of Member Registration, Password Reminder and Forgot Password Question which makes the designing work on Login Works kinda tricky, not even need to mention the words that are loaded from the language resource files.
Ok, lets start changing those ugly interface! First we need to locate all the files that need to be changed. You will need to have FTP access to your DNN installation root.

Step 1: Changing the Login Module Container

The Login Module is basically the Admin’s Container by default where there is actually no login page but a “DNN Control” (Home/ctl/Login.aspx) unless you create a page and specified it in Admin > Site Setting > Advance Setting > Login Page.

Step 2: Locating Files that need to be changed

Now we need to locate the Login Authentication Providers at /DesktopModules/AuthenticationServices/ There will be 3 default providers which is DNN, LiveID and OpenID. You will find Login.aspx and Login.ascx.resx (under App_LocalResources) inside it and that are the files you are going to change it. For the DNN authentication files, you can get them at: /admin/Users/user.aspx and /admin/Authentication/login.aspx
Make sure you didn’t mixed up with login.aspx in providers.

Step 3: Changing the Text and Words

You can either change it using DNN Language editor which is located in Admin > Language in control panel are directly look for the files in FTP. I actually prefer the later method as it is more easier to read and modify using Visual Web Developer.
“Register” “Forgot and Password” at
/httpdocs/admin/Authentication/App_LocalResources/Login.ascx.resx
*If you have more than one portal, the file name will be “Login.ascx.Portal-0”

<data name="Remember.Text" xml:space="preserve">
     <value>Remember Login</value>
 </data>
 <data name="cmdForgotPassword.Text" xml:space="preserve">
    <value>Forgot Password ?</value>
 </data>
 <data name="cmdRegister.Text" xml:space="preserve">
     <value>Register</value>
 </data>

All you need to to change the text inside between the “value” attribute. I’d not recommend you to put html/css into it as it will increase the load time and may messing up xhtml coding standard…

Step 4: Changing the files.

First, we need to deal with the Login Tabs which is using the DNNTabStrip webcontrol. You can find this file at:
/httpdocs/admin/Authentication/Login.ascx
Inside the file, look for:

<DNN:DNNTabStrip
 ID="tsLogin"
 runat="server"
 TabRenderMode="All"
 CssTabContainer="LoginTabGroup"
 CssContentContainer="LoginContainerGroup"
 DefaultContainerCssClass="LoginContainer"
 DefaultLabel-CssClass="LoginTab"
 DefaultLabel-CssClassHover="LoginTabHover"
 DefaultLabel-CssClassSelected="LoginTabSelected"
 visible="false" />

The Css Classes are located at /Portals/_default/default.css by default. You can either change the css file, override it in skin.css / portal.css or redefine the classes in login.ascx
If you look at the pokerDIY login tabs, you will see that the tabs have been pushed into 2 lines which makes the layout very messy. You can simply widen it by changing the “width=160” to a larger number in the following lines and you will have the problem solved.

<asp:panel id="pnlLogin" runat="server" Visible="false">
     <table cellspacing="0" cellpadding="3" border="0" summary="SignIn Design Table" width="160">

Ok, now you have change the “Register” and “Forgot Password?” text but what about the design? For these, you need to look for “cssclass=”CommandButton” in the following lines located inside the same login.ascx.

<asp:Linkbutton id="cmdRegister" resourcekey="cmdRegister" cssclass="CommandButton" text="Register" runat="server"/>
 <asp:Linkbutton id="cmdPassword" resourcekey="cmdForgotPassword" cssclass="CommandButton" text="Forgot Password?" runat="server" />

We’ll leave the other parts of codes inside the file and CSS coding for a moment. Now we proceed to change another login.ascx which is located in:
/DesktopModules/AuthenticationServices/DNN.ascx
There are few basic things you need to change to make your login looks beautiful which are: The width, Label text/icon, login button, input box and the text inside it. You can find them in these lines:

<dnn:label id="plUsername" controlname="txtUsername" runat="server" resourcekey="Username" />
 <dnn:label id="plPassword" controlname="txtPassword" runat="server" resourcekey="Password" />
 <asp:textbox id="txtUsername" columns="9" width="150" cssclass="NormalTextBox" runat="server" />
 <asp:textbox id="txtPassword" columns="9" width="150" textmode="password" cssclass="NormalTextBox" runat="server" />
 <asp:button id="cmdLogin" resourcekey="cmdLogin" cssclass="DNNLogin" text="Login" runat="server" />

Like many others, you probably thought of removing the stupid help icon in the login page. It is simple if you’re only having a single language website version. All you need is to replace the <dnn:label to standard html code.
If you need to persevered the language resources function, you may substitute the dnn label control into standard asp label control as follow:

<asp:label id="plUsername" controlname="txtUsername" runat="server" resourcekey="Username" />

To change the textbox design as well as the font inside, simply look for <asp:textbox and change the cssclass value and thing applies to <asp:button for the login button.
After you’ve changed all the cssclass value in dnn.ascx, you may proceed to LiveID.ascx and OpenID.ascx using the same method.

Step 5: CSS Styling codes

Now we’ve reached into the hardest part where we need to use css to make a stylish login page. First, I would suggest you to put a new name for each of the value inside the CssClass attribute. This is because the default value are general classes which are shared with other modules and controls in the whole portal.

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5/month only. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.



DotNetNuke Hosting - ASPHostPortal.com :: How To Integrating your Zoom search page into DNN

clock Maart 15, 2015 11:36 by author Mark

Integrating your Zoom search page into DNN

At this point, you should have a working search page which you can access and perform search queries on as seen above. You can use your search page just as it is, and simply modify the "search_template.html" file to match the look of your site. However, if you want to further integrate the search page inside your DNN website (so that it will maintain the same skinning and various modules you are using), then read on.
First, we need to "Add" a new page in DNN to serve as your new Search Page. This will contain a search form, and your search results. You can name this something appropriate like "Site search".
On this new page, we will need to add an IFRAME module (if you do not see "IFRAME module" in the Modules list, you will need to login as "host" and "Find/Install additional modules"). You can title this added module as "Search" or something similar. Now click on the "Edit IFrame Options" button.
Here you should specify the Link Type as a URL, and copy and paste the URL of your working search page (from before) in the "Location:" text box as seen below. For the width, specify "100%" and we recommend a decent height of something around 600 pixels (or enable Auto height if your search page is on the same domain as your DNN site).

 

Next, click on the expand box next to the "QueryString Parameters" heading. We will need to add all the parameters that Zoom will use so that the page can pass these parameters along to the actual "search.asp" script within the IFrame. Click on the "Add QueryString Parameter" link and specify the following:

 

This allows the main search query to be passed to this page. If you would like to have more parameters in your custom search forms (search forms that you will place on other pages of your site), then you will need to add them here as well. If you are not familiar with the idea of the custom search form or what other parameters are necessary, don't worry, as this will be explained a little later below and you can come back here to add more parameters as needed.

 

Now click "Save" to return to your search page. You should now see your Zoom search page loaded within the IFrame of your DNN search page!

 

Run a few test searches and you should find that everything should be working within your new DNN search page.
If you wish to modify the text or layout (or the colours and fonts of the search results) within the IFrame, you will need to change the "search_template.html" file. Please see chapter 6 of the Users Guide ("How do I customize the look of my search page?") for more information.

Note: You may notice that when you click on a search result, the link opens within the IFrame of the search page. If you wish to change this behaviour, go to the Zoom Configuration window, and select the "Search Page" tab. Under "Results linking", change the selected option to "Frame or window:" and enter "_top" (without the quote characters, but note that the underscore is important) in the text box next to this option. Re-index your website and upload the files for this change to take effect. You will now find your search result links will open outside of the IFrame.

Additional note: If you make the IFRAME very tall, you'll find that when you click on the "Next >>" results link down at the bottom of the search results page, the browser would not scroll back to the top of the frame automatically. To fix this, edit your "search_template.html" file and replace the <body> tag with the following:

<body onload="location.href='#'">

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5/month only. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.



About ASPHostPortal.com

We’re a company that works differently to most. Value is what we output and help our customers achieve, not how much money we put in the bank. It’s not because we are altruistic. It’s based on an even simpler principle. "Do good things, and good things will come to you".

Success for us is something that is continually experienced, not something that is reached. For us it is all about the experience – more than the journey. Life is a continual experience. We see the Internet as being an incredible amplifier to the experience of life for all of us. It can help humanity come together to explode in knowledge exploration and discussion. It is continual enlightenment of new ideas, experiences, and passions


Author Link


Corporate Address (Location)

ASPHostPortal
170 W 56th Street, Suite 121
New York, NY 10019
United States

Tag cloud

Sign in