What steps will reproduce the problem?
1. +bucket/create foo
2. Create a job in that bucket
3. (any random player) +myjobs
What is the expected output?
Players unassociated with job don't see it
What do you see instead?
The job # is in the listing of +myjobs for all players
Please use labels and text to provide additional information.
Setting the &ACCESS attribute resolves the problem. However, the default is
problematic.
Players still can't read the job. Listing permissions should be aligned with
reading permissions.
Original issue reported on code.google.com by widdis@gmail.com on 15 Mar 2012 at 6:57
Original issue reported on code.google.com by
widdis@gmail.com
on 15 Mar 2012 at 6:57