Opposite permissions in Dynamicweb suddenly does not work

Hi!

We are developing a new webshop with both public and secured product catalog. A few of the products in the public webshop cannot be bought in the secured webshop.

Therefore we have used opposite permission like: all users are allowed to see these product catalogs except the extranet users from a given usergroup. This functionality worked in Dynamicweb 8.1.2.4, but after upgrading to Dynamicweb 8.2.1.11, this function doesn't work.

Take a look at this little screencast running on Dynamicweb 8.1.2.4:

http://co3.dk/files/files/screencasts/permission-in-dw-8-1-2-4.swf

How can it be that this suddenly does not work?

Is this a bug that have been fixed as mentioned by the support guys at the DW office or should this be working?

Any ideas to a nice workaround without spoiling the navigation templates with conditions and hardcodes?

- Allan, Co3

Hi Allan,

The opposite scenario was an issue for a lot of our partners, so we fixed it in DW8, since we found it unlikely that anyone would use the Extranet in this way - we were wrong about that it seems :)

However, it does not make much sense to deny a user the possibility to see a page if all he has to do is to log out to be able to see it.

It might be possible to solve the issue in an other way, if you want to make sure a certain user-group cannot see a certain paragraph or page. You could consider writing this into your template somehow or maybe using OMC-profiling for this:
http://manual.dynamicweb-cms.com/Default.aspx?ID=7438

You can set up a profile and use the standard-rule, "Is logged in" and set the page/paragraph to be hidding if the profile matches (in this case, if the user is logged in). It should basically do the same as you are trying to do.

Developer forum

Opposite permissions in Dynamicweb suddenly does not work

Replies