Hello again 🙂
You can create another Photos collection (in your folder) because that default collection named Photos is actually just the Media Library, and not a real collection on the WordPress side. It is simply a default to drop your files in.
Why don’t you name your folder “All Photos”?
I checked the Lightroom API just now and if I want to give the power to the user to rename the folder, the user will also be able to delete it. I find it a bit dangerous since if it is deleted, then the default is gone and impossible to get it back. Might trigger a lot of issues I am afraid :/
It’s not a problem at all, I’m still curious though: I can create other collections on the same hierarch-level as the “Photos” collection and I don’t see any difference between collection that I created in the “Photos” collection vs. collection created on the same hierarchy. So I assume everything is/should happen within the “Photos” collection/folder anyway.
If that’s the case and everything is happening in that folder, why do you show it at all instead of letting all the magic happen in that folder by default?
Cheers,
Oliver
I don’t see any difference between collection that I created in the “Photos” collection vs. collection created on the same hierarchy.
Are you sure you don’t see a difference? I mean, the photos will always go in the Media Library. But if you use an extension for something, let’s say the Basic Collection, then a Collection will be created for that collection you created by yourself. Nothing will be ever created for the default Photos.
If that’s the case and everything is happening in that folder, why do you show it at all instead of letting all the magic happen in that folder by default?
Sorry, what? :p Hahaha, I lost it! You need a default collection, normal users (not using any extensions or anything) need that. Then advanced user can ignore that default collection (which doesn’t do anything, except to be a drag and drop thing, you need one) and create collections and everything that user wants.
