Images best practise

ThorstenvBW

gabriel Cover images you can address, by using a separate files attribute.

That is an option but somewhat awkward ...
in the flow of things the broker just wants to upload a bunch of images and be done with it

ThorstenvBW

gabriel It is primarily designed for internally accessed business apps, less for hosting large image galleries for public consumption.

Got it but my system is two fold. Rei3 serves as Business App. But the result of this "business" or better the created content therein has to become public ie. own website but also Internet listings / yellowpages / speciality sites.
Therefor in my cas i need the uploaded images in a public space.
best would be just to serve out of the /data/ directory, or, for security, keep a copy of the /data/images dir somewhere acessible ... seems much easier than do import and export steps ... but okay

gabriel

ThorstenvBW Got it but my system is two fold. Rei3 serves as Business App. But the result of this "business" or better the created content therein has to become public ie. own website but also Internet listings / yellowpages / speciality sites.
Therefor in my cas i need the uploaded images in a public space.
best would be just to serve out of the /data/ directory, or, for security, keep a copy of the /data/images dir somewhere acessible ... seems much easier than do import and export steps ... but okay

For this case, it´s probably best to use 2 systems: One internally (like r3) and another externally. r3 is ill-equipped to handle the later. From what you describe, you are already doing/planning this.

ThorstenvBW

gabriel Sorry, this would require a major rework of the file backend. Nothing that can be done without a major internal project and a corresponding priority.

i gather the framework already carries some meta data (in JSON)? like dates, versions, filenames (origina).
So if we could carry one more variable (bool) for "primary" ?
In the gui it woild just be a tiny checkbox in the existing frame
problem is to keep track of the "primary's" since only one of the images may carry the true value ... thats a thing i guess.
Just braining away sorry (-:

gabriel

ThorstenvBW i gather the framework already carries some meta data (in JSON)? like dates, versions, filenames (origina).
So if we could carry one more variable (bool) for "primary" ?

Tools like r3 are complicated beasts. All this abstraction, necessary to make them low/no code tools in the first place, means that changes like this are complex and have many consequences. We do regularly add new features for organizations to meet niche requirements - but these changes take days, so it´s not always worth it to spend for the effort.

ThorstenvBW

gabriel Please have a look at how r3 manages files by creating your app and looking at the file data structures that you get when you run GET requests. There is some meta data available, that you can use for sorting - like the file name or change dates.

not shure what you mean. Any docu on this ?
i see the data/download/ url with variables yes ... and ik know there is sorting on dates and filenames ... but not how to access that in detail ...
any hint ?
Thanks

gabriel

ThorstenvBW not shure what you mean. Any docu on this ?
i see the data/download/ url with variables yes ... and ik know there is sorting on dates and filenames ... but not how to access that in detail ...
any hint ?

What I mean is what I described in my posts above. The download handler data/download is just for downloading files. To deal with file meta data, you need to have an API defined in your app that includes a files attribute. Once you have this API, you can then execute GET requests and see the data structure and what information is included.

« Previous Page