Author have to be managed.
auth_id is mandatory to avoid all difference from time to time.
Access as a category or a tag access has to be implemented.
A link between member and Author has to be defined.
Maybe later a role has to be created as vimages explained.
**Reported by VDigital on 26 Dec 2006 10:27**
Author have to be managed.
auth_id is mandatory to avoid all difference from time to time.
Access as a category or a tag access has to be implemented.
A link between member and Author has to be defined.
Maybe later a role has to be created as vimages explained.
Topic related is http://forum.phpwebgallery.net/viewtopic.php?id=5693
[Piwigo Bugtracker #607](http://piwigo.org/bugs/view.php?id=607)
<!-- github-sync-id:97225205 -->
Acked (without h), just to promote it.
I don't know if we have time enough to do it in 1.7
**Comment posted by VDigital on 31 Jan 2007 07:57**
Acked (without h), just to promote it.
I don't know if we have time enough to do it in 1.7
<!-- github-comment-id:124889174 -->
> I don't know if we have time enough to do it in 1.7
No, we don't, but you're right to promote this feature request. We have to make it right after branch 1.7 fork (on trunk, of course).
**Comment posted by plg on 2 Feb 2007 16:16**
> I don't know if we have time enough to do it in 1.7
No, we don't, but you're right to promote this feature request. We have to make it right after branch 1.7 fork (on trunk, of course).
<!-- github-comment-id:124889218 -->
This feature request is a bit confused and mixes several ideas:
converting piwigo_images.author from a textfield into a list of values => we implemented it for search in Piwigo 2.6, see 0511ed2236 => now we should go further and implement it "the clean way", with a piwigo_authors table, numeric id and so on. See #486
browsing photos by author => once step 1 is done, this could be implemented with a plugin
having a relation between users and authors => this was implemented years ago with piwigo_images.added_by. We know which user has added which photo.
This feature request is a bit confused and mixes several ideas:
1) converting piwigo_images.author from a textfield into a list of values => we implemented it for search in Piwigo 2.6, see 0511ed2236b1fab9bc9c23b6c3bbee82ee4efdb5 => now we should go further and implement it "the clean way", with a piwigo_authors table, numeric id and so on. See #486
2) browsing photos by author => once step 1 is done, this could be implemented with a plugin
3) having a relation between users and authors => this was implemented years ago with piwigo_images.added_by. We know which user has added which photo.
<!-- github-comment-id:221606351 -->
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.
Reported by VDigital on 26 Dec 2006 10:27
Author have to be managed.
auth_id is mandatory to avoid all difference from time to time.
Access as a category or a tag access has to be implemented.
A link between member and Author has to be defined.
Maybe later a role has to be created as vimages explained.
Topic related is http://forum.phpwebgallery.net/viewtopic.php?id=5693
Piwigo Bugtracker #607
Comment posted by VDigital on 31 Jan 2007 07:57
Acked (without h), just to promote it.
I don't know if we have time enough to do it in 1.7
Comment posted by plg on 2 Feb 2007 16:16
> I don't know if we have time enough to do it in 1.7
No, we don't, but you're right to promote this feature request. We have to make it right after branch 1.7 fork (on trunk, of course).
This feature request is a bit confused and mixes several ideas:
converting piwigo_images.author from a textfield into a list of values => we implemented it for search in Piwigo 2.6, see
0511ed2236=> now we should go further and implement it "the clean way", with a piwigo_authors table, numeric id and so on. See #486browsing photos by author => once step 1 is done, this could be implemented with a plugin
having a relation between users and authors => this was implemented years ago with piwigo_images.added_by. We know which user has added which photo.