Item9847: Topics don't inherit access control settings from template topics when saved with NatEdit

Updated with new info concerning NatEditPlugin

Expected behaviour

Access controls for a template in META data should be passed on to the topics created from them. For example a template with %META:PREFERENCE{name="ALLOWTOPICVIEW" title="ALLOWTOPICVIEW" type="Set" value="Main.SomeGroup"}% set should result in a topic with the same access controls in the meta data. This works fine with the standard editor. Using NatEdit it doesn't happen.

Test case

In an environment using NatSkin and NatEditPlugin I set up a TestGroup and a TestTemplate with nothing but %META:PREFERENCE{name="ALLOWTOPICVIEW" title="ALLOWTOPICVIEW" type="Set" value="Main.TestGroup"}% in it. A topic created using TestTemplate has no access controls set in the meta data. This is probably due to NatEdit's own permissions feature not correctly loading the meta data or wiping them clean.

It is of course still possible to put the following into the template text:

%ME%NOP%TA:PREFERENCE{name="ALLOWTOPICVIEW" title="ALLOWTOPICVIEW" type="Set" value="Main.TestGroup"}%

This will then expand into the correct setting upon topic creation. However it exposes the access setting during the first ordinary editing.

-- HolstenerLiesel - 19 Oct 2010

I have tried to reproduce this and when I test I can create a topic based on a template with ALLOWTOPICVIEW in the template meta.

As long as the user creating the new topic has read access to the template the new topic is created WITH the access setting.

And also, I checked that if the topic template is not readable by this user, he is refused to create a copy of it which is important for security.

-- KennethLavrsen - 19 Oct 2010

This appears to have been caused by using NatEditPlugin to save the new topic. Updated the report accordingly (updates in italics).

-- HolstenerLiesel - 19 Oct 2010

Seems to be a duplication of Item9766.

Please check latest release.

-- MichaelDaum - 22 Dec 2010