targren / piwigo Goto Github PK

It's not necessary. The remote sync jar works poorly at best, and I don't use any of the listed desktop apps, most of which are for devices I don't have.

Look into Digikam.

Currently, Parent project keeps all non-physical album images in subdirectories of "./uploads" perpetually.

Instead, store those subdirectories in a separate image storage directory ("./images", e.g) once added to an album.

Idea: "Uploads" directory gets its own "dynamic" album to find and access images that are yet unprocessed.
Less desirable option: Database flag for uploaded/synchronized files that are not yet processed.

Probably requires #1

• Instead of trying to import files as-is and failing/refusing to import files with "illegal" characters, store the original filename and rename the physical file.

• Import subdirectory names as sub-albums, given the same treatment.

This largely removes the need for "physical albums" and means the loss of "Directory First" storage, which doesn't fit my use case.

Potential security implication: Confirm if malicious scripts/files can be uploaded, guessed, and executed from uploads.

Use case: Allow ease of backup, storing large amounts of data separately from the web application (larger drive, e.g.) without having to resort to symlinks.

Ideally, plugins should continue to function with any local modifications.

Most attention must be paid to plugin tasks that access image files or albums.

i.e. "Tags," "Linked Albums", "Album Thumbnail"

Good fix: Auto-expanding fields as needed
Lazy fix: Bigger fields

Attempt to update the API to accommodate changes to the back end functionality without breaking it. Best case scenario, PiwigoNG app and API clients continue to work with changes.

See #1 #2 #4

At a minimum, a search for images that lack any tags at all.

Main project currently forces resize to thumbnail (120x120, cropped), Square (144x144) and Medium sizes. Investigate how many are necessary for functionality (Thumbnail almost certainly) and attempt to reduce duplication/storage needs

Mistyping database auth info isn't checked, and leads to a 500 error rather than failing gracefully and displaying the access denied message, because it attempts to set charset on an invalid DB.

Current "Inherit Permissions" setting depends on all albums being sub albums or setting permissions on every new album, and requires editing backend config file.

Try to make this install-wide, available in the admin configuration ("Permissions" section already exists), and specify whether or not it can be overridden for specific albums.