Actually I managed to get it to work on the phone by upgrading Chrome. According to caniuse, optional chaining became available in Chrome 80. In theory compatibility should extend all the way down to Kitkat. The lack of transpiling is a bit concerning though.
In my custom route I use:
var requestedURL = req.originalUrl; // [...| req.session.returnTo = requestedURL; return res.redirect('/login');
to redirect the visitor to login page if he's not logged in.
I need this because the visitor calls:
he should log in and after successful login he should be redirected to
The GET-Params are absolutely necessarily.
It works like a charm if I call the page directly, but via
ajaxifyit does not work. So back to topic:
Is there a equivalent to
What exactly isn't working? They aren't being redirected to the login page? They aren't being redirected after login?
You might need to use this:
@pitaj I'm sorry. The page leaves blank after clicking the link. So it does not redirect to login. It turns white and endless loading spinner.
Excuse me but can you help me a little more. I don't know excatly how to deal with the given function...
ajaxify.end. Don't know how to trigger.
But your sent link is on the serverside as well? Or isn't it?