DigitalShoestringSolutions / LocationTracking

GNU General Public License v3.0
0 stars 0 forks source link

Old product names appearing - browser cacheing? #17

Open tobyaharris opened 1 day ago

tobyaharris commented 1 day ago

Often when testing this solution I find ID Entry names from previous tests appear unexpectedly.

I have a test setup that I'm done with. For sake of example l used a product type called MyPredefBulk1 with identifier blk1. I run ./stop.sh, docker system prune -a -f, delete the git clone of LocationTracking and restart the pi. docker ps and docker images both return a blank table. There is no trace of the location tracking solution left on the pi.

After reboot, I clone LocationTracking again, run ./setup.sh, docker compose build and ./start.sh. I log into :8002 and create a new product type (with a unique name I haven't used before, say prod1) and add an identifier to it, also novel eg p1. I move one unit of this from one of the default locations to the other. The name shown in the dashboard is not prod1 - the only product type in the database - but MyPredefBulk1 which doesn't exist in this build.

Could these names be cached in the browser? Where else are they stored? I know there is an autoid underneath each name, to allow renaming and it's plausible that these product types are sharing an autoid. But why isn't the autoid to ID Entry name lookup table being replaced too?

image

tobyaharris commented 1 day ago

Closing the browser window and opening a new one resets the name to loading... momentarily before showing the correct name. Suggests it is a browser session cache.