I thought I would move my pestering of you to your forum. :)
The RemoveProtection method is giving me a hard time now. When I remove all my members from the media item and then want to completely remove the protection it actually regenerates my old settings.
Yes you are right. The member that "sticks" is set on the parent node. If I set another member on the parent node that one is selected on this node as well.
Seems like it will show the inherited members if no members are selected on the node. I have made this new screencast of it. It might actually be on purpose from your side and that's fine, although not entirely logical (Or that might just be me!):
Media RemoveProtection bug?
Hi Richard,
I thought I would move my pestering of you to your forum. :)
The RemoveProtection method is giving me a hard time now. When I remove all my members from the media item and then want to completely remove the protection it actually regenerates my old settings.
Watch this screencast of my problem:
http://screencast.com/t/iWu7jqHydG
/Rune
Hi Rune,
No worries This functionality is still in development as you know so I'm happy I didn't release it yet, will look into this now.
Thanks,
Richard
Hi Rune,
I think a parent still has protected items. when you remove it from the child it gets the protected items from its parent. Can you check that please?
Thanks,
Richard
Hi Richard,
Yes you are right. The member that "sticks" is set on the parent node. If I set another member on the parent node that one is selected on this node as well.
Seems like it will show the inherited members if no members are selected on the node. I have made this new screencast of it. It might actually be on purpose from your side and that's fine, although not entirely logical (Or that might just be me!):
http://screencast.com/t/fnAhZ4LeQ5
/Rune
By the way. The access of the file is still correct in all cases. So it's just a matter of the API feeding me inherited data.
/Rune
Hi Rune,
Yes it's on purpose since Media Protect is using that method to determine access to the file ;-)
Cheers,
Richard
Cool. And I have found out it actually wirks quite fine for me. It just buggled me, when doing it.
Thanks
/Rune
is working on a reply...