What should happen when changing the storage location of imagetypes?

[Elfangor93]

The storage location of an image in the filesystem is derived based on two settings in the config manager:

• General Settings/Common Settings/Filesystem --> root of the filesystem
• Image Processing/Static images/Root path --> path to imagetype folder

Now if you change one of these settings after you already uploaded some images or created some categories, JoomGallery will create a mess.

• The path to images uploaded before the change will not be created correcty and the images will not be shown anymore.
• New uploaded images will be threatened correctly.

As a result, changing one of these settings requires many operations to bring everything back into line especially for large galleries. Changing this settings and start this operations could cause many problems if some of the operations fail for some reason.

How can we tackle this problem?
How can we realize a GUI which leads an administrator correctly through this procedure?
Do you think its even a good idea placing this settings in the config manager?

[szepty-ziemi]

I think it will be rather source of issues. Most users use default settings and do not fiddle with them that much.
Other users like to experiment... having no experience or understanding.
There is little few that will use this feature and benefit from it.

[AlexanderSupp]

Google-Translate:
The basic questions in an image gallery are:
Does the software developer determine where the data is stored, or is it up to the user?

What are the advantages and disadvantages. And for whom?

Storage locations are specified:
The advantages for the software developer are a shorter development time and simpler solutions.

Storage locations can be selected:
The user can use existing or new directory structures. Originals, details, and thumbnails can be in different root paths. Due to a directory structure, categories can be automatically regenerated or restored. Each table entry of an image contains the full path of the original, the detail view and the thumbnail.

Due to the tense situation of the JG4 contributors, I would remove the storage location information from the configuration.

Original:
Die grundsätzlichen Fragen bei einer Bildergalerie sind:
Bestimmt der Softwareentwickler, wo die Daten gespeichert werden oder wird dies dem Benutzer überlassen?
Was sind die Vorteile und Nachteile. Und für wen?

Speicherorte werden vorgegeben:
Die Vorteile für den Softwareentwickler sind eine kürzere Entwicklungszeit und einfachere Lösungen.

Speicherorte können gewählt werden:
Der Benutzer kann bestehende oder neue Verzeichnis-Strukturen nutzen. Dabei können Originale, Details und Thumbnails in unterschiedlichen Root-Pfaden liegen. Aufgrund einer Verzeichnis-Struktur können Kategorien automatisch neu generiert oder wiederhergestellt werden. Jeder Tabelleneintrag eines Bildes enthält den vollständigen Pfad des Originals, der Detailansicht und des Thumbnails.

Aufgrund der angespannten Situation der Mitwirkenden der JG4 würde ich die Angaben nach den Speicherorten aus der Konfiguration entfernen.

[Elfangor93]

The main advantage of different storage locations is that you can store image files in cloud storages next to your webhosting. Cloud storages are much cheaper than webhosting storage since you pay only what you are using. They provide more speed, better backup functionality but much less services. This is especially suitable to store big amaounts of media files like photos and videos.
Source:
https://www.cloudpanel.io/blog/web-hosting-vs-cloud-hosting/

This is, next to tags and imagetypes one of the coolest features of JG4.