I think it would be really nice to create an option where the user can select a single folder (like /Photos) and the app only scans this folder and its subfolders.
I have tons and tons of images all over my nextcloud, but only in /Photos are my, well, photos. And it's kind of a tedious task to create always a .nomedia file in all other directories.
@jancborchardt ?
Yes, @Mikescops and I briefly talked about this at the Contributor Week as well. What we could go for:
Showing files from Photos
and a button: ( Change folder )
That way it’s an automatic setup process but can still be adjusted later.
I would say it doesn't cover my needs. I have multiple folders with pictures that I want to be shown. Android is using all available photos, no idea for other galleries. Could be nice to check what users expect before pushing such drastic changes :)
Also, just having a setting to include/exclude some folders is probably the easiest/most universal way to do? :woman_shrugging:
@skjnldsv the point of @jancborchardt during our discussion was to have the most easy and transparent way to have the folder setups. I agree include/exclude would be the prefered way (as it is done on the sync for desktop client) but Jan thought choosing a single folder and having a per default on the Photos folder is the easiest way.
Defaut is indeed always preferable, I'm not arguing this part.
But a default automated config needs to be relevant. I'm not sure this is relevant to use a default Pictures or Photos folder.
Even our Nextcloud client have the default autoupload set to the InstantUpload folder, so we would not be compliant to our android setup :)
Let's take root folder but provide an option asap to restrict it to a given folder
same issue here that i am getting things like icons and unrelated artwork pictures in the photo app.
i suggest maybe copying the music app option to specify the path to your picture collection, and only if left empty use the root?
same issue here that i am getting things like icons and unrelated artwork pictures in the photo app. i suggest maybe copying the music app option to specify the path to your picture collection, and only if left empty use the root?
Yes that would be great, or the other option mentioned above:
Let's take root folder but provide an option asap to restrict it to a given folder
does .noimage apply to a folder and all subfolders or just the folder itself?
does .noimage apply to a folder and all subfolders or just the folder itself?
folder and subfolders :)
ok, in that case it simply does not work for me ... latest stable release of nextcloud 18
@bendschs please file a separate issue then. Make sure to search for duplicates beforehand.
Can this be developed? the .noimage/.nomedia trick isn't working for any of my folders.
@kicker334 sure thing – are you interested in contributing? :)
@jancborchardt I honestly wouldn't know where to start, develop, or test this type of thing... :( I have to ask strangers on the internet for help.
I'd love to help out - I'm super new to this kind of thing but if I could get some starting tips I can definitely have a go!
For anyone willing to help, please feel free to do so :)
It requires the addition of a setting section here
https://github.com/nextcloud/photos/blob/108105a984586db72fcc027cbbfeb87e737a35d5/src/Photos.vue#L27-L41
https://nextcloud-vue-components.netlify.app/#/Components/App%20containers?id=appnavigationsettings
Then a proper selection using our filePicker https://nextcloud.github.io/nextcloud-dialogs/modules/_filepicker_.html to specify which folder to use.
After that there will be various places to implement this filter:
https://github.com/nextcloud/photos/blob/108105a984586db72fcc027cbbfeb87e737a35d5/src/services/FileList.js#L53
https://github.com/nextcloud/photos/blob/108105a984586db72fcc027cbbfeb87e737a35d5/src/services/AlbumContent.js#L37 (see the AlbumController file, you should be able to specify the path)
This is definitely a complex task, but we'll be glad to assis anyone diving into this the best we can!
This is a really important feature to me. Because otherwise the "Your Photos" view is completely broken for me since it displays all kind of images (like my 1 billion screenshots) that are not import and should not be shown there.
I totally agree with @ntimo. I'd love to have Nextcloud photos be my primary photo storage, but due to this bug it's essentially unusable.
I totally agree with @ntimo. I'd love to have Nextcloud photos be my primary photo storage, but due to this bug it's essentially unusable.
I concur; I fear that the developers aren't actually using the app to a sufficient extent to realize how poor the experience is in a number of ways. I am really trying to use Nextcloud Photos as my main photo workflow but having a lot of trouble.
Since the 'cloud photo' use-case is such a core feature of Nextcloud for casual users it really deserves a lot of attention and polish.
Right - just add one more voice to the chorus. Keeping root as default but adding possibility to select what folders/subfolders should be used seems the best way to go.
Hello. I looked through this a few times now, and I just can't figure out what is the solution to changing the Root photos folder for the Photos timeline? I am on the latest release 20. What needs to be done/configured to enable Photos timeline to be pointed to a custom photos folder?
@RebelCoderRU
This is an opened issue. This is not implemented
Any idea when this will be implemented at all? It's been almost a year now and in all honesty this isn't that big of a function that it would take so long to add something as simple as a (Customizable) list of scannable folders.
Without that, I have no use for the whole "Photos" app/functionality at all in NextCloud, simply because whatever I add gets buried within a whole bunch of random images..
If this really can't be done by the actual developers themselves, there is no shame but at least just tell us it isn't going to happen unless we build it ourselves.
Uninstalling the app until it actually works right, I suppose..
EDIT: And yes, if you really want to go for the quick, dirty and simple solution? Only scan the Photos folder. That's the whole reason it would be there right? For your photos.. It actually makes sense to only scan /Photos and its subdirectories, just count every subdirectory as an album. There is your quick and easy fix that makes this all work out nicely :)
@StarSmasher44 if you read all the way through this issue you would see that #515 is open. You could try deploying that patch to production. YMMV though.
What about have a configuration item with the directory to start from and if it's not in the path in scanCurrentFolder in AlbumsController then ignore the scan?
I'm posting this because even though a naive solution it seems that a lot of people would like to use Photos as a product with their NextCloud instance but have everything is blocking, which is a shame since most of the hard work is already done.
Suggestions done in other issues are surely better but also more complex (fine filtering) which seems not to get approved.
What about have a configuration item with the directory to start from and if it's not in the path in scanCurrentFolder in AlbumsController then ignore the scan?
This is not for the albums, this is for the Timeline, which uses a different endpoint
I'm not sure this feature is actually requested for the Albums section :thinking:
@skjnldsv then what's the indexing function for the Albums section? The idea would be the same, to filter out paths that are not in the configured one.
This is the dav endpoint. Nextcloud's files indexing core.
Please check the other comments in https://github.com/nextcloud/photos/pull/515 so you can fully grasp the issues and why this hasn't been fixed yet :)
Most helpful comment
Yes, @Mikescops and I briefly talked about this at the Contributor Week as well. What we could go for:
That way it’s an automatic setup process but can still be adjusted later.