Update module pages affected by "removal of (old) Content API"
(DOCU-1191)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Richard Gange |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Sprint: | Docu Sprint 36, Docu Sprint 37, Docu Sprint 38 | ||||||||
| Description |
|
Page to update: https://documentation.magnolia-cms.com/display/DOCS56/Imaging+module Old comments on the imaging module: Version 3.3.1 does not consider (see sourcecode) the properties storeGeneratedImages or validateFileExtension anymore. |
| Comments |
| Comment by Richard Gange [ 22/Nov/17 ] |
As far as I can tell nothing more was done other than the content api removal and module relocation. |
| Comment by Richard Gange [ 22/Nov/17 ] |
|
Possible follow-up ticket: |
| Comment by Christoph Meier [ 23/Nov/17 ] |
|
Please note, that 3 modules have been relocated. relocations ├── magnolia-imaging-fix-preload-awt-relocate ├── magnolia-imaging-relocate └── magnolia-imaging-support-relocate Since magnolia-imaging depends on magnolia-imaging-support, I would also add at least the new link to the magnolia-imaging-support-JAR-File. (However ... I am not completely sure for what magnolia-imaging-fix-preload-awt is needed ...) |
| Comment by Christoph Meier [ 24/Nov/17 ] |
|
Yes, rgange, we could do Would you be in the mood doing it? Besides: Thanks for the updates on this and on the other modules. |