[MGNLSTK-1438] ImagingSupport should be decoupled from JCR Created: 15/Feb/13 Updated: 02/Jul/18 Resolved: 02/Jul/18 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
Its a problem because Assets may or may not have a JCR backing (provider). |
| Comments |
| Comment by Magnolia International [ 04/Feb/14 ] |
|
Today, that's actually up to STK since ImagingSupport is in STK. Then again, the reason ImagingSupport exists is because the imaging module itself doesn't provide means to generate links to the images it generates. This conundrum could perhaps be solved by improving the Link API. In the meantime, I'll suggest a couple of improvements in the linked wiki page which could help. |
| Comment by Magnolia International [ 13/Mar/14 ] |
|
To reiterate, it actually is decoupled - and perhaps what's missing is documentation about that. |
| Comment by Jan Haderka [ 02/Jul/18 ] |
|
STK have been deprecated in September 2017. As part of this project nearing end-of-life, we are not planning to fix any of the existing issues except for the critical security issues. For more details, please consult documentation. |