hi everyone!
trying to nail down the asset problem (format=downloadLink breaking pages)...
how are resource type formats supposed to work? are they all strictly internal-only, or should i be able to request them via browser as well?
when i create an asset FOO.png under /index and request /default/authoring/index/FOO.png?format=downloadLink, i get standard rendering of the page, not (as i believe i should) just the xhtml snippet from xslt/downloadLink.xsl. same if i try format=icon or similar.
btw, here's a suggestion (after wading through many a convoluted sitemap): can we please stop this nonsense of using pseudo "file names" like "xhtml.xml" as matcher patterns? these are totally obscure, give no clue what they are about and worst of all imply there's an actual file resource somewhere. how about using self-explanatory names? for instance, the resource module implements several formats, all named "something.xml". why not just match for "format-downloadLink", "format-webDAV", "format-whatever", where the part after the dash matches what's declared as format identifier in config/cocooc-xconf/module.xconf?
i'm also not sure whether we should maintain the configurable format uri in the xconf files. why not set up the convention that resource type formats are to be implemented as "format-FOO" and get rid of the indirection? or are there examples where the current approach is absolutely necessary?
regards, jörn -- Jörn Nettingsmeier Kurt is up in heaven now. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
