🇩🇪Germany @markaspot

Anybody → credited markaspot → .

Thank you so much; your offer is highly appreciated. I seem to be a co-maintainer and currently see no option to add you. Therefore, I'll assign this to colan.

Thank you for looking into this. I suspect the module's description might be based on version 7.x, prior to merging it with a similar module resulting in the 3.x branch. However, I’m not entirely certain about this. I'm wondering if the api-key parameter, which could have been relevant in the D7 version is still relevant. Anyway I am open to a configurable option, but I think this would need a new maintainership, as my time constraints prevent me from keeping this module alive. Sure it would be easy to edit the module description, if it's just a typo.

Hello, although the PHP namespace has remained as lsolesen\pel, I've encountered a "Class not found" error with lsolesen\pel\PelJpeg. I've tried deleting the vendor directory and composer.lock file without success.

Error: Class "lsolesen\pel\PelJpeg" not found in Drupal\file_mdm_exif\Plugin\FileMetadata\Exif->getFile() (line 112 of modules/contrib/file_mdm/file_mdm_exif/src/Plugin/FileMetadata/Exif.php).

I have also attempted to clear Composer's cache and regenerate autoload files plus drush cr, but this has not resolved the issue. Any guidance would be greatly appreciated.

I can confirm that this fix worked for me as well. I encountered a similar issue while using S3FS to retrieve a remote image via code and the system_retrieve_file function, and then storing it in a subdirectory. However, I was unable to reproduce the bug when using the Drupal UI in Drupal 10.

Could you please test the latest dev-commit again? I was able to reproduce the deprecation warning you mentioned without the null coalescing operator, but adding it fixed the issue for me using PHP 8.1.15. If you could confirm that the solution works for you, I would be happy to create a new release as soon as possible.

This change breaks my authentication. Sorry for making this change without thorough testing. I will reopen this issue with an updated status and create a new release that rolls back the change. I am sorry for any inconvenience this may have caused.

Would you be willing to use the 3.0.2 release and possibly assist with testing it? It seems like this module could use additional support.

Thank you, I added a new release.

Actually i can't really reproduce this. I tried to fix this warning with 202b36597. However can you try adding a null coalescing operator instead?

if (strstr($route_name ?? '', 'entity.api_key')) {
    return FALSE;
}