With Piwigo 14.0.0beta3 (starting with beta1) we have implemented a new search system. One important decision in this new design is that a search can be "updated" with API method pwg.images.filteredSearch.update.
Now let's take an example when it's a real problem:
on monday morning, Peter copies the url of his search http://domain/index.php?/search/psk-20230927-QD6IP9evVB and sends it to Matthew by email
on tuesday, Peter keeps working on this search, adds some filters and modify previously added filters
on wednesday, Matthew clicks on the link and will see the updated search of tueday, not the search as it was on monday
That's a problem, because Peter certainly thinks that he has copied the search rules "as they are" at the moment of the copy.
Updating a search was an interesting idea, to avoid too many lines in the piwigo_search table, but leads to this kind of user experience issue. We must revert this design decision and create a new search each time a parameter is modified/added/removed.
With Piwigo 14.0.0beta3 (starting with beta1) we have implemented a new search system. One important decision in this new design is that a search can be "updated" with API method `pwg.images.filteredSearch.update`.
Now let's take an example when it's a real problem:
1. on monday morning, Peter copies the url of his search `http://domain/index.php?/search/psk-20230927-QD6IP9evVB` and sends it to Matthew by email
2. on tuesday, Peter keeps working on this search, adds some filters and modify previously added filters
3. on wednesday, Matthew clicks on the link and will see the updated search of tueday, not the search as it was on monday
That's a problem, because Peter certainly thinks that he has copied the search rules "as they are" at the moment of the copy.
Updating a search was an interesting idea, to avoid too many lines in the `piwigo_search` table, but leads to this kind of user experience issue. We must revert this design decision and create a new search each time a parameter is modified/added/removed.
<!-- github-sync-id:1915720883 -->
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.
With Piwigo 14.0.0beta3 (starting with beta1) we have implemented a new search system. One important decision in this new design is that a search can be "updated" with API method
pwg.images.filteredSearch.update.Now let's take an example when it's a real problem:
http://domain/index.php?/search/psk-20230927-QD6IP9evVBand sends it to Matthew by emailThat's a problem, because Peter certainly thinks that he has copied the search rules "as they are" at the moment of the copy.
Updating a search was an interesting idea, to avoid too many lines in the
piwigo_searchtable, but leads to this kind of user experience issue. We must revert this design decision and create a new search each time a parameter is modified/added/removed.