Ticket #8312 (closed Feature Request: fixed)
Allow ResourceRegistries to Reference External Resources
| Reported by: | dunlapm | Owned by: | dunlapm |
|---|---|---|---|
| Priority: | major | Milestone: | 3.3 |
| Component: | Infrastructure | Keywords: | |
| Cc: | fschulze, interra, wald |
Description (last modified by dunlapm) (diff)
Splitting ticket #5521 to have Conditional Comments and External Resource be separate tasks with separate branches that can be handled independently.
Previous proposal called for adding a new render type of 'external' which leaves too much room for breaking the ZMI with the current templates, and errors with the tool attempting to cache and/or merge a resource it doesn't own. Instead I propose the following:
- Intelligent handling of resources starting with "http://" or "https://"
- Automatic disabling of merging, caching and compression
- Disallow inline rendering (link, import, etc still allowed)
Attachments
Change History
comment:3 Changed 4 years ago by dunlapm
- Status changed from new to assigned
- Description modified (diff)
Changed 4 years ago by dunlapm
-
attachment
external-registires.patch
added
Proposed patch for registries
Note: See
TracTickets for help on using
tickets.
