Inserting new taxa fails if no permissions exist for user in fine grained permissions

[GoogleCodeExporter]

Use a user that has no biota permissions (distinct from read-only).

Trying to add taxa fails at commit time. The reason for this is that the 
security system needs the new taxon's parentage to work out if the user has 
permission, but the newly added taxon, even though it now has a valid biotaID, 
has not parentage because the containing transaction is still pending (the 
parentage for the taxon has not yet been calculated).

The fix is to remember if the update is actually on a new taxon and skip the 
security check if so.

Original issue reported on code.google.com by david.ba...@gmail.com on 15 Aug 2011 at 3:16

[GoogleCodeExporter]

This issue was closed by revision r965.

Original comment by david.ba...@synergi.com.au on 15 Aug 2011 at 3:16

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by david.ba...@gmail.com on 16 Aug 2011 at 11:16

• Added labels: Milestone-RC4
• Removed labels: Milestone-Release1.0