Bug #1446
closedLogin events should fire and the redirect to CB login form should not happen again if events do redirect
Description
E.g. CBSubs needs those events to propose plans upgrades to blocked user
I added the event triggering earlier, but got following unwanted issue:
That happens with a redirect, but then FBC does a second redirect, as it didn't clear the need to redirect BEFORE the events get fired.
To reproduce: wait for expiry of a very short mandatory subscription for a FBC-synced user, then try logging him in: you will see in browser url a quick redirect to cbsubs then a second redirect to CB login form.
With "Tamper Data" firefox extension (side-bar) you can observe those redirections too.
Wanted behavior: events get fired, and if there is a redirect in the event, there is not a second following on the page after by FBC.
P.s. For the event firing, we should adapt the CB 1.2.2 authentication API to suit your login without password.
p.s.2. Issue #1445 needs also to be fixed for that to work properly.