adam/Piwigo
1
0 Fork 0
mirror of https://github.com/Piwigo/Piwigo.git synced 2026-10-30 21:52:00 +01:00
Code Issues 657 Packages Projects Releases Wiki Activity

Lack of Auto Synchronization #2182

New Issue
Open
opened 2026-10-05 01:08:54 +02:00 by adam · 2 comments
adam commented 2026-10-05 01:08:54 +02:00
Owner
Copy link
Copy source

I am running a production photo archive using Piwigo, where images are regularly uploaded over FTP in large batches. This is a common and efficient workflow for high volume environments, especially when uploads are automated or handled by external systems.

The core issue is that Piwigo still lacks a reliable and maintained mechanism for automatic synchronization of newly uploaded files. After uploading images via FTP, the gallery does not reflect changes unless a manual sync is triggered. For an active photo bank, this is not practical.

There are a few existing tools and plugins that attempt to address this, but they appear to be abandoned. Some have not seen updates in close to nine years, and they no longer align with current Piwigo versions or modern deployment practices. Relying on outdated or unmaintained code is not an option in a production setup.

What is missing is a simple and robust solution, for example:

  • A scheduled synchronization task that scans directories every 120 minutes for example
  • A native cron-based or background job solution
  • Or an officially supported plugin that handles this reliably

Auto synchronization after FTP uploads is not a niche feature. It is a baseline requirement for anyone managing large or frequently updated collections, and it is something most gallery or DAM systems handle out of the box.

I would like to understand:

  • Whether there are any plans to support automatic synchronization natively
  • If not, whether there is interest from the core team in maintaining an official solution
  • Or if there is a recommended, modern approach that is actively supported

At the moment, this limitation makes it difficult to justify Piwigo for serious or automated photo workflows, despite its strengths in other areas.

Thank you for considering this feedback.

I am running a production photo archive using Piwigo, where images are regularly uploaded over FTP in large batches. This is a common and efficient workflow for high volume environments, especially when uploads are automated or handled by external systems. The core issue is that Piwigo still lacks a reliable and maintained mechanism for automatic synchronization of newly uploaded files. After uploading images via FTP, the gallery does not reflect changes unless a manual sync is triggered. For an active photo bank, this is not practical. There are a few existing tools and plugins that attempt to address this, but they appear to be abandoned. Some have not seen updates in close to nine years, and they no longer align with current Piwigo versions or modern deployment practices. Relying on outdated or unmaintained code is not an option in a production setup. What is missing is a simple and robust solution, for example: - A scheduled synchronization task that scans directories every 120 minutes for example - A native cron-based or background job solution - Or an officially supported plugin that handles this reliably Auto synchronization after FTP uploads is not a niche feature. It is a baseline requirement for anyone managing large or frequently updated collections, and it is something most gallery or DAM systems handle out of the box. I would like to understand: - Whether there are any plans to support automatic synchronization natively - If not, whether there is interest from the core team in maintaining an official solution - Or if there is a recommended, modern approach that is actively supported At the moment, this limitation makes it difficult to justify Piwigo for serious or automated photo workflows, despite its strengths in other areas. Thank you for considering this feedback. <!-- github-sync-id:3827857494 -->
adam commented 2026-10-05 01:08:55 +02:00
Author
Owner
Copy link
Copy source

I fully support this request.
DéHème

I fully support this request. DéHème <!-- github-comment-id:3831076531 -->
adam commented 2026-10-05 01:08:56 +02:00
Author
Owner
Copy link
Copy source

I fully support this request. DéHème

It seriously has to get some love. I mean, running a Perl script with embedded raw credentials in 2026 is nuts, yet beautiful in some way, but it is probably time to give the function some love and find a more feasible way. Got nothing but love for Piwigo, but what the heck 🥹

> I fully support this request. DéHème It seriously has to get some love. I mean, running a Perl script with embedded raw credentials in 2026 is nuts, yet beautiful in some way, but it is probably time to give the function some love and find a more feasible way. Got nothing but love for Piwigo, but what the heck 🥹 <!-- github-comment-id:3858549633 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Piwigo#2182