Custom Fields Issues
Custom Fields Not Appearing in Admin UI
Custom Fields Not Appearing in Admin UI
If your custom fields aren’t showing up in the Payload CMS admin panel, check the following:
1. Check Collection Slug
Ensure the collection slug in your plugin configuration matches exactly with your Media collection slug.2. Plugin Order
Make sure thecloudinaryStorage plugin is registered before your collections are processed. Try moving it earlier in your plugins array:3. Field Name Conflicts
If you already have fields with the same names in your collection, there might be conflicts. Try using different field names.4. Restart Dev Server
Sometimes a full restart of your development server is needed after making plugin configuration changes:5. Debug Plugin Configuration
Add a temporary debug log to see what’s happening (fromREADME.md:447-459):Upload Issues
Upload Fails Silently
Upload Fails Silently
File Uploads to Wrong Folder
File Uploads to Wrong Folder
Verify Folder Configuration
Check your folder setting in the plugin config:Dynamic Folder Mode
If folders aren’t appearing as expected, check if Dynamic Folder Mode is enabled:Dynamic Folder Mode Issues
Files Not Appearing in Media Library UI
Files Not Appearing in Media Library UI
Newer Cloudinary accounts use Dynamic Folder Mode, which separates the folder structure in the UI from the public ID path.
Enable Support
Ensure Dynamic Folder Mode support is enabled (it’s on by default):How It Works
With Dynamic Folder Mode:- The plugin sets
asset_folderparameter during upload - Assets appear in correct folders in Cloudinary Media Library
- Public IDs remain unchanged
- URLs continue to work as expected
Check Account Type
Determine if your account uses Dynamic Folder Mode:- Upload a test file with the plugin
- Check the API response or document in Payload:
- Dynamic Mode: Has
asset_folderanddisplay_namefields - Fixed Mode: Has
folderfield
- Dynamic Mode: Has
README.md:391-432 for more details.Versioning Issues
Version History Not Being Stored
Version History Not Being Stored
Old Versions Not Being Invalidated
Old Versions Not Being Invalidated
Enable Auto-Invalidation
SetautoInvalidate to clear CDN cache for old versions:CDN invalidation may take a few minutes to propagate globally.
Frontend Integration Issues
Images Not Loading
Images Not Loading
Check Cloud Name
Verify your cloud name environment variable is set correctly:NEXT_PUBLIC_ to be accessible in the browser.Verify Public ID Format
Check the public ID doesn’t have extra slashes or invalid characters:Test URL Manually
Try accessing the Cloudinary URL directly in your browser:Transformations Not Applied
Transformations Not Applied
Performance Issues
Slow Upload Times
Slow Upload Times
Database Issues
Cloudinary Metadata Missing
Cloudinary Metadata Missing
Orphaned Records After Deletion
Orphaned Records After Deletion
The plugin automatically deletes files from Cloudinary when media documents are deleted from Payload.
Manual Cleanup
If you have orphaned records, clean them up manually:Getting Help
If you’re still experiencing issues:Report Issue
Contact the maintainer on X (Twitter): @syedmuzamilm
Next Steps
Configuration Reference
Complete plugin configuration options
Media Collection Structure
Understanding media document fields