- Issue created by @adaddinsane
- π¬π§United Kingdom adaddinsane
OK, here's some additional data.
As mentioned, every image URL is coming out using the "res" sub-domain instead of "api-eu".
File URI: cloudinary://images/2023-03/background.png
becomes
Image URI: https://res.cloudinary.com/xxx/image/upload/s--krZz8bFO--/c_fill%2Ch_243%2Cw_360/v1/images/2023-03/background.png?itok=IOSup1_k
But the Cloudinary config looks like this:
Cloudinary\Configuration\Configuration Object ( [sections:protected] => Array ( [0] => cloud [1] => api [2] => url [3] => tag [4] => responsive_breakpoints [5] => auth_token [6] => logging ) [includeSensitive:protected] => 1 [cloud] => Cloudinary\Configuration\CloudConfig Object ( [cloudName] => xxx [apiKey] => 999999999999999 [apiSecret] => pppppppppppppppppppp [oauthToken] => [signatureAlgorithm:protected] => [explicitlySetKeys:protected] => Array ( [cloudName] => 1 [apiKey] => 1 [apiSecret] => 1 ) ) [api] => Cloudinary\Configuration\ApiConfig Object ( [uploadPrefix:protected] => https://api-eu.cloudinary.com [apiProxy] => [connectionTimeout] => [timeout:protected] => [uploadTimeout:protected] => [chunkSize:protected] => [callbackUrl] => [explicitlySetKeys:protected] => Array ( [uploadPrefix] => 1 ) ) ...the rest is empty.
Nothing I do forces it to use "api-eu" instead of "res" - I have changed everything I can find.
- πΊπ¦Ukraine nginex
Hi,
There are plenty of fixes in β¨ Create a Cloudinary media source instead of a separate media type Fixed
It will be a new major version and there is upgrade path from 2.xYou could try to switch to that fork and recheck or wait for new release
- πΊπ¦Ukraine nginex
Admin API is used for many features in the current implementation, I will check if it makes sense, if it's mandotary and will be back to you later with more information