-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Craft 3 support #7
Comments
@espensgr We are working on Craft 3 support, but since we are not yet running projects on Craft 3 there is not a lot of time i get to spend on this. I'm hoping to get the plugin done in april. We will submit it same day we get the release done i'll submit it to the store. |
@roelvanhintum Good to know 👍 |
+1 😊 |
+1 |
@roelvanhintum Thanks for the great work so far. Any idea if the launch of v3 is imminent? Otherwise we'll develop our own solution. |
I'm working on it. I'm hoping to get things working today. Sorry, for the insane delay. |
Check 2.0.0-beta.1. It should be fully functional, i just didn't test it in a production environment yet! Please, let me know if you have any problems! |
Will do! Thank you! |
Thanks for the beta! Steps to reproduce:
Please correct me if I missed something |
@RichardFrontwise Just tried to reproduce the issue, but i got logged out as supposed to. Can you give me some specifics about your settings? Do you have a different admin path or domain? |
Did a clean craft install and the plugin works as expected! |
Thanks! Sounds like that should not influence the plugin.
|
Digging deeper: defaultCookieDomain results in a redirect loop.
|
Ok, i'll look into hooking into this on a lower level. Right now it passes through authentication and logs out when the 2FA is not verified. |
@RichardFrontwise in beta 2 the redirect loop should be fixed. I couldn't move the rest of the logic to a lower level due to some limitations in Craft's routing structure. |
Awesome, thanks! |
Debug toolbar issue is discussed in #9 |
Hey,
Any ETA for plugin store?
The text was updated successfully, but these errors were encountered: