Thanks again Will. I have subscribed to the new issue in GitHub, and will look into addressing this via code in the meantime as you suggest.

Two questions:
[list=1][*]If the issue now described in GitHub is solved, do you think it is likely that the solution would be applicable to 1.10.4, or only 3.X?
[*] You suggested addressing this in the meantime via code in the category view. It is the product viewer pages that are giving me trouble, so should I be looking at things like the ProductPageViewModel and perhaps DotNetNuke.Entities.Users.UserController.Instance.GetCurrentUserInfo()?
[/list]

[quote=Adam Bernstein;208]If the issue now described in GitHub is solved, do you think it is likely that the solution would be applicable to 1.10.4, or only 3.X?[/quote]

Any new updates to the source code will only occur in the latest code base, which right now is version 3.0 and newer.

[quote=Adam Bernstein;208]You suggested addressing this in the meantime via code in the category view. It is the product viewer pages that are giving me trouble, so should I be looking at things like the ProductPageViewModel and perhaps CMS.Entities.Users.UserController.Instance.GetCurrentUserInfo()?[/quote]

Sorry... you should address this in whichever view has the issue. It's not uncommon to do role-checking in views for a various number of use cases. You'll find a simple example of this in the SO question below.

https://stackoverflow.com...cakes-checkout-views