Check session variable before delivering cached page

@odessite schrieb:

So you don’t use shopware login system at all?

In case customer logged in to shopware - he can’t do anything till log in to 3rd part service?

 shopware login system is still in place, so is registration and all that. At the moment the only way for the user can finish the checkout is by making a guest account, but that is besided the point here, that’s  another functionality.

the 3rd party service is delivering data that is imported to shopware and the „logging in“ actually takes place by a shopware controller that gets the 3 pieces of data the user submitted and just checks if an entry with this 3 pieces of data exists in a custom table in the shopware database (much like a normal login uses email and password, but the data we are using is from 3 parts).

until the user provides this data he can’t do anything (but look at the login form). from the moment he puts in the 3 pieces of data (and they are verified), he is a normal user of the shop, can use all the features and when the time comes for checkout, he needs to provide user information and addres and so on just like a normal guest on a normal shopware site would. Because those data is not included with the data we get from the 3rd party service…

imagine that you have a „private shop“ that only users that have been told certain secret words can access… and this session check needs to happen before the page is loaded from cache. If the site is in development mode it already works fine. All i need to do is move this check before the cache is checked…