With DotNetNuke version 4.9.0 is included by default a Skin called MinimalExtropy. This Skin has a localizable label called TEXT, with which it is possible to show up different texts depending on the language that the portal has configured at a given time.

That text is configured inside a file stored in the following folder:
[RootFolder]\Portals\_default\Skins\MinimalExtropy\App_LocalResources\

Within DNNEnglish and DNNCastellano Language Packs for DotNetNuke v4.9.0 is included a ZIP file containing a file called  "index.ascx.yy-XX.resx" which is intended to be installed inside that same folder, and thus provide a correct localization for the Skin's Te ... Read more »

It is rather usual to find that Skins for DotNetNuke include the text "You are Here" before the BreadCrumb element. The BreadCrumb element is a Skin Label used to indicate which page of the site the user is navigating, and its hierarchical position within the site. It looks more or less like:

You are here >> Home - Products - Details

Where the user is supposed to be navigating the "Details" page that depends on "Products" and then on "Home".

The solution is the following: Inside the DNN installation look for the folder ~\Portals\_Default\Skins\ and within that, the Skin's folder for the currently applied Skin.

Read more »

What do I mean by "permanent"? Each time a new language pack is installed in DotNetNuke, all the *.resx default file set for that localization is overwritten. This means that any change made to any of those files will be lost.

Besides the standard default resource files edition possibility, DotNetNuke provides two ways to perform modifications on its text resources so that they will not get overwritten upon a new language pack installation. The first works for all portals of a given DNN installation and the second is only related with a specific portal. The first is called "Host level" and the second "Admin level".

Let's see how to perform the three modifications and the differences that each one has.

1. Standard System level messages modification

It consists in modifyin ... Read more »

DotNetNuke displays the current date using a standard LongDateString formatting. It often happens that the user would have preferred another way to display the current date, but the standard customization provided by .NET sometimes is just not the best solution.

After investigating a little the CURRENTDATE skin object, I have found that it is not really difficult to display the current date in any format.

In order to format the date the way you want, you only need to edit the file "CurrentDate.ascx.vb", which is stored inside the "~/Admin/Skins" directory.

Inside that file, look at the following code (and modify it to suit your needs):

Private Sub Page_Load(ByVal sender As< ... Read more »