I have a product filter set up in a lightbox. I used session.setItem to save the selected and use session.getItem to retrieve it. I use session because I want the selection to be preserved when moving between the product page and product gallery so that users don’t have to reselect everything and it does work on desktop version where I don’t use a lightbox.
However I have the following psuedocode going on :
-
starting on productGallery on desktop version select red then switch to mobile version
-
session.getItem(‘filterObj’) returns [‘red’]
-
open the filter lightbox, session.getItem(‘filterObj’) returns []
-
user selects “blue”, add “blue” to filterObj and session.setItem(‘filterObj’, filterObj)
-
session.getItem(‘filterObj’) returns [‘blue’]
-
close lightbox to return to productGallery and session.getItem(‘filterObj’) returns [‘red’]
Essentially it seems lightbox has its own ‘session’ independent of the site’s ‘session’. Is this yet another bug of Corvid? It’s does not seem to be documented anywhere that lightbox have their own ‘session’ nor should they in my opinion.
I know I can pass data from lightbox through coding, but it would be redundant since it would mean that I would have to pass the data and then run session.setItem again even though it already did when the user chooses what filters to add.
I am passing this on the QA for evaluation.
@yisrael-wix Thanks, is there anywhere that has a log of the bugs that Wix has and whether or not they have been fixed so I can know when this is issue is fixed? Preferably where one can follow the bug and be notified via email when it is fixed.
I have reported another bug to the Wix support regarding duplicated elements that are in repeaters retaining their original onClick()/onChange() handlers making them fire twice if you try to attach a script to them, but it took them over a week to say that it I need to use the Render API which doesn’t even make sense considering the onClick()/onChange() handlers fires the original script it was attached to (before being duplicated) even when it is left blank. If the issue was due to it firing once on client and once on server side, it would fire twice when there is an onClick()/onChange() handler attached but not at all when there isn’t any script attached under the onClick()/onChange properties. I even showed them a video of me recreating the bug. Note that switching between preview and editor was insanely slow, so please scan through the video to save time.
Sorry to bother you but you are a lot more competent than the Wix support that just bounces around to a new member in each message, which gets frustrating fast.
@briapril30 Please post this latest problem as a separate post. Please explain what you are trying to accomplish, what works, and what doesn’t. Share your code in a code block.