Quick tips for getting more from your skin.
Here's a compilation of tips and tricks for getting at more than just <%= SkinPath %> in your DNN skin.
To show the name of the Portal:
<%= PortalSettings.PortalName %>
To get the current portal's home directory (i.e. /portals/0 ) you would use:
<%= PortalSettings.HomeDirectory %>
Read More...
Comments (0)
You may have noticed that when you edit text in DotNetNuke, what you see in the editor window may not look like what you see when you save your changes. This is because the fckEditor applies a different stylesheet in the editor window instead of any of the actual site css files. To change this, all you need to do is edit the web.config file for the site and set the proper value for the StaticCSSFile variable in the FckHtmlEditorProvider section.
So search your web.config for StaticCSSFile. And update it to point to your desired css file (e.g. StaticCSSFile="~/Portals/0/Skins/MySkin/skin.css"). Save your changes and you should now see the proper styles when you edit content.
I initially tried making changes to the EditorAreaCSS variable in the fckconfig.js file as this is the standard place to make fckeditor changes but that proved to be a dead end. Not sure why the DNN folks implemented this in the web.config instead.
Comments (0)
DotNetNuke has a nice way to require unique passwords for all users. You can't simply go into the web.config, search for RequireUniqueEmail="False" and set it to RequireUniqueEmail="True". The problem is if there are already users with duplicate email addresses, bad things happen (It's been awhile since I've tried it and I don't remember specifically what happens but I know it wasn't handled well).
So, you need a way to remove the duplicate email addresses before you make the web.config change. This SQL will take care of it.
Read More...
Comments (0)
Don't get duped into buying a module just to add a PayPal button to your DotNetNuke website. Paypal will actually generate the code/HTML you need for you and then you can just paste that text into the Source view of a Text/HTML module.
Here's some sample code that you can modify with your own information:
But, if you log in to your PayPal account, there's a section where they will generate this code for you with a variety of options.
Comments (0)
This is something I've learned and forgotten at least 4 times. Writing these types of things here helps me remember and seem to help quite a few other people as well. So...
Usually in DotNetNuke, if you want to associate a resource file with your control, you just create a resource file with the same name as the ascx file plus the .resx extension and place it in your App_LocalResources directory. DotNetNuke and/or ASP.NET auto-magically associates the file with your code and it just works.
However, every time that I create a control that dynamically loads other controls, I spend 30 minutes looking at names and file placement and... trying to figure out why the resource file doesn't seem to be loading. Eventually, it comes to me, for dynamically loaded files, you must explicitly set the LocalResource file.
To do this add the following line to your PageLoad function in your dynamically loaded control:
LocalResourceFile = DotNetNuke.Services.Localization.Localization.GetResourceFile(this, "controlfilename.ascx");
To learn more about DNN Module Localization, check out the DotNetNuke Module Localization Guide.
Comments (0)