Login bug in Mezzanine site - mezzanine

we have just recently started on a project using the mezzanine cms platform. we were trying to implement the authentication/login feature but already encountered a problem:
http://usbong.pythonanywhere.com
when you click the "Login" button (the one beside Sign Up, not the link) nothing happens when the Login Form is supposed to show. Signup works just fine but you can't log in. Once you login using other means (admin), it's the "Logout" button's turn not to work.
any help please? thank you
EDIT: it appears that mezzanine.accounts and django's allauth appear not to work well together? because when we comment out allauth in settings.py, the login works. what is the workaround for both of them to work at the same time?

All auth supports username/password login. Any reason why you wouldn't just use that?

Related

Any experience with cypress-social-login using Facebook provider?

I am trying to make an automated test of the Facebook login feature in our web application in Cypress. I would like to skip the visual input of credentials and rather provide them programatically.
I came across the cypress-social-login plugin - https://www.npmjs.com/package/cypress-social-logins
Does anyone have the experience specifically with the implementation of this plugin for Facebook login? Or did anyone manage to automate Facebook login without any plugin?
Another question is: for the plugin to work, I have to provide a login url fom my application. But my application doesn´t have a specific login url. It uses a fullscreen modal that contains a Facebook login button. Is there a way to modify the plugin to deal with this?
Meanwhile I accepted this fact. But I was successful by using another much simpler approach: First I go to facebook.com and log in there. Then I open my App and click the Facebook login button. In this way I can simulate the majority of users that are already signed in.
Unfortunately, when I run the tests on Lambdatest, Facebook won´t let me sign-in and tells me that I am misusing their services by going too fast :D
For now I am left by running tests locally.

App review says Login button does not work

I am working on a project that needs a permission for user_link. Functionality that implements this feature is currently implemented on https://staging.meetmeinthe.bar/. I have fixed all of our bugs and made our app comply fully with the requirements. But, for some reason, one of FB reviewers keeps declining our submission, saying that our Login button does not work. We have tested our login functionality many times from multiple devices - it works. Why do we keep getting rejected? Any advices are welcome.
When you land on a web page, you should click orange "Login" button in the top-right corner to see it.
Thanks in advance for your time!
The solution was to contact support that verified the fact that everything was working correctly.

How do make the list of facebook application users not show upon login

I am using the javascript SDK as shown in the documentation, my issue that when the user logs in, a list of users that have already allowed the app shows in the position of the login button. Any one have any ideas as to why this happens and/or how to fix it.
edit: seems like its the facepile plugin, but i havent specifically enabled that plugin.
oops, i had the data-show-faces attribute set.

When I use the facebook javascript SDK for authentication it fails on mobile phones and ipad

Javascript authentication works great on browsers but once I use the website on mobile, I always get this error on the login popup.
Sorry, the application you are using is misconfigured for Facebook integration. Please download the newest version of the application.
Instead of showing the usual login popup, it goes to m.facebook.com and it produces this error. Whats interesting is clicking on the spanish link, makes it work again.
--EDIT--
After doing some research and tinkering, ive nailed it down to this:
<fb:login-button registration-url="http://www.example.com/page#register" onlogin="authenticate.facebookLoginCallBack()"></fb:login-button>
Its possible the pound sign blows it up. I need the pound sign because i dont want to redirect off the page,instead i want to trigger a js registration popup.
My guess is that the # gets into the redirect-url, and then must somehow get transformed again on its way to getting redirect to m.facebook.com and that makes it fail there.
--EDIT--
I thought about redoing the flow by creating my own button and calling FB.login, but there is no way to tell the API to stop at login, and load my own registration. The problem is summed up here Registration flow using FB.login
Realistically it seems we are only provided with one option here:
https://developers.facebook.com/docs/plugins/registration/
Login + Registration Flows
and it doesnt work in my situtation
VISUALS
Typically the user clicks on this button
Then they see this dialog. (Notice it says www.facebook.com in the url)
But they see this dialog on mobile. (This is loading from m.facebook.com)

Blank popup with FB connect

I've implemented the facebook connect using Javascript SDK. The authentication works fine when the user I'm trying to authenticate is not logged into facebook. But when he's already logged into facebook the login popup never closes. The url of the popup starts with "http://static.ak.fbcdn.net/connect/xd_proxy.php#cb=....."
This happens both on Firefox 3.5 and on Chrome.
Any suggestions? Do I need to set any extra parameters while connecting to Facebook?
I've encountered the same error today, with my year old implementation. I've added the channelUrl tag to FB.Init(), without any luck; so I started the login procedure from scratch with the js sdk, oauth2 enabled: with some minor changes, everything started to work misteriously again. I've run my pages through the Facebook debug tool as well, it suggested some changes as well.
To sum up: basically, if Facebook Connect stops working, upgrade your code according to the latest documentation avaliable.
No special parameters are needed. This is probably a browser problem. Maybe you have a setting/plugin somewhere that does not allow Javascript to close a window for you.
The easiest way to test this is to post a link to your implementation so that other people (with other browser setups) can give it a try.