[MAGNOLIA-1198] admininterface: support magnolia.develop property properly Created: 10/Nov/06 Updated: 23/Jan/13 Resolved: 19/Jun/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.0 Final |
| Fix Version/s: | 3.6 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
the magnolia js page renders the messages, therefore they are not cachable. Since this file is huge this very stoopid. we need to separate:
This should increase the admininterfaces speed a lot |
| Comments |
| Comment by Magnolia International [ 22/Nov/07 ] |
|
Will check this for RC2 - if no change required, will reset "fix version" to RC1. |
| Comment by Philipp Bracher [ 19/Jun/08 ] |
|
Implemented by:
In case you want to develop javascripts or change resources you must set the property to true. |