In the actual version of Piwigo, the relation between image/album, album/sub-album, group/user are not available in the addition, movement and deletions activities.
It could be useful for creating activity log's pages.
I suggest add object's id in details of these activities.
In the actual version of Piwigo, the relation between image/album, album/sub-album, group/user are not available in the addition, movement and deletions activities.
It could be useful for creating activity log's pages.
I suggest add object's id in details of these activities.
<!-- github-sync-id:678438062 -->
Can you give an example of relation you would expect. For example if I delete a photo, what details would you like to have?
Hi @Zacharieg
Can you give an example of relation you would expect. For example if I delete a photo, what details would you like to have?
<!-- github-comment-id:700140966 -->
If my memories are good, there isn't a specific column in activity table for linked objects, but we can add it in details, it is already done on some activities but not enough to create a cool log page (like when you want to relate to the adding of a photo on an album log page, but you don't have the information of the album where it was created)
For this exemple (delete a photo), we could add a new information on the delete activity log (in the details) : the album id, or a new activity log of modification on the album, with information of the photo.
Maybe a new table structure could be better on activities, even if this is complex cause of the data collected since the creation of this table
If my memories are good, there isn't a specific column in activity table for linked objects, but we can add it in details, it is already done on some activities but not enough to create a cool log page (like when you want to relate to the adding of a photo on an album log page, but you don't have the information of the album where it was created)
For this exemple (delete a photo), we could add a new information on the delete activity log (in the details) : the album id, or a new activity log of modification on the album, with information of the photo.
Maybe a new table structure could be better on activities, even if this is complex cause of the data collected since the creation of this table
<!-- github-comment-id:700306858 -->
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.
In the actual version of Piwigo, the relation between image/album, album/sub-album, group/user are not available in the addition, movement and deletions activities.
It could be useful for creating activity log's pages.
I suggest add object's id in details of these activities.
Hi @Zacharieg
Can you give an example of relation you would expect. For example if I delete a photo, what details would you like to have?
If my memories are good, there isn't a specific column in activity table for linked objects, but we can add it in details, it is already done on some activities but not enough to create a cool log page (like when you want to relate to the adding of a photo on an album log page, but you don't have the information of the album where it was created)
For this exemple (delete a photo), we could add a new information on the delete activity log (in the details) : the album id, or a new activity log of modification on the album, with information of the photo.
Maybe a new table structure could be better on activities, even if this is complex cause of the data collected since the creation of this table