DotNetNuke Hosting with ASPHostPortal.com

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

Free Trial DotNetNuke Hosting :: How to Hover Dropdown Menus for Responsive Twitter Bootstrap Skin for DNN 7

clock Maart 19, 2014 08:42 by author Kenny

Bootstrap is a free collection of tools for creating websites and web applications. It contains HTML and CSS-based design templates for typography, forms, buttons, navigation and other interface components, as well as optional JavaScript extensions.

Twitter's Bootstrap is an excellent set of carefully crafted user interface elements, layouts, and javascript tools, freely available to use in your next web design project. This video series aims to introduce you to Bootstrap; taking you all the way from downloading the resources, to building a complete Bootstrap-based website.

While in the process of developing our own Responsive Twitter Bootstrap Skin for DotNetNuke 7, we had to jump over a couple of hurdles. First we had to figure out how to implement a dropdown on hover menu. Secondly, we had to overcome the Bootstrap issue where once you are on a child page, you cannot navigate back to the parent page in the menu. Bootstrap is against both of these features, however we feel as though these features provide a user friendly interface, especially while using a tablet or smartphone. With that said, we wrote this article to save you the headache to incorporate these two features in your Responsive Twitter Bootstrap Skin for DotNetNuke 7.

 

The real beauty was that I realized, I had included both the data-toggle="dropdown" and the data-hover="dropdown". You must only use the data-hover="dropdown" to fix both issues! The correct code is below:

Now you will have dropdown on hover menu items AND will be able to navigate to the parent page from the child page.



Free Trial DotNetNuke Hosting :: How to Hover Dropdown Menus for Responsive Twitter Bootstrap Skin for DNN 7

clock Maart 19, 2014 08:42 by author Kenny

Bootstrap is a free collection of tools for creating websites and web applications. It contains HTML and CSS-based design templates for typography, forms, buttons, navigation and other interface components, as well as optional JavaScript extensions.

Twitter's Bootstrap is an excellent set of carefully crafted user interface elements, layouts, and javascript tools, freely available to use in your next web design project. This video series aims to introduce you to Bootstrap; taking you all the way from downloading the resources, to building a complete Bootstrap-based website.

While in the process of developing our own Responsive Twitter Bootstrap Skin for DotNetNuke 7, we had to jump over a couple of hurdles. First we had to figure out how to implement a dropdown on hover menu. Secondly, we had to overcome the Bootstrap issue where once you are on a child page, you cannot navigate back to the parent page in the menu. Bootstrap is against both of these features, however we feel as though these features provide a user friendly interface, especially while using a tablet or smartphone. With that said, we wrote this article to save you the headache to incorporate these two features in your Responsive Twitter Bootstrap Skin for DotNetNuke 7.

 

The real beauty was that I realized, I had included both the data-toggle="dropdown" and the data-hover="dropdown". You must only use the data-hover="dropdown" to fix both issues! The correct code is below:

Now you will have dropdown on hover menu items AND will be able to navigate to the parent page from the child page.



DotNetNuke Hosting - ASPHostPortal.com :: How to Optimize Your DNN Installation for Speed and Efficiency

clock Februarie 7, 2014 07:58 by author Jervis

Review some of the default DotNetNuke configurable settings, most of which have been configured for general ease of use. This article will show you how to modify some of these settings ito improve the overall performance of your DotNetNuke installation.

DotNetNuke is a large and flexible web platform and as such has many configurable settings. Most of these settings have been configured for general ease of use, so it is recommended that we review and modify some of these settings if we wish to improve the overall performance of a DotNetNuke installation.

1) Host Settings Configuration

Configuration - Check For Upgrades
When this option is enabled, your website will communicate with “DNN Corp” to check for upgrades. An upgrade check will be performed every time you view the module definitions page or if you view a page with the DNN control bar embedded.

We should turn this option off to reduce overhead and remove the annoying nag images.

Appearance - Show Copyright Credits
This feature injects the DNN copyrights into the page, this just adds more page weight and is not required.

We should turn this option off to reduce page overhead.

1.2) Request Filter Settings

DotNetNuke introduced the request filter feature starting with DotNetNuke 4.5.3, this feature enables you to setup request filters to block or redirect users.

If you do not specifically need this feature, then we recommend that you turn this option off.

1.3) Performance Settings

The default DotNetNuke performance settings are ok for testing environments but production environments will require these settings to be modified. The following sub sections will outline recommendations for the configuration of these items.

Page State Persistence
This setting determines whether the page’s view state is stored in the page or server memory. Although changing this option to “Memory” could reduce the overall size of the request sent to the user, in most cases it causes other problems and I personally recommend NEVER changing this value to anything other than “Page”.

Module Cache Provider
The module caching provider setting configures how DotNetNuke will store the output cache of its module objects. The proper configuration of this setting is dependent on the specific environment that the website will be hosted in. Shared Hosting and Dedicated hosting environments will typically see better results using “Memory” caching. In Cloud computing environments, disk based caching makes sense as website content is stored on a SAN or similar device with very good write speeds, and memory availability is limited.

Cache Setting
This performance setting is used to control how much of the underlying data is cached by DotNetNuke.
We recommend setting this option to “Heavy”.

Authenticated Cacheability
This setting is used to define the cacheability of content for authenticated users, this can be used to optimize what can and cannot be cached by downstream routers and machines when working with authenticated users. For more information on the values in this section please consult MSDN

I recommend that this setting is left at the default value.

Compression Setting
Enabling gzip compression is an easy way to reduce the size of the site payload and get a nice boost in performance. It is possible to disable the DotNetNuke compression and use IIS native compression, however, we have experienced issues with some third party modules and IIS level compression. Therefore it is recommended that we use the DNN functionality unless there is a specific need to compress at the IIS level.

Use Whitespace Filter
This setting will strip whitespace from your generated page content following the Regular Expression specified in the Whitespace Filter option under "compression settings". This option is NOT needed if you are using a compression method. If you are not using a compression method and still would like to see a reduction in page size you can use this option which will slim down the HTML size of your pages.

Output Cache Provider (DNN Prol Only)
This provider is used to cache the entire content of a generated page allowing for zero database lookups and page generation activities to be skipped for un-changed content. This option is not available in the community edition of DotNetNuke.

1.4) Other Settings

Enable Users Online
The Users Online feature allows DotNetNuke to show you which users are currently online. This process adds a fair amount of overhead and it is recommended that you do NOT have users online enabled.

Site Log History
The Site Log History setting controls the data retention policy used by the DotNetNuke Site Log.
We recommend that the Site Log History setting be set to “0” days which will disable all site log functionality.

Scheduler Mode
This setting controls how DotNetNuke scheduled tasks are triggered. The default configuration of “Request Method” requires that on page requests a check is performed to trigger any tasks. This mode introduces additional request overhead and can delay end-user experiences. We recommend setting this configuration option to “Timer Method”.

Enable Event Log Buffer
DotNetNuke writes all kinds of log entries to the event log, user login, page changes, etc. Enabling the event log buffer allows DotNetNuke to queue these log items to cache, thus reducing the number of database writes. Therefore it is our recommendation that this setting be enabled on all installations.

Auto Sync File System
This configuration option enables/disables the automatic file synchronization functionality. We recommend disabling this functionality as it is only needed if files are added to the portal via FTP on a regular basis.

2) Admin Settings

On DNN 5 portals, un-select “Enable Skin Widgets” if they are not being used. This will prevent additional page resources from being injected, and increasing the size of the page.

3) DotNetNuke Scheduler

This is another DotNetNuke sub-system that is worth configuring to ensure the website is optimized
for performance. The DotNetNuke task scheduler provides vital functionality, however if the tasks are
scheduled to run too frequently they will have an adverse impact on the websites performance.

We recommend the following task scheduler optimizations:

First disable all scheduler tasks that are not required by this website installation.

Configure “DotNetNuke.Services.Scheduling.PurgeScheduleHistory, DotNetNuke” to run every 12/24 hours (or whatever best fits your portal requirements, based upon how much Schedule Log your website generates)

Configure “DotNetNuke.Services.Search.SearchEngineScheduler, DotNetNuke” to run every 12/24 hours and retry after 24/48 hours. (again depending upon what best fits your portal requirements). Note: updating this setting will yield a significant improvement in performance.

4) DotNetNuke Event Log

Anyone who uses DotNetNuke for any period of time will soon discover that the “EventLog” can produce a significant hindrance on performance. It is very important to note that DotNetNuke by default does not clear the entries in “EventLog” table. Over time this table will grow to be very large.

You can enable the “EventLog” buffer feature, to minimize the impact, but I recommend truncating this table on a daily basis. This allows for a 24 hour rolling history for any diagnostics purposes and avoids rapid transaction log growth when deleting records. This can be accomplished a number of ways;

SQL Server Scheduled Job

Manual process

Or using a custom module.

Also disable all logs that are not essential for the website installation, this will reduce the number of database requests your website will need to perform, in particular:

Disable “Application Start” log entries

Disable “Application End” log entries

Disable “Scheduler Started”, “Scheduler Event Started” log entries

5) Authentication Providers

Starting with DotNetNuke 4.7.0 additional authentication provider modules were introduced. Website administrators can configure which authentication provider/s is used to authenticate the users against.

Most DotNetNuke sites will only require the standard DotNetNuke Authentication Provider. However, behind the scenes the website will incur a performance hit when additional authentication providers are enabled, even if they are not being utilized.

This performance hit is typically limited to the login page itself where DotNetNuke polls all enabled providers to see if they must be rendered, but the performance impact can be major.

It is our recommendation that all non-essential authentication providers should be disabled.



Press Release - ASPHostPortal.com Proudly Launches DotNetNuke (DNN) 7.2 Hosting

clock Januarie 16, 2014 06:08 by author Mike

ASPHostPortal.com is a premiere web hosting company that specializes in Windows and ASP.NET-based  hosting with innovative technology solutions, proudly announced the best DotNetNuke (DNN) 7.2 hosting  service with a combination of affordable price, high customer satisfaction rate and commendable quality.


DotNetNuke is an open source web content management system that is built on ASP.net infrastructure and  solely has its life wire running smoothly on Microsoft platform. Furthermore, it is an open source web  content management system that started in the year 2002 by a team of developers which was headed by the  original creator Shaun Walker who happens to have bagged his certification as a certified Microsoft Most  Valuable Professional in the year 2004 and the latest version is 7.2 with lots of awesome features.

DotNetNuke (DNN) 7.2 includes a number of new features and enhancements that will benefit users and  developers alike along with a large number of bug fixes. DNN 7.2 version incorporates some of the  interesting features to elevate the existing functionality and make your site administration process a  lot easier. DNN 7.2 also allows you to install JavaScript libraries as first party extensions. Once  installed your module or skin can request that JavaScript library and the platform will automatically  add the library into the page. The API mirrors the one used for jQuery and JQuery UI making it very easy  to use.

Some benefits that the DotNetNuke content management system includes are greater site consistency,  improved site navigation, streamlined authoring process, faster turnaround time for new pages and  changes, increased site flexibility, support for decentralised authoring, increased security, reduced  duplication of information, greater capacity for growth, and reduced site maintenance costs. DotNetNuke is the best CMS (content management system) for businesses and  is easier to create and manage with ASPHostPortal.com.

ASPHostPortal.com is a popular online DotNetNuke (DNN) 7.2 hosting service provider with all of its  hosting plans to help users to automate and simplify website and server administration tasks such as  installation and migration. For more information about this topics or have any enquiries related to DotNetNuke (DNN) 7.2 hosting,  please visit http://www.asphostportal.com/DotNetNuke-Hosting

About the Company
ASPHostPortal.com is a hosting company that best support in Windows and ASP.NET-based hosting. Services  include shared hosting, reseller hosting, and sharepoint hosting, with specialty in ASP.NET, SQL Server,  and architecting highly scalable solutions. As a leading small to mid-sized business web hosting  provider, ASPHostPortal.com strive to offer the most technologically advanced hosting solutions available to  all customers across the world. Security, reliability, and performance are at the core of hosting  operations to ensure each site and/or application hosted is highly secured and performs at optimum  level.



DotNetNuke Hosting - ASPHostPortal.com :: How to Upgrade DNN to The Latest Version

clock Januarie 7, 2014 10:31 by author Mike

DotNetNuke is an open-source content management system ideal for creating and deploying projects such as commercial websites, corporate intranets and extranets, and online publishing portals. DotNetNuke is built on a Microsoft ASP.NET (VB.NET) platform, and is easily installed and hosted with all of our Windows Hosting Plans. If there is an upgrade available, follow the following steps to perform the upgrade.

In Preparation:

  • Back up the DNN database
  • Back up all website files
  • Check your database and website backups!
  • Download the latest DotNetNuke upgrade package:
    a. From the www.dotnetnuke.com site. You may need login credentials if you are using a non-community version of DNN.
    or
    b. Click the "Upgrade Available" button that appears when you are *not* running the latest version.
  • Create a basic html document called app_offline.htm. This page will be shown on the site while you are doing the upgrade.

See figure about no maintenance page. Users may see errors while the site is partially upgraded.

No maintenance page

Good Example - HTML page to let users know the site is offline:

This site is offline for routine maintenance. Please check back later.

To Perform the Upgrade:

  1. Upload the app_offline.htm file to the root web folder for the site.
  2. Navigate to the site in a web browser and check that the app_offline.htm file is shown instead of the usual default page.
  3. Copy the contents of the latest DotNetNuke upgrade package over the top of the existing files. All files should be copied because the package should only contain generic files ?no configuration files.
  4. When the copy is complete, rename the app_offline.htm file to app_offline.htm.save. When you navigate to the site, you will see a new construction page:
    Remove underline
  5. Access the /install/install.aspx?mode=upgrade page (e.g.www.mysite.com/install/install.aspx?mode=upgrade) using a web browser. The site will begin an automatic upgrade process:
    Automatic upgrade running

  6. On completion of the upgrade, you will see the following message at the bottom of the page. Click on the link to return to the site.
    put an underline under the link

  7. Click through the newly upgraded site to perform a smoke test.
  8. Log in to the DNN site and navigate to "Host", then "Host Settings". You will see that the site is running the newest version of DNN and that there are no upgrades available.
    Latest version and no upgrades available


DotNetNuKE Hosting - ASPHostPortal.com :: 10 DotNetNuke Admin Quick Tips

clock Desember 20, 2013 06:45 by author Robert

Here are 10 somewhat lesser known "quick tips” for DotNetNuke administrators described in no more than a sentence or two and implemented just as quickly.

 

 

  • Module Header & Footer Text
    Use the module header and footer text boxes (Module Settings > Advanced Settings) to inject short snippets of text and / or HTML above or below any given module. No need to drop additional text/html modules.
  • Registration Copy
    I still see way too many sites with the default copy of “Membership to this portal is Private / Public / Verified. …” Change it via the language editor at Admin > Languages > Global Resources > SharedResources.
  • Login / Register Links
    And while you have the language editor running, customize the anchor text of commonly used skin tokens such as Login, Register, Terms, and Privacy at Admin > Languages > Local Resources > Admin > Skins. Alternatively, most of these tokens support a “text” attribute for overriding the anchor text directly in skin.ascx:
    <dnn:login runat="server" id="dnnLOGIN" text="Sign in" />
  • Page Header Tags
    Tucked away in the advanced page settings is a field that allows you to specify additional meta tags on a page by page basis. For instance, to keep Google from archiving the page, enter <meta name="robots" content="noarchive">.
  • Installation Date
    Ever lost track of when you or your hosting provider installed DNN for your site? The “InstallationDate” key in the appSettings section of web.config will tell you.
  • Terms of Use & Privacy Statement
    The default terms and privacy notice are meant as a general guideline only. If you are running a “high profile” site, have the documents reviewed by a legal professional and edit accordingly via Admin > Languages > Global Resources > GlobalResources (message_portal_terms.text and message_portal_privacy.text.) Even if the default copy is sufficient for your needs, mask the email address in the last paragraph of the privacy statement to avoid spam.
  • Website Administrator
    You have entered a valid email address in your DNN profile and double-checked the SMTP server settings and still don’t receive admin notifications from DNN? In case of multiple users with admin rights, you need to set yourself as the site administrator at Admin > Site Settings > Advanced Settings > Other Settings.
  • Module Title
    The module title field accepts roughly 250 characters including HTML/CSS. That’s good enough for little tricks such as adding a small image, link or vary the font size of words in the module title. Just don’t overdo it.
  • Copyright
    Similar to the module title field, I often enter additional information such as contact details into the copyright field (Admin > Site Settings > Site Details), which then conveniently display in the footer of your pages or wherever else you placed the copyright skin token.
  • Module Installation Timeout
    As modules get more sophisticated and provide more features and functionality, the file size of private assemblies (PAs) naturally grows as well. This may lead to HTTP session timeouts when uploading PAs the conventional way (Host > Module Definitions > Install New Module). While there are means to increase the session length in web.config, I prefer to simply FTP upload the PA zip file into the Install\Module folder on the web server and then change the file extension from .zip to .resources. Subsequently, the module is listed in the Available Modules section of the Modules Definition page and installation can resume from there.

At least half of the above suggestions should be applicable to any DNN version, while the other half is geared more towards DNN 4 and above.

 



Free DotNetNuke 7.1 Hosting :: Switching over from Url Master to the Advanced URL functionality in DNN 7.1

clock Desember 12, 2013 06:34 by author Mike

If you are planning to start using the new Advanced URL functionality in DNN 7.1, and you have an existing license for the Url Master module, there is a conversion path. This converts all of the Url Master redirects, portal alias settings and configuration settings over to the DNN format. The Advanced functionality is heavily based on the Url Master codebase, but they are not exactly the same. Many changes have been made in order to properly integrate the product into the DNN Core.

Therefore, I suggest that people test the switch-over carefully, and make sure that they have checked that redirects, third-party modules, and all other URL-related functionality works correctly. I strongly recommend that people do this in a 'localhost' test environment if they have the capability. If not, you must take a backup immediately prior to doing the conversion and be prepared to revert to the backed-up version of the site if the tests do not pass.

This process applies both to the DNN Platform (formerly DotNetNuke Community Edition) and those who have upgraded DotNetNuke Professional Edition to Evoq Content.   While the DNN Platform has very few UI configuration locations for the Advanced URL Settings, the functionality is fully operational once the Url Master settings are converted.

Please note : you need to have a fully licensed version of Url Master in order to activate the conversion functionality, except if you are running on ‘localhost’, in which case it will work with an unlicensed version.

The actual process of conversion is very simple:

1. Upgrade your Url Master version to 2.8

2. Go to the Host->Friendly Url Settings page, and find the 'Convert to DNN Advanced Urls' button.

image

3.  This will load the Conversion Dialog:

image

Click 'Start Conversion' when you are ready to do the conversion.

4.  The conversion process will run, and then show a summary of the changes made:

image

The figures in the boxes apply to the entire DNN installation. Check through the numbers to do a 'sanity check' and make sure that the figures seem correct. You can then close the dialog – the conversion is complete and your site is now activated in DNN 'Advanced' mode. Note that because this requires a web.config change, the site will automatically restart when the process is complete.  The 'close' button triggers a page refresh to complete this process.

5. Check functionality on your site to make sure that the conversion has worked correctly. A brief set of tests should include:

  1. Basic site operation : all public URLs work as expected
  2. Edit Mode : does the Edit Mode functionality work as before?
  3. Any third-party module functionality : do blog posts, forum threads, e-commerce pages, photo galleries etc load up correctly?
  4. Login/Logoff functions : are you able to login and log out as normal?
  5. 404 Handling : if you had 404 handling configured, check that the 404 error handling works as expected.
  6. Admin/Host Urls : are you able to do basic functions like search for a user, save site settings, etc?
  7. Custom Urls : do custom redirects you had configured in Url Master still work OK?  Are any custom URLs showing for pages correctly?
  8. Site Alias redirects : does the site respond correctly in terms of alias redirects (like example.com –> www.example.com)
  9. User Profile pages : if you had vanity user profile URLs activated, do they still work correctly?  Are the profile pictures showing correctly, can users post updates, edit their profiles?

This is only a brief list to get you thinking; you should execute a comprehensive test plan to make sure the site is working as expected.  Your SEO depends on making sure there are no surprises and everything is working as before. In the vast majority of cases, there should be no difference in behaviour or functionality, but it is imperative that this be tested and confirmed. While I have tested this functionality to make sure a like-for-like conversion of settings is working as expected, it is impossible to test the entire universe of Url Master installations.

6.  When the conversion is finished, it’s up to you whether or not you uninstall the Url Master module. You may wish to keep it installed as a backup for the short term in case you find a problem with the conversion process. You can run the conversion process as many times as you like – it has been designed to be run repeatedly without causing any issue, to allow for iterative checks. Each time it is run, the settings are taken from the Url Master configuration and applied to the DNN install – thus any changes in the DNN installation may be overwritten each time you do this.

Anyone using Custom Module Providers for the Url Master module – the settings specific to Custom Module Providers are not converted during this process.  Any Custom Module providers will have to be replaced like-for-like with a DNN 7.1 specific Extension Url Provider which provides the same functionality, and the settings specific to that provider will have to be carried across.



Free DotNetNuke 7.1 Hosting :: Switching over from Url Master to the Advanced URL functionality in DNN 7.1

clock Desember 12, 2013 06:34 by author Mike

If you are planning to start using the new Advanced URL functionality in DNN 7.1, and you have an existing license for the Url Master module, there is a conversion path. This converts all of the Url Master redirects, portal alias settings and configuration settings over to the DNN format. The Advanced functionality is heavily based on the Url Master codebase, but they are not exactly the same. Many changes have been made in order to properly integrate the product into the DNN Core.

Therefore, I suggest that people test the switch-over carefully, and make sure that they have checked that redirects, third-party modules, and all other URL-related functionality works correctly. I strongly recommend that people do this in a 'localhost' test environment if they have the capability. If not, you must take a backup immediately prior to doing the conversion and be prepared to revert to the backed-up version of the site if the tests do not pass.

This process applies both to the DNN Platform (formerly DotNetNuke Community Edition) and those who have upgraded DotNetNuke Professional Edition to Evoq Content.   While the DNN Platform has very few UI configuration locations for the Advanced URL Settings, the functionality is fully operational once the Url Master settings are converted.

Please note : you need to have a fully licensed version of Url Master in order to activate the conversion functionality, except if you are running on ‘localhost’, in which case it will work with an unlicensed version.

The actual process of conversion is very simple:

1. Upgrade your Url Master version to 2.8

2. Go to the Host->Friendly Url Settings page, and find the 'Convert to DNN Advanced Urls' button.

image

3.  This will load the Conversion Dialog:

image

Click 'Start Conversion' when you are ready to do the conversion.

4.  The conversion process will run, and then show a summary of the changes made:

image

The figures in the boxes apply to the entire DNN installation. Check through the numbers to do a 'sanity check' and make sure that the figures seem correct. You can then close the dialog – the conversion is complete and your site is now activated in DNN 'Advanced' mode. Note that because this requires a web.config change, the site will automatically restart when the process is complete.  The 'close' button triggers a page refresh to complete this process.

5. Check functionality on your site to make sure that the conversion has worked correctly. A brief set of tests should include:

  1. Basic site operation : all public URLs work as expected
  2. Edit Mode : does the Edit Mode functionality work as before?
  3. Any third-party module functionality : do blog posts, forum threads, e-commerce pages, photo galleries etc load up correctly?
  4. Login/Logoff functions : are you able to login and log out as normal?
  5. 404 Handling : if you had 404 handling configured, check that the 404 error handling works as expected.
  6. Admin/Host Urls : are you able to do basic functions like search for a user, save site settings, etc?
  7. Custom Urls : do custom redirects you had configured in Url Master still work OK?  Are any custom URLs showing for pages correctly?
  8. Site Alias redirects : does the site respond correctly in terms of alias redirects (like example.com –> www.example.com)
  9. User Profile pages : if you had vanity user profile URLs activated, do they still work correctly?  Are the profile pictures showing correctly, can users post updates, edit their profiles?

This is only a brief list to get you thinking; you should execute a comprehensive test plan to make sure the site is working as expected.  Your SEO depends on making sure there are no surprises and everything is working as before. In the vast majority of cases, there should be no difference in behaviour or functionality, but it is imperative that this be tested and confirmed. While I have tested this functionality to make sure a like-for-like conversion of settings is working as expected, it is impossible to test the entire universe of Url Master installations.

6.  When the conversion is finished, it’s up to you whether or not you uninstall the Url Master module. You may wish to keep it installed as a backup for the short term in case you find a problem with the conversion process. You can run the conversion process as many times as you like – it has been designed to be run repeatedly without causing any issue, to allow for iterative checks. Each time it is run, the settings are taken from the Url Master configuration and applied to the DNN install – thus any changes in the DNN installation may be overwritten each time you do this.

Anyone using Custom Module Providers for the Url Master module – the settings specific to Custom Module Providers are not converted during this process.  Any Custom Module providers will have to be replaced like-for-like with a DNN 7.1 specific Extension Url Provider which provides the same functionality, and the settings specific to that provider will have to be carried across.



DotNetNuke Hosting :: Tips Optimize your DNN site (SEO Friendly)

clock November 22, 2013 10:43 by author Mike

DotNetNuke has many SEO features, but some are less obvious to the casual administrator. These SEO features, however, can have a dramatic effect on how your DNN website is indexed by Google, Bing and others, and as such, can have an effect on your page rank and search results.

Here are a few DNN tips and tricks to help in your DNN’s SEO:

1. Site Map Priority
Buried within your page settings is a feature that allows you to set indexing priorities to your DNN pages. To get there (once logged in as an administrator), go to “page settings”, then “advanced settings”, then at the bottom of the window, go to “other settings”.

Here you will find the item: “Site Map Priority”. The default for this is .5. However, if your page is the home page, or perhaps a landing page, you will want to up the number to 1.0, or .9 (1.0 being the highest). This will increase the perceived importance of the page by search engines such as Google. Where is this relevant? When your organization appears in a Google search, high priority pages may be presented as sub-links to the home page more frequently. This can be critical in immediately directing visitors to key pages in an organic search result.

2. Site Settings

Here we’ll talk about one of things NOT to do when it comes to SEO in DotNetNuke. In the “site settings” of DotNetNuke, administrators have the ability to enter descriptions and keywords. By doing that, those items will then be placed in the META tags for EVERY page on the DNN website. For SEO, this is an extreme no-no, as it will confuse the search engines and reduce the relevancy and page rank of your overall DNN website. It may be an easy way to get keywords throughout your site… but it will definitely hurt you in the long run!

3. Page Titles
One of the nice features about DotNetNuke is its ability to add dashes between spaced words in your page title. For example, if you title a page “DNN SEO Tips”, DNN will title the actual URL as “DNN-SEO-Tips”. This ensures that the individual words in the title will be relevant to Google.
Some administrators like to use underscores between words. For example: “DNN_SEO_Tips”. This is strongly discouraged as Google will index the entire string as one item. This means people searching for DNN, or SEO or Tips will not see your site on Google. They would only find you if they specifically put “DNN SEO Tips”. In some cases this may be a good thing, if your content is very niche-oriented. But if you’re looking to gather visitors based on more broad searches, using underscores will hurt you.

4. Robots.txt
OK, this one gets a bit technical for the casual DotNetNuke administrator, but robots.txt is an important factor when comes to SEO, so what we’ll do in this section is give you enough information that you can intelligently go to your IT person or your hosting provider to ask questions.

In short, the robots.txt function (which not accessible via the administration tools in DNN), tells various search engines such as Google what pages to index and what pages they should not. Pretty important! But, if your DNN website is with a host provider and you are operating on a shared instance (one installation of DNN with many portals), you may be operating on one, centralized robots.txt file, which may be configured to tell the robots to ignore all pages on your site!

There is a way to take control and get around this, but it takes someone with access to the server and a bit of IT knowledge. But, don’t let that stop you from finding out if your robots.txt file is configured properly.

Ask your IT or host provider:
Is your DNN website on a shared instance?
Do you have an individual robots.txt file for your specific DNN website?

That’s it a few simple tools and information on how to squeeze more effectiveness with your DotNetNuke’s SEO. Hope useful.



DotNetNuke Hosting - Tips and Trick to Optimize DotNetNuke

clock April 25, 2013 10:41 by author andy_yo

A typical DNN install requires considerable server resources, and creates significant traffic between the database & web server. These techniques aim to reduce both of these where-ever possible, along with some other optimizations. Some of these may not apply to you, and I advise you to exert discretion in deciding which of these work best for you.

 

About ASPHostPortal.com
ASPHostPortal.com is Microsoft No #1 Recommended Windows and ASP.NET Spotlight Hosting Partner in United States. Microsoft presents this award to ASPHostPortal.com for ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2012, ASP.NET 4.5, ASP.NET MVC 4.0, Silverlight 5 and Visual Studio Lightswitch. Click here for more information

DNN Optimization:

  1. Host Settings
    1. Set the "Performance Setting" to "Heavy Caching".
    2. Depending upon Hosting resources, set the "Compression Setting" to "Deflate Compression" or "GZip Compression".
    3. Depending upon Hosting resources, enable "Whitespace filter" (not of much use, if you have also enabled compression).
    4. Disable "Users Online" for Installations on which "Users Online" module is NOT used.
    5. Set the "Scheduler Mode" to "Timer Method". "Request Mode" causes the Scheduler to be invoked on every request to a page of your installation.
    6. On sites where Logging is NOT mission critical, enable "Event Log Buffer", so that log entries are buffered before being flushed.
    7. On sites where the Site files do NOT update frequently, disable "Auto-sync filesystem".
    8. Uncheck "Enable Ajax" on portals that are just informative, and do NOT involve management tasks.
  2. Admin Settings
    1. On DNN 5 portals, unselect "Enable Skin Widgets" if they are not being used to prevent redundant skin file downloads.
  3. Log Settings
    Disable all Logs NOT required on an installation. In particular,
    1. Disable "Application Start".
    2. Disable "Application End".
    3. You might also want to disable others like "Scheduler Started", "Scheduler Event Started" etc. depending upon if they are not much useful to you. However, "Sceduler event Failure" should not be disabled to enable debugging of any scheduler issues.
  4. Schedule Settings
    Disable or customize all Schdules NOT required on an installation. In particular,
    1. Configure "DotNetNuke.Services.Scheduling.PurgeScheduleHistory, DOTNETNUKE" to run every 5 days (or whatever fits best to your portal depending upon how much Schedule Log your portal generates).
    2. Configure "DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE" to run every 5 days and retry after 1 day (again depending upon what fits best to your portal. There is no one size fits all approach here).
  5. Javascript & CSS Optimization
    1. Manually optimize all css & js files to remove redundant white-space (or use a free or paid DNN module e.g. Page Blaster to manage this task for you).
    2. Zero out portal.css (if you dont use it, or better still, delete it).
    3. Check ~/portals/_default/default.css for any styles not being used on your portal.
    4. Try to use any other menu except SolPart Menu.
    5. Try NOT to use table based skins (improves the perceived rendering of your page).
  6. Cookies: Set the appropriate value for Persistent & Session cookies in web.config.
  7. Compilation: If you are compiling DotNetNuke or any Extension from source, make sure that you compile the project in Release mode. Moreover, make sure you have debug="false" in web.config for your production sites.



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