Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In ACS 7.4 previews still work even with thumbnails and renditionService2 disabled #2

Open
igorbga opened this issue Sep 19, 2023 · 0 comments

Comments

@igorbga
Copy link

igorbga commented Sep 19, 2023

The RenditionService2 is enabled by the AND-joined values of `system.thumbnail.generate` and `renditionService2.enabled`. This means that the entire service will be disabled if an administrator sets `system.thumbnail.generate` to `false`, only expecting that thumbnail images are no longer generated, even if they would still want to support e.g. PDF renditions, video transcoding or other kinds of renditions to occurs which help to make content more accessible on different client software / system constellations.

This migth be something new in 7.4, not sure, but it seems that even if you set both parameters to false the previews are generated.

In fact I've have had to disable both because otherwise the thrid rendition of each document fails. The first rendition triggered by share creates a rendition node that does not use "rn2" aspect and it works ok. When you update the content the second rendition is generated but this time the rendition node is "converted" and the "rn2" aspect added. The third one, the one that finds an existing rendition which already has "rn2" aspect and you would expect to be the "easy" case is the one that fails. If you delete the rendition node then it starts again, first rendition without "rn2", second rendition with "rn2" related aspect and error again...

Disabling both flags makes everything work as expected, but of course you loose the thumbnails in the document list, not a big deal in our case.

Definitively there hasn't been much love put into this implementation. Sadly it seems that it being a new and community only functionality might probably have something to do with it. And as you already pointed in your document contributing, even if it is only by submitting bugs, is harder harder on every Alfresco owner change.

It's a pity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant