Pages: 1
Good evening, this may be a problem I've already addressed, but I haven't found a solution anywhere.
I've been using Piwigo Docker (piwigo/piwigo) for a few weeks as my family gallery, hoping to replace Synology Photos. I like it.
I recently extended my testing and uploaded some files to a new album via the iOS app, and I noticed that the file name in the Upload folder corresponds to the upload date, not the date it was taken.
This had never happened to me before, and all my photo names begin with the date it was taken.
I've tried numerous times and scoured the web because it's important to me that the file name matches the date it was taken.
Despite everything, I haven't been able to change this behavior, which is consistent with HEIC, JPEG, and PNG images, so it doesn't depend on the photo format in the gallery. In fact, the date it was taken appears correct in the image tab in Piwigo. I'm using iOS 16.7 on an iPhone 8 Plus.
No plugin intercepted the image to rename it. All attempts to configure environment variables via Piwigo plugins have failed.
Is there a way to configure Piwigo to save photos with filenames that match the date they were taken?
Thanks everyone for any help or suggestions.
Offline
Hi druid86,
By default, all files uploaded with the web UI or the iOS/Android apps to a Piwigo get a name starting with the date of the upload. I invite you to have a look at plugins renaming files. Among them, AutoFileRenamer may be the most appropriate.
Hope this helps.
Cheers
Offline
Dear cryopad,
thanks for the clarification, I wasn't sure if this was a programmed behavior or a configuration error.
I tried "AutoFileRenamer" and all the other plugins to rename the files, as well as to extend character compatibility to spaces, and every other plugin possible, without success. Furthermore, I have iOS and Android, which rename photos differently, and the plugin you recommended only supports one naming pattern.
Anyway, after days of testing and a reinstallation, I had to turn off Piwigo because there's no way it could import the large image library I already have.
I got every possible error, and I just let it go, until (after initial tests) I finally tried to import all my photos, and the import plugins started creating thousands of albums, naming them with the file names (both the native plugins and the community plugins that break the upload process into multiple parts). I had to stop, deeply discouraged, unable to invest any more time in software that, after over 24 years of development, still can't manage tens of thousands of photos.
I liked Piwigo, and it met all my and my family's needs, but the inability to import old albums and name new files by upload date made me give up. I'm disappointed, though.
In any case, thanks for the information.
Best regards,
Simone
Offline
Dear Simone,
Do you know that it exists an alternative solution for those who are using a self-hosted gallery? syncing files transferred by FTP.
In Admin / Photos / FTP + Synchronisation, you will find a minimal documentation explaining that you can transfer files organised inside folders to your Piwigo and then go to Admin / Tools and click on the Synchronise button.
May be you should have a look at the FTP import and synchronization of the documentation.
All the best,
Eddy
Offline
Dear cryopad,
thanks for the clarification.
I copied the files directly into the Galleries folder after removing all characters Piwigo doesn't allow, except for spaces. Then I used the Admin / Tools function and clicked the Synchronise button, and it was at this point that the thousands of albums appeared at the root level with the file names (various years, so clearly coming from files read in subfolders and brought to the root level).
However, I discovered this when I re-entered Admin / Tools, because during the scans I consistently received an Nginx error despite having overridden the PHP time limit of 300 seconds (Docker piwigo/piwigo 16.4 on Container Manager 'Project' on Synology).
In any case, it doesn't seem possible to handle the import of nearly 100,000 items in one go without creating a stable and consistent work queue.
In fact, the first attempts with the entire library resulted in crashes and eventually slowdowns, so much so that the Piwigo site became extremely slow to load, perhaps due to the sheer volume of data being imported.
I'd like to point out that none of the imports extended to files; I had only selected "folders" (the middle option) and had deselected all the metadata options. Basically, everything happens just by reading the folder tree. Hence my discouragement in continuing.
I'm not a Piwigo expert, but I certainly tried to follow best practices, so much so that for the initial tests (the first 8,000 files or so), everything ran smoothly, albeit slowly.
Perhaps it's not the effort that was lacking, but rather a few more options for managing such large directories.
Thanks anyway for the tips.
Kind regards,
Simone
Offline
Pages: 1