[
http://jira.magnolia.info/browse/MAGNOLIA-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Bracher resolved MAGNOLIA-1198.
---------------------------------------
Resolution: Fixed
Implemented by:
- using cache
- regexp uri mapping
- removing the messages from javascript.js and putting them into a
messages.[iso].js page
- .resources are cached as well
In case you want to develop javascripts or change resources you must set the
property to true.
> admininterface: support magnolia.develop property properly
> ----------------------------------------------------------
>
> Key: MAGNOLIA-1198
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1198
> Project: Magnolia
> Issue Type: Improvement
> Affects Versions: 3.0 Final
> Reporter: Philipp Bracher
> Assignee: Philipp Bracher
> Fix For: 3.6
>
>
> the magnolia js page renders the messages, therefore they are not cachable.
> Since this file is huge this very stoopid. we need to separate:
> - messages_iso-code.js
> - other-files.js
> This should increase the admininterfaces speed a lot
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
