DNN is a great platform to build secure websites. But where do you start? The answer is to start with SSL encryption. But there are important Best Practices that will help you get the most value out of SSL on your DNN website or portal. Here is everything you need to know about implementing SSL certificate encryption on your website along other security pointers to help you get started making your site safe and secure.
The DNN Security team was recently informed of a security vulnerability in a third-party component suite that is used within DNN Products. It is critical that you follow the instructions provided in the link to ensure that your site isn’t compromised. …
Without doubt, DNN's role system is a powerful means for customising your site's content. The visibility of every single module on your pages can be configured on the basis of roles. By employing the technique, you can easily display additional content for super users, display some relevant information for your sellers, or hide products already bought from customers on your e-commerce website. But there is one central limitation.
Even though new versions of DNN modules are constantly released, too many module users still use older versions. Why? Well, maybe because they need concrete arguments to justify the price, time, or fear of the unknown, other than the usual “because it’s a new better version.”Therefore, I have put together 6 reasons (in no particular order) why DNNizens should update their modules.
Public: Content is viewable to anyone who can see the blog page.
Private: Content is only viewable by you.
Personal: Only the blog owner can publish blog entries.
Ghost Writer: The blog owner and any ghost writers can publish entries; blog owner is the displayed author.
All Bloggers: Any user who can blog can publish blog entries to this blog and the person publishing the entry is credited as the author.
Posts are available for others to use on their websites or to access through a newsfeed reader program