Today we released minor bugfix releases for DNN Dynamic Roles (version 01.03.01) and DNN Google Analytics Advanced (version 01.00.01). Both fix Azure compatibility and EVS errors.
Today, we’re happy to announce the release of DNN Google Analytics Advanced, our second module that makes more of the popular .NET CMS platform DNN (formerly DotNetNuke). The module extends DNN’s built-in modules “Google Analytics” (DNN Platform) and “Google Analytics Professional” (Evoq Content). Continue reading
Using DNN’s default role system, you may know the following issue: When restricting the visibility of your site’s module to specific roles, the roles are connected by a logical OR. However, there are situations where you want a module to be visible only if a user is a member of two (or more) roles. Creating a separate new (combined) role and managing role memberships manually is complex and error-prone. DNN Dynamic Roles makes this job easy by extending DNN’s standard permission system and automating the process of managing role memberships. Continue reading
DNN Dynamic Roles can be used to detect an unsupported browser and or browser version in the DNN CMS platform. If an unsupported browser is detected, you can show an error message or update hint for example. Here’s how: Continue reading
We’re happy to announce today’s release of DNN Dynamic Roles 01.03.00. The new version features anonymous tracking – a powerful feature that keeps track of your dynamic roles even if your visitors log in on your website at a later point. Besides, the new version includes a new random rule as well as several bugfixes. Continue reading
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. Continue reading
Do you already have set up a static (“usual”) role in DNN, assigned some users to it, and want to turn it into a dynamic one now? That’s easy: Just create a new dynamic role with the same name using DNN Dynamic Roles. As the module integrates smoothly with DNN’s default role system, the users assigned manually will stay assigned. Continue reading
weweave is not only providing modules which extend DNN’s range of functions. We also actively support the development of the DNN CMS software itself.
Last week, we discovered a bug in DNN’s functionality for purchasing and installing new modules from within the CMS: As an extension publisher, you can make multiple versions of your module available for download. This is quite useful for customers if you employ a license model like we do: Our customers get one year of free updates for DNN Dynamic Roles. Thus, we’re required to make older versions of our module available as well. We can’t just delete old versions from the list of available downloads. Continue reading
If you have set up dynamic roles with complex rules that are expensive to evaluate, or you do not expect that the rule’s result will change from one second to another, you can use the dynamic role’s “Caching Time” setting to increase performance. In detail, after the rule is evaluated (and depending on the result, so whether the user was added to or removed from the dynamic role) the “Caching Time” defines the timespan in which the rule is not evaluated again. During this time the user’s role membership status remains unchanged.
One scenario for a rule where setting a “Caching Time” is recommended is a dynamic rule with trigger “Request” that’s based on geo localisation (see section “Geo Location” in the docs). Since most likely the user’s location won’t change from one request to the next, it is reasonable to use a suitable “Caching Time” to evaluate the rule only once in a while.