Frustrating search results
RekindlePhoto
6 Jun 2013 14:19
When searching and sorting by number of sales, if you click on a footage for a preview then hit the browser back button to go back to original results page, it goes back to default not number of sales.
ryanp5
10 Jun 2013 18:01
Hey Don, thanks for posting this. We're aware of this problem and it has already been noted in our system to be fixed. We're working on the solution as we speak!
Cheers,
Ryan
Pond5 Crew
Cheers,
Ryan
Pond5 Crew
tiberio
20 Jun 2013 02:51
this is probably because they do not have 1 single universal function for reading environment variables, such as search requests.
env variables can be stored in form data (cgi), hand coded in urls, in cookies, in user prefs stored in the database, or on a file on the server.
they probably use one function that reads from form data or cgi, and another that reads from the cookies, and they are using different functions, so it is not clear where the priority is, and then you see differing behavior on the site.
this is solved by writing an env function that uses unified variables in every location where the values can be stored, and then searching in this order: 1st form data or cgi, then hand coded urls, then cookies, then user prefs, then defaults. return the first one that has a successful match as a request object, and call this 1 function from all scripts on the site in the CMS. this will ensure you get the same search defaults every time, as long as any updates to env variables are recorded immediately when changed.
env variables can be stored in form data (cgi), hand coded in urls, in cookies, in user prefs stored in the database, or on a file on the server.
they probably use one function that reads from form data or cgi, and another that reads from the cookies, and they are using different functions, so it is not clear where the priority is, and then you see differing behavior on the site.
this is solved by writing an env function that uses unified variables in every location where the values can be stored, and then searching in this order: 1st form data or cgi, then hand coded urls, then cookies, then user prefs, then defaults. return the first one that has a successful match as a request object, and call this 1 function from all scripts on the site in the CMS. this will ensure you get the same search defaults every time, as long as any updates to env variables are recorded immediately when changed.