Instead of using the element_url provided by pwg.images.getInfos, it would be better to have a download_url for several reasons:
if it is missing (or better, is empty), it would mean that the user has no download right
if provided the API user (eg mobile app) would use the right URL, such as action.php?... with or without pwg_token: download statistics would be more accurante
Instead of using the `element_url` provided by `pwg.images.getInfos`, it would be better to have a `download_url` for several reasons:
1. if it is missing (or better, is empty), it would mean that the user has no download right
2. if provided the API user (eg mobile app) would use the right URL, such as `action.php?...` with or without `pwg_token`: download statistics would be more accurante
<!-- github-sync-id:1710202292 -->
as privately requested by @EddyLB it would useful to add a way to tell Piwigo a photo has been download from application cache, meaning without making a new request to action.php. I suggest adding a is_download parameter to pwg.history.log
as privately requested by @EddyLB it would useful to add a way to tell Piwigo a photo has been download from application cache, meaning without making a new request to `action.php`. I suggest adding a `is_download` parameter to `pwg.history.log`
<!-- github-comment-id:1549114103 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Instead of using the
element_urlprovided bypwg.images.getInfos, it would be better to have adownload_urlfor several reasons:action.php?...with or withoutpwg_token: download statistics would be more accuranteas privately requested by @EddyLB it would useful to add a way to tell Piwigo a photo has been download from application cache, meaning without making a new request to
action.php. I suggest adding ais_downloadparameter topwg.history.log