extensive usage of mix:versionable slows down the system
(MAGNOLIA-2086)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.6 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: |
| Description |
|
none must have mix:versionable but mix:referencable instead |
| Comments |
| Comment by Magnolia International [ 11/Jul/08 ] |
|
just updated a fresh 3.0.5 instance without touching the nodetype def files at all and got no warning or blocking condition |
| Comment by Magnolia International [ 14/Jul/08 ] |
|
the issue was that the condition was only added when updating from 3.5, not as an install task (which is the case when updating from 3.0 because core was not a module at the time) |