@duncanmaguire
On page two, you can’t have onReady multiple times, it should only be listed after the imports at the start of the code.
Have a read of onReady here:
https://www.wix.com/corvid/reference/$w.html#onReady
The rest of your code on page two should be something like this:
import {session} from 'wix-storage';
$w.onReady(function () {
const title2 = session.getItem('title');
const price2 = session.getItem('price');
const class2 = session.getItem('class');
const days2 = session.getItem('days');
$w('#title2').text = title2;
$w('#price2').text = price2;
$w('#class2').text = class2;
$w('#days2').text = days2;
});
The trouble that you’ve got is that on page two you are trying to populate the dropdown with the code from session storage, which would work in normal practice.
However, with your code that dropdown value could be any of the options as they are all called regiondropdown.
So yes, it might redirect to the right page from the code on page one, however when it comes to page two, it can’t give a correct value as all of them are the same value.
See in my example code above for page two, each session get item value is for a different option, so that it has a definite answer to put as the value.
You can go down a long and boring route with setting up multiple dropdowns that are overlayed with each other and called say regiondropdown1, regiondropdown2 etc which correspond with each region, so Africa = regiondropdown1 etc.
Then on page two, you can have all the regiondropdowns set up as hidden on load and set to be only shown when the corresponding region was clicked on page one.
So, when Africa is clicked on page one, then when page two loads the regiondropdown1 is shown with the value shown as Africa.
The other option would be to just dispose of having it as a dropdown value and have it setup as a simple text element that just displays the value of the region button that was clicked on page one.
If you wanted, you can still keep the existing region dropdown so that it is still usable for your search on page two, just not have it connected to the sessions storage from page one, instead keeping it all within the data query of the search.