ecartz wrote: ↑Sat Feb 11, 2023 9:58 pm
If you're properly passing the session ID ...
Dumb question ... but what is the "proper" way to pass the session id? If you navigate between pages in Phoenix it doesn't register multiple entries into the whois database, and the session ID is not part of those urls? Also, I cannot replicate this, so not sure what session setup needs to be in place to have this issue occur? @mhsuffolk what version of Phoenix are you using?
Ah, this is interesting. My live shop is 1.0.8.4 which I have upgraded from 1.0.7.0. I have a clean install test shop on 1.0.8.15 and this does not do this.
ecartz wrote: ↑Sat Feb 11, 2023 9:58 pm
If you're properly passing the session ID ...
If you navigate between pages in Phoenix it doesn't register multiple entries into the whois database, and the session ID is not part of those urls?
My 1.0.8.4 live shop produces a new row for very page that the user navigates. Was this old behaviour and my updates have missed the change? This may be why I see this issue.
Point of Interest.
One good side effect of having a entry/line for every click is that hacking attempts can be identified very easily. On my live shop I sometimes get many repeated clicks a few seconds apart from one IP on privacy.php and shipping.php and others. These IPs can then be blocked.
If you use Href, then it will pass the session ID for you. If you use a GET form with Form->hide_session_id, it will pass the session ID for you. If the client's browser allows the session cookie, it will pass the session ID for you.
If you're building a link in Javascript, you have to duplicate those behaviors. So check if the cookie exists. If so, you're done. If not, either add it to the query string (for GET requests) or add it to the request body (for POST, PUT, etc.).
To replicate, I would start by using a browser with cookies turned off. This should force the session ID into the URL. Note: a Chrome profile would count as a separate browser in this case.
I was able to recreate the issue and coded in a fix
I will add a new option to allow admins to choose which behaviour they want.
I will also be adding a setting for number of minimum characters before an ajax call is made.
Just one question here
I'm using @raiwa KissIT image thumbnailer with watermark.
The search is directly calling the images with scr=
Is there another way to call the images where KissIt will still function?