🇫🇷France @sgostanyan

Thanks for your feedback. The new changes should add a proper way to check for the existence of files with both local and remote storage system.

Additionally, I have added the use of the generic thumbnail as fallback and added a message to the logs.

sgostanyan → made their first commit to this issue’s fork.

Thanks for reporting this. A new release has been published. Please update to 6.1.5

Thanks for reporting this. I guess you're using remote file storage.
Could you please try attached patch which properly handles temporary path.

Thanks for reporting that bug.

Could you please test this patch? It should fix the issue

Done in 6.1.3

Merged thanks

Got the same issue with Claro (10.3.9). Patch #2 🐛 Paragraph title overflow hidden on form display RTBC fixed the issue.

Patch added to 6.1.2
Thanks

Merged, thanks

sgostanyan → made their first commit to this issue’s fork.

Wording

The error you are encountering, attempt to perform an operation not allowed by the security policy 'PDF' @ error/constitute.c/IsCoderAuthorized/413, is not related to the module itself but rather to the ImageMagick security policies configured on your server.

ImageMagick has a configuration file, typically called policy.xml, that defines rules for which operations are permitted or denied. In your case, the server's ImageMagick policy is restricting access to PDF files, which is why the module is unable to read or process the PDF.

To resolve this, your server administrator will need to modify the policy.xml file to allow the processing of PDFs. Specifically, they need to adjust the following entry:

<policy domain="coder" rights="read|write" pattern="PDF"/>

If the rights are set to none, PDF operations will be blocked. Updating the rights to read|write should allow the module to work as expected.

Please note that the location and content of the policy.xml file may vary depending on the version of ImageMagick installed. Typically, it can be found in directories such as /etc/ImageMagick/ or /etc/ImageMagick-7/ depending on the version.

Thanks lifelifeone for your patch. It could be better to add a default config value while installing the module and also set the new checkbox at the bottom of the form :)

Purging all PdfEntites from config page should solve your issue

sgostanyan → created an issue.

Thanks for your feedback.

The new stable release of 6.1 has been made in order to prepare the full Drupal 11 compatibility. All futur features and fixes are planned to be developped under PHP 8.3, that's why backward compatibility of PHP will not be guaranteed. You can still use version 6.0.x

Nevertheless it has been decided to rollback compatibility to >=8.1 for 6.1.x for now. We probably will support PHP >=8.1 untill Drupal 10 EOL. Please see 6.1.1

sgostanyan → changed the visibility of the branch 3465240-make-it-possible to hidden.

sgostanyan → created an issue.

sgostanyan → created an issue.

sgostanyan → created an issue.

sgostanyan → created an issue.

sgostanyan → created an issue.

sgostanyan → created an issue.

Thanks for reporting that issue.

Could you please try 6.1.0-rc1 release if it fixes your issue.

Remove deprecated instruction

Merged in release 5.6

Thanks.

Hi,

This issue has been fixed : https://www.drupal.org/project/media_pdf_thumbnail/issues/3292862 🐛 Huge Temporary files Magick Fixed

Updating to version 6.0 should fix the problem.

It's been merged into 6.0.0.

Thanks

Could you confirm that the attached patch is working.
Instead of using filesystem to get the realpath, it uses the stream wrapper. In the case of the streamwrapper is unable to give a realpath, the file uri is used to instanciate the Pdf object.

Merged in 6.0.0-rc3

Thanks

Merged in 6.0.0-rc3

Thanks

The module requires at least spatie/pdf-to-image v1.4.0 for 5.x and v2.1.0 for 6.x. So no needs to update.

Thanks :)

Change summary

Could you please update to version 6 and refer to the documentation →

If you still encounter the same problem, feel free to reopen the issue.

I'm closing that issue because it doesn't seem to be a bug but just a configuration ununderstanding.
Please update to version 6 and refer to the documentation →

Image format selection has been introduced in version 6 Usage in Media view mode →

Thanks for your report

Could you please tell where you find that setLayerMethod has been removed ? It seems to still exists, maybe I have missed something.

Thanks

Many thanks for you report !

All points should have been fixed in the rc2 release.

Add image destination hook alter

Add settings doc

Yes pdf-to-image goes into "vendor" ;)

The upgrade process is good but the updb has to be run after enabling the module.

Just for being sure, when you say "Changed all displays", you mean Media entity view modes, right ? So I understand you are rendering thumbnail field throught the whole Media entity render ? I'm asking this because some people confuse entity render et single field render.
For example in the admin media list page /admin/content/media which is a page built with Views (field render), settings made in Media view modes won't work.

Could you please have a look on this, just in case ?

spatie/pdf-to-image should be installed with composer

Could you give details about how you configured settings (all steps) ?

Also what is your version of imagick, php and drupal core ?

The fact that there is no error probably means the field is not handled by the module (config issue or way of use)

Thanks for proposing that feature.

The generation in cron/queue has been added in version 6.x but in a different way. The formatter itself get that option, the Media "Queue thumbnail downloads" is not used for two reasons.
The first one is because we decided to let users to use the queueing system separately for each formatter in each view mode, for a finnest configuration.
The second one is because some people use that module for other entities than Media. It works for any fields (usage of any image field with any file field) in any entity, so we want that users have also the opportunity to take advantage of that feature.

As version 6.x is still in beta, that patch will be usefull for those who want cron/queue feature for now. But it will not be included in 5.x release for avoiding confusion when upgrading to version 6.

King regards

sgostanyan → created an issue.