Very often we come across the requests to set larger file uploads for the editor in DotNetNuke.
The default setting allows you to upload 4mb which if you want to upload media files is not enough.

Here are the changes required to upload larger files via editor and file manager in DotnetNuke.
The example is based on using the TelerikEditorProvider set as the default html editor for the site and is based on DNN 6.01+

1. Setting the TelerikEditorProvider as the default editor for the site.

Under host HTML Editor Manager you can see the current provider and change it if required to TelerikEditorProvider

[Read the rest of this article...]

Actions: E-mail | Permalink | Comments (0) | Kick it! | DZone it! | del.icio.us | ReTweet

With the current growth of smart mobile and tablet market you can not ignore the fact that your site should be mobile ready. Any business or organisation has to take into consideration how their website will look on mobile devices. When developing in DotNetNuke there are few different approaches you can take.

Apart from creating mobile specific site located on its own url (for example mobile.mysite.com or mysite.com/mobile) maybe you should consider using the same portal and content for mobile devices as for desktops, just change method of delivery depending on the device used to access the site. The advantage of this approach is that you only have to maintain one site / portal.

Here are available options and their advantages.

[Read the rest of this article...]

Actions: E-mail | Permalink | Comments (2) | Kick it! | DZone it! | del.icio.us | ReTweet

To quickly add a meta tag or verification code to the page just place the code within Page Header Tags in the Page Settings >> Advanced Settings

[Read the rest of this article...]

Actions: E-mail | Permalink | Comments (0) | Kick it! | DZone it! | del.icio.us | ReTweet

When renaming, moving or deleting pages in your live DNN Portal it is important that you take into account the effect this has on SEO and your site users. If the page has been indexed by search engines you should always implement 301 redirects, this way you will avoid page not found errors and will transfer potential traffic and ranking to a new (or another) page.

DotNetNuke allows you to achieve this by changing the page settings. Here are the steps I follow on all of our production sites.

[Read the rest of this article...]

Actions: E-mail | Permalink | Comments (1) | Kick it! | DZone it! | del.icio.us | ReTweet

If you are developing in HTML5 or if you have researched the subject you have probably come across the HTML5 Boilerplate template. This is a robust HTML/CSS/JS file base for developing websites in HTML5 and was created by Paul Irish, Divya Manian and others - thanks guys for sharing your efforts. Please visit www.html5boilerplate.com to find out more about the project.

Looking at the boilerplate file set I thought it would be worthwhile to rework the code so it can be applied in the DotNetNuke skinning process. As a result I came up with the file set that that I now use as standard as a starting point for all of my skins,click here to download all in a zip format.

The idea behind it is that the files include all the necessary code to make your skinning job easier and faster, making sure that your skin will display correctly across different browsers and enables you to target those browsers via CSS. It is not a finished skin, just a collection of code that you can pick up or delete as required. As I said before this is a rework of the code published by HTML5 boilerplate crew and all the credit for the hard work should go to them.

[Read the rest of this article...]

Actions: E-mail | Permalink | Comments (7) | Kick it! | DZone it! | del.icio.us | ReTweet