Project:
| View Revisions: Issue #50160 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0050160: Write access should not be done when flushing dirty changes of bobs saved in admin mode | ||
| Revision | 2022-09-27 13:53 by caristu | ||
| Steps To Reproduce | 1) Create a new BaseOBObject in admin mode for an entity not writable for the current context user. Save it with OBDal.getInstance.save(bob) -> This works fine because we are inside an admin mode block. 2) Do an update in that BaseOBObject (this generates a dirty change) and execute OBDal.getInstance.flush() outside of the admin mode block. ERROR: The flush operation fails because the write access check is not passed. |
||
| Revision | 2022-09-09 12:41 by caristu | ||
| Steps To Reproduce | 1) Create a new BaseOBObject in admin mode for an entity not writable for the current context user. Save it with OBDal.getInstance.save(bob) -> This works fine because we are inside an admin mode block. 2) Execute OBDal.getInstance.flush() outside of the admin mode block. ERROR: The flush operation fails because the write access check is not passed. |
||
| Revision | 2022-09-08 09:33 by caristu | ||
| Steps To Reproduce | Scenario : I connect with HQ role I create a DOI I add an article I click on “book” button |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |