On automatic migration on new repositories, the property ametys:newrepository on ametys:versions node is never set to false because we never save the modification when setting it to false.
- discovered while testing
-
WORKSPACES-1325 Changing from getSites to getSite breaks the migration
-
- Closed
-
- Est référencé par
-
REPOSITORY-496 Automatic migration : remove newrepository
-
- Closed
-
- is duplicated by
-
WORKSPACES-1332 JCR.before scripts are initialized instead of migrated
-
- Closed
-
[REPOSITORY-493] Automatic migration: newrepository is never false
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Link |
New:
This issue Est référencé par |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Code review OK [ 10206 ] | New: Resolved [ 5 ] |
Link |
New:
This issue is duplicated by |
Status | Original: Available for review [ 10005 ] | New: Code review OK [ 10206 ] |
Assignee | Original: Raphaël Franchet [ raphael ] | New: Bérénice Maurel [ bmaurel ] |
Sprint | Original: 4.6 M3 [ 74 ] | New: 4.6 M2 [ 73 ] |
Link |
New:
This issue discovered while testing |
Assignee | Original: Bérénice Maurel [ bmaurel ] | New: Raphaël Franchet [ raphael ] |
Status | Original: Open [ 1 ] | New: Available for review [ 10005 ] |