Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.
Please keep in mind:
Yes, but from what I see here (on the forum) chevereto is a good script, but the lack of annex development is a shame
But hey, it could be a function to integrate in future versions, right? like many others that would be useful but good from what I've seen it's not the priority which is a shame for the script: /
And then like 80% of script users of this kind the skills (for my part) are more than limited, but hey it's like that .....
@SimplyCorbett
And then I am not an image host, but a photographer who uses the script for a community (what the script provides for the base, isn't it?) So to keep a certain quality limiting the download helps a lot, doesn't it?
then talk about DB to modify etc ...
talking to me in Chinese would come back to the same (like many) if people don't give more explanation
ex: how to do?
In any case thank you but I am not more advanced to date ...
ok specifically insofar as I don't know anything about it and I'm not a magician and you haven't understood my problem, what do I do? How? 'Or' What ? with what ? and I put what?So make a plugin that supports this or do what I suggested and ban any IP that downloads the image more then a few times by parsing your web server logs.
You can actually count how many times the image is downloaded globally that way too. So what you want is possible on the OS level.
Sorry for being stupid ... but I really didn't understand what you said!Perhaps you think that this is just a counter and a permission enforcement, it is not. At least if you really want it to work, because to limit if the download button shows or not is ridiculously trivial. However, it will be also very easy to overpass it. Is just like the "disable right click", that while it blocks the context menu, it doesn't block the underlying direct URL access because the files are served directly.
Chevereto doesn't serve the images neither enforces access restrictions on top it, the system was designed for mass public storage and for the web, which on its own adds limitations that avoid to easily implement restrictions (for example, if this were a mobile application it could block access to the resources at application level without the server footprint).
In any case, for V4 I want to implement an image server, which will allow us to add this kind of enforcement policies (and many other neat stuff) as the ongoing needs for the software also includes a tight control on who has access to the uploaded content.