View Issue Details

IDProjectCategoryView StatusLast Update
0003783Composrgalleriespublic2019-02-27 19:29
ReporterChris GrahamAssigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status non-assignedResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0003783: Import from filesystem
DescriptionAllow importing galleries from an on-disk directory structure, just like we currently support for the downloads system.
TagsNo tags attached.
Attach Tags
Time estimation (hours)4
Sponsorship open

Relationships

related to 0001381 non-assigned Allow mass import when adding a gallery 

Activities

Chris Graham

2019-02-27 19:29

administrator   ~0005929

Actually on discussing this (https://compo.sr/forum/topicview/browse/deploying/installer-fails-to.htm?post_id=5672&topic_id=1310&timestamp=1551294888&redirected=1#post_5672) I can see some system that does this dynamically would be better. People aren't going to want to import media libraries and then stop editing filesystem structure.

A better way to do it would be to implement some kind of scanner hook system. When you go to a gallery, it may be bound to a directory path based on a hook's determination. That would then rebuild that gallery based on disk contents. Any images/videos that no longer existed would be unvalidated. Any images/videos that previously existed would be re-validated. This way comments would persist. Depending on exactly how the hook was written, we might migrate old image/video entries to a new gallery, if we detect a file has moved.
We could ship a default hook with some inbuilt assumptions.

Some kind of proxying script may also be needed, if the bound directory is not web accessible.

Possibly we'd do this for galleries too, in addition, or instead of, the import process.

Issue History

Date Modified Username Field Change
2019-02-27 18:10 Chris Graham New Issue
2019-02-27 18:10 Chris Graham Relationship added related to 0001381
2019-02-27 19:29 Chris Graham Note Added: 0005929