-
Notifications
You must be signed in to change notification settings - Fork 15
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
Error: 402 Payment required #5
Comments
This is the same error i get on the Google Authenticator. |
How have we not seen all these messages since May! Sorry guys! I believe this is a hack to get around some browser quirks in the back office but I'll double check to see if we can recreate this one like you show it. Thanks for reporting it. |
I am also facing same issue with Umbraco 7.6.3 |
Hi We are having the same issue with the Payment Required message - is this working with version 7.7 yet? Many thanks |
also facing same issue with Umbraco 7.7 |
Hi guys, We had a blocking issue in Core (http://issues.umbraco.org/issue/U4-10620) that we were waiting before we looked at this one...then we forgot to double check it! Thanks for the nudge. We will get some time scheduled in to look into this one asap. Pete |
BTW can you guys confirm which version of the package and Umbraco you are running? |
We're running Umbraco 7.6.13 and installed the package from the package repo in Developer (not a local zip file) I'm just trying a clean install of Umb ver 7.6.12 and ver 2.0.0 (froma zip) of 2FA - I'll let you know how I get on. Cheers, Aron |
Is this still an issue since the PR was merged? https://issues.umbraco.org/issue/U4-10620 |
I just installed the plug-in and I see that error. Did anyone manage to have a workaround? |
Hi there,
first of all I love the idea of the package you've created! Have been thinking a lot about a package about this, but without Umbraco 7.6 it was almost impossible to create it. I have been doing some testing today and may be you can look at some issues I was facing.
This will maybe have to be related to the fact that I don't have a SMSprovider implemented? If I disable the SMSProvider in the config-table and restart the application everything works fine.
The text was updated successfully, but these errors were encountered: