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
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
If you are active in marketing your website, a common scenario is setting up landing pages. A good landing page exactly matches a visitors expectations. Thus, it’s a good practise to tailor your landing pages exactly to the source of traffic. For example, you may have one landing page which is addressed by a set of slightly different advertisements (i.e. Google AdWords, banner ads, affiliate marketing, etc.). DNN Dynamic Roles is great for customising your content depending on the source of traffic. Continue reading
We’ve just released version 01.01.00 of DNN Dynamic Roles – our module for the DNN CMS which allows for defining criteria which, when matched, automatically assign your visitors to roles (and unassigns them again when the criteria are not matched anymore). Continue reading
A few days ago, we introduced our product “DNN Dynamic Roles“. Now it’s time to go a bit deeper: What’s the purpose of this module? Who needs it? What can you do with it?
If you are a DNN administrator or editor, you probably know that a page is made up of several components, or “modules” in DNN’s language. You can control who is allowed to see which parts of your portal by employing roles: By adding and removing roles to each module’s permission list, you can widen or restrict the visibility of your page modules. The default setting is “All Users” can “View Module”. Quite a good guess in most situations. Continue reading