Hi "developer",

There is currently no "browse by author" feature. But you can search a specific author in the search page. Of course, it is not as user friendly as a click on the author name below a given photo.

You can use an alternative, add a tag "author:John" or "author:Sarah", then you will be able to see all photos from a given author.

If you want to tag all photos where author is "John", do the following:

1) go to Administration>Photos>Caddie
2) if the caddie is not currently empty, in the "Caddie management" check the "Empty caddie" option and click on the "Submit" button
3) go back to the gallery (click on the "Visit the gallery" link in administration header)
4) go to the search page
5) in the "Search for an author" field, enter "John" and then click on the "Submit" button
6) you are now on the thumbnails page, click on the "add to caddie" icon
7) go to Administration>Photos>Caddie
8) in the "add tags" field, type "author:John", press the "Enter" key to validate the new tag
9) select "all" as "target"
10) click on the "Submit" button

Job's done, you can virtually browse your gallery by author.

Can somebody create such functionality? If not for free may be for some fee, let me know how much it could cost. I really need it. Thank you!

plg wrote:

what's more difficult is to convert the data model from images.author into a dedicated table authors{id, name} + images.author_id and then to modify existing code to select/insert/update the author in the new table instead of the old images.author field.

Optionnaly, we could need have an "authors" page (just like the "tags" page).

(I'm not saying yet that I'm going to code it, I just write the technical specifications without going too much into details)

Convert is not difficult but "modify existing code to select/insert/update the author in new tables" has a heavy impact on API processes and Synchro process. An impact on coding and on performance.

@plg,
Why do not trying to collect authors and their related images by an asynchronous logic?
So we don't have impact on current processes.
Based on a check of recent images.date_update (new) or images.date_metadata_update (existing).

(I'm not saying yet that I'm going to code it as well).

plg, yes I need it short term 2.1
Whats the advantages of more difficult solution? dedicated table? I mean as for performance it wouldn't affect it no matter which solution is used, am I right?

I am fine with easy solution as long as it works and less code is actually better for performance usually, if everything is managed within core functionality. Correct me if I am wrong =)

Thank you for suggestions. Let's make it happened =)

Thank you plg!
If tags exception is possible [Forum, topic 16132] Tags exception
I can do url rewrite, the main thing is functionality in next few days =)