New User - storage needed and Magento plugin not working as expected?

Cy80rg
Cy80rg Member Posts: 2 ✭
edited September 19 in Digital Asset Management

Hi guys,

We have 3 servers - Dev, Stage and Live.

To test Cloudinary, we're installing and configing it on Dev, then to Stage, then finally to Live…

As our entire catlogue has c20Gb of Media, do I actually need to sync that 20Gb x3 servers into our Cloudinary account?

Secondly, just installed the Cloudinary extension for Magento 2.4…

Have set the credentials, mapped the Media dir, and just enabled both Sharding and Auto Upload Mapping.

Based on the docs saying "

Enable Auto Upload Mapping

 to automatically upload existing media assets to Cloudinary when they are first requested by a user.
"

… had rather expected to see the Cloudinary DAMS assets fill up as I surged around our site (on dev)… however, no sign of this happening?

Lastly, to see if the plugins doing anything at all, I set the Global Custom Transformation to r_60,W_200 - expecting to see an image preview… again, did nothing, no preview…

What am I missing here?

NB - so far I've only installed the extension and given it our (free) account creds…

Tagged:

Answers

  • Cy80rg
    Cy80rg Member Posts: 2 ✭

    NB - we also have various other caches configd on Magento - Varnish etc - do we need to disable or alter any of those?

  • DannyFromCloudinary
    DannyFromCloudinary Member, Cloudinary Staff Posts: 139

    Hi @Cy80rg. Thanks for getting in touch.

    There's nothing on our side preventing multiple Magento instances from connecting to a cloud, so you shouldn't experience any issue connecting your dev, staging, and production environments to the same cloud. It should be possible to use the same catalogue of assets within a single cloud so long as those assets are all named identically across your three environments. Assets are synced automatically once they're accessed, so if the naming is the same, you won't experience duplicate uploads of the same image.

    Regarding the auto-upload mapping, the behaviour you describe is what we would expect to see too. We sync assets on-the-fly as they are requested, rather than doing a bulk upload as soon as your Cloudinary account is connected to your Magento account. If this isn't the case, could you please raise a support ticket with your cloud name and a link to your public-facing Magento environments so we can take a look further. From the sounds of this, and the fact that your global transformation isn't being applied, it sounds like Cloudinary hasn't properly connected to your Magento instance.

    Looking forward to hearing back from you.

    Kind regards,
    -Danny

  • albert23
    albert23 Member Posts: 1 ✭
    edited September 28

    t sounds like a couple of things could be happening here:

    1. Media Sync: No, you don't need to sync the full 20GB across all 3 servers. Cloudinary’s auto-upload mapping should handle media on request, so it doesn't need to be manually uploaded to each server.
    2. Auto Upload Not Working: If assets aren't appearing in Cloudinary after browsing your site, check your auto-upload mapping settings and ensure the Media Library is correctly mapped. Also, confirm that write permissions are set correctly.
    3. Custom Transformations Not Showing: Ensure you've cleared Magento's cache and Cloudinary’s cache. Sometimes transformations won't reflect unless the cache is refreshed.

    These steps should help diagnose the issue.

Categories