On Mon, 21 May 2012, Stefan Hesselbach wrote: > Is this the expected behavior? I would expect the collection gets > restricted after the first webcoll run after the viewrestrcoll for it > is set up.
Currently, you have to run `webcoll -f' for a collection cache to be updated when you update its access control rights. That is, use webcoll with a force flag. Otherwise the change of access restrictions to a collection won't be noticed by webcoll. (As opposed to changing collection tree structure that would be well noticed, as you have also observed.) This is because webcoll does not look at the changes in access control tables when it decides whether to update the collection cache. As if it assumed a kind of best-case scenario, so to speak, since access control tables are used for many other actions, not only viewrestrcoll. I think we should rather go for the worst-case scenario approach here and update the collection cache in this case even if it may lead to unnecessary updates at times. Amended now. Here is the patch: <http://invenio-software.org/repo/invenio/commit/?h=maint-1.0&id=aae78753038a877c262c1c4d2b4e0e69eeb2dbb8> Thanks for reporting this problem. Best regards -- Tibor Simko
