It is all rather worrying, Robert, and I can confirm that simply closing a stack no longer re-sets the protection.
Bug 546 (http://support.runrev.com/bugdatabase/show_bug.cgi?id=546) requests
the ability to re-set protection without closing the stack, but it only has
15 votes. If 'clone' is a different issue, perhaps someone should bugzilla it. However, since there is an increasing number of 'prohibited actions' in protected stacks including 'clone', I would humbly suggest that v2.61 could be considered 'broke' in this respect and in critical need of repair by addressing
546 urgently.
Yip... Hugh still has a serious bee in his bonnet on this one!
/H
Yes, cloning is a totally separate issue. I am entering this in Bugzilla so RR people can sort it out. As far as I can see, this is an undocumented change of behavior.
Not instating password protection upon close is yet another issue and I will Bugzilla it as well. It is not new to 2.6.1 but it did not check how far back it goes. If 546 was in place, we could have a workabout. As it is, there is nothing we can do AFAIK.
Robert _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
