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
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
Improving DNN: How we fixed DNN’s built-in extension system only showing the first file for a product
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.
We’ve just released DNN Dynamic Roles Version 01.02.00 with several useful new features. Continue reading