Cloudinary Stream Wrapper caches items in the database (Database Storage) but never actually checks if an item is inside the storage

Re-published, not spam.

Since there has not been a reply here recently on this issue. Just wanted to let you know this issue is still relevant for the new 3.x branch. The patch above is still working without any modifications.

There are multiple problems related to this issue:

* The meta data is never loaded from storage (which is addressed by the previous patch)
* The meta data is never fetched if the asset's public_id contains a file extension
* Because the meta data is always re-fetched a fatal error is thrown if the original file is not found via the Cloudinary admin api: Uncaught InvalidArgumentException: A path was passed when a fully qualified domain was expected
* Pages containing multiple cloudinary assets (e.g. the file admin view, entities with a lot of cloudinary media entities, etc) get a big performance impact because the cloudinary_stream_wrapper module calls the cloudinary api for every asset that is displayed.

Attached is a patch that addresses these issues:

• The patch introduced earlier
• Keep the file extension in the public_id
• Fall back to the homepage URL if the asset cannot be fetch from cloudinary when generating an external URL

Because ✨ Avoid overloading admin API Active addresses similar issues and covers additional areas where cloudinary data can be loaded from the database / cache instead of the API I have incorporated the changes introduced in the initial patch in ✨ Avoid overloading admin API Active .