Michiel Meeuwissen wrote:
We are still running 1.7.0 because MMBase 1.7.0 and 1.7.1 are too incompatible in my experience for an easy transition. This bug is fixed in 1.7.1?NO_CHECK should not mean that authorization is disabled, but that it is not checked already, and that it should be checked afterwards, node-by-node.
There was indeed a issue that this node-by-node checking did not work, well, which was fixed a few weeks ago. So, I suppose this message can be considered a duplicate of that bug.
Then I probably have a new bug for 1.7.1 if the node-by-node checking is enabled: what if the original query is limited (in our case we limit the number of news items to 3 on the homepage). If any of the first 3 news items resulting from the query are not readable for the user the result will not be 3, even if there are more than 3 news items which he is allowed to see. (Not tested though)
Why is there a context limit anyway? Is it to avoid the max entries in an "IN" statement in the database?
Michiel
-- Met vriendelijke groet, Arjan Lamers
-----------------------------------------------------------------
First8 BV Notice: The only person getting his work done
Groenestraat 294 by Friday was Robinson Crusoe
6531 JC Nijmegen [EMAIL PROTECTED]
