After resolving , the protocol view is now searching in the defined or current plugin before searching into the CMS plugin.CMS-8304
Behavior of the view protocol, search the file into the following locations :
- current skin (*)
- plugin WEB (*)
- WEB-INF/param/view folder
- plugin defined in view:[pluginName]:// or if empty the current plugin
- plugin CMS
(*) If the plugin WEB exists and the WebViewSelector is selected in runtime.xml
I am not convinced about the relevance of this improvement for several reasons :
- The plugin is mandatory for skins (no ?)
- If you want to call an XSL file from a specific, just call it
- The defined or current plugin is red after the plugin WEB, then it always wins
- In a specific plugin, there is now no way to get the XSL file from WEB if the plugin exists, then CMS.
Note : The whole content types from plugin ODF are not displayable without a skin (then the plugin WEB) for now.
When the web plugin is there, all the files are searched into the skin then the web plugin in priority.
But, if we have an XSL defined into [pluginName] (for example odf) and web like common.xsl, the [pluginName] file is always ignored.