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 | ||
| Description | When saving a new BaseOBObject or flushing changes done in BaseOBObjecs, a check for a write access is done in the OBInterceptor. This causes that BaseOBObjects created correcly in admin mode, are not finally persisted in the database because the OBInterceptor may perform the write checks on dirty changes not in admin mode. That check should be skipped BaseOBObjects saved in admin mode. |
||
| Revision | 2022-09-09 12:41 by caristu | ||
| Description | When saving new a new BaseOBObject or flushing changes done in BaseOBbjecs, a check for a write access is done in the OBInterceptor. This causes that BaseOBObjects created correcly in admin mode, are not finally persisted in the database because the OBInterceptor perform the write checks not in admin mode. That check should be skipped BaseOBObjects created or updated in admin mode. |
||
| Revision | 2022-09-05 15:55 by XABIER_AGUADO | ||
| Description | Roles without access to Data Import Entries and EDL Request cause an inifite loading screen to show up after trying to book a DOI. Only happens in TEST. Seems related to Push API Infrastructure |
||
| Revision | 2022-09-05 15:55 by XABIER_AGUADO | ||
| Description | Roles without access to Data Import Entries and EDL Request cause an inifite loading screen to show up after trying to book a DOI. Seems related to Push API Infrastructure |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |