We've been doing a lot of DotNetNuke based E-Commerce projects lately. The projects we've done have really spanned a variety of store types (wine, audio files, church stuff, an automated shutoff system, resistors, printing products, and more), client types (wineries, churches, incentive programs, manufactures, master distributors) and feature requirements. So far, for all the DotNetNuke based E-Commerce sites we've built, we've used Catalook.
Catalook has a huge number of features, an immense number of configuration options, and is probably the worst implemented piece of software I've ever used. But it works. At times, though, I think it would be faster if I had just built the E-Commerce pieces of each of the sites from scratch.
Read More...
Comments (1)
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)