Update module pages affected by "removal of (old) Content API" (DOCU-1191)

[DOCU-1234] Update "Imaging module" page Created: 17/Nov/17  Updated: 24/Nov/17  Resolved: 24/Nov/17

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:
relation
is related to MGNLIMG-200 Remove uses of the Content API Closed
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
See also description of the parent ticket.
There may be also other little tiny things to update which have changed with the release of 5.5


Old comments on the imaging module:

Version 3.3.1 does not consider (see sourcecode) the properties storeGeneratedImages or validateFileExtension anymore.
(Marc Johnen)
And there may have been others



 Comments   
Comment by Richard Gange [ 22/Nov/17 ]

Version 3.3.1 does not consider (see sourcecode) the properties storeGeneratedImages or validateFileExtension anymore.
(Marc Johnen)
And there may have been others

  • It seems storeGeneratedImages is still there
  • validateFileExtension I don't find anywhere in the current docs.

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: DOCU-648

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.
To show only one maven dependency snippet seems fine here in the case of this module.

(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 DOCU-648, or at least try again whether it can be done now.
But I would not consider it as a high prio.
Personally I think this dynamic image creation with text overlays is not used very often anymore these days.
However ... since there is the ticket. Let's do it at some point.

Would you be in the mood doing it?
Just asking.

Besides: Thanks for the updates on this and on the other modules.

Generated at Mon Feb 12 01:16:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.