My understanding was that the registration plugin allows you to use the same reg form for users not registering with Facebook as well with Facebook. However, if a user is logged into Facebook and visits the registration page the form prefills information and only gives them the option to register with Facebook. That's kind of a freaky user experience. They hit the register button on your website and it auto fills fields with Facebook info without permission. Just because a user is logged into facebook doesn't necessarily mean they actually want to create the account with their Facebook information.
Here's what I have handled so far by the registration plugin:
User is not logged into Facebook and registers via the plugin, but with my site authentication not Facebook.
User is not logged into Facebook, uses the plugin to log into Facebook, fields are prefilled and user registers via Facebook.
Here's what I dont have handled
3. User is already logged into Facebook, but may want to register with my site authentication and NOT connect the account to their Facebook account. Currently, it prefills the forms and provides them with only a register button connecting Facebook to my app.
Basically, I want the user to have to opt-in to register with Facebook even if they are logged into Facebook, but I want to use the Registration plugin form. Is this possible?
I hope that makes sense.
A user can clear the fields by ckicking the X when mouseover the name field
What you need to do is something similar to Scribd approach, where you can by default wrap and hide the "Login with facebook" button (or the registration form if the user is already logged in and connected!) and for example in your form div/container have a checkbox (a location over the flow is preferred) stating:
Register with my Facebook account
Or something more catchy and when the user clicks/checks the input the facebook DIV will slide down and used instead of your registration routine.
Related
Whenever the user register on my Shopify website i want that account to be disabled until admin enable it from back-end panel. Currently when user is registered, his account is enabled by default.
Have searched various forums even tried Shopify support but still no luck.
There are two options. why you are not putting "request membership" sign up form instead of sign in form (disable from here)? You could use the contact page for that if you wanted. Then you get an email when they fill that out. You would create the account (just copy and paste the info) and email them an invitation. They click the link in the invite to make the password. (I think it will be a tedious task for you)
Otherwise, let them create the account, but hide the pages with the Locksmith app. Then after you approve them you would apply a "tag" to the customer account so they can see the pages and products locked with Locksmith.
I'm hoping that a Bigcommerce rep can answer this. I had some trouble accessing my Bigcommerce store to get my support PIN so I'm posting here.
I am developing a Bigcommerce app and am wondering if the Bigcommerce user must automatically be logged into my app when they open it in the iframe, or can the app display a login page inside the iframe when it opens?
I've seen some apps first display a signup page for the user to fill out, and I was planning to also first display a signup page for the user to create an account inside the app, then ask them to log into the app on the next session. Is this allowed, or do I need to implement OAuth in a way that allows the Bigcommerce user to log into my app based on their store during the app load?
Thanks
I am building a basic login page using the existing sign-in portlet.
I just want to have a functionality that when a user access the website, right now localhost:8080, the sign-in portlet should pop up!
Is this doable? If so, Can someone please hint me how this can be done?
This is how the default page looks like right now:
To log in, I have to explicitely click on the "sign-in" blue button and then it pops out a modal sign in portlet.
But what I am trying to do here is:
Whenever a user clicks on the default url, it should immediately ask the user to login rather than showing a blank page with a sign-in button (something like the output image)
Or even a modal sign-in box (Whatever is easy to customize.)
and
Whenever a user hits any other url for eg. localhost:8080/web/project1/home and if the user is not signed in, it should force him to sign in first.
Two possibilities out of the box:
place nothing but the sign in portlet on the homepage, appearing at that location (typically /web/guest/home)
protect your default page to be not visible to the guest user (this will automatically forward to the sign-in portlet) - see the "Permissions" button on the "Manage Pages" interface
There are more, but these seem to be the first and most obvious ones. Let me know if one of them works for you or what the reason for your request is
From what I understand, you want the Login Portlet to popup as a modal window/lightbox on the current page (i.e. without leaving the page). AFAIK, to achieve this, you'll have to develop all your portlets to use AJAX to create links that point protected resources. So when you get an unauthenticated request, you can stay on the same page and show login dialog.
This is high-level approach. You'll need to 1) embed the Login portlet in your theme and 2) put the below javascript functionality in Theme:
callback function - to handle response for unauthenticated request,
to render modal/lightbox
You might face surprises while implementing this.
I set up an app to allow users to log into my site using Facebook. When users click the FB login button, the expected auth dialog appears. My auth dialog shows a second page which says: "This app may post on your behalf, including status updates, photos and more."
But my app doesn't need any extended permissions, and will not be posting anything to Facebook. I don't want this second page to appear, but I can't figure out how to make it go away.
On my app's settings page, I didn't specify any extended permissions. Is there someplace else I have to specify that I don't want extended permissions?
Thanks for the help.
You might have specified a scope in the "Login with Facebook" button that requests these permissions from the user. Especially if you just copy-and-pasted an example from the documentation, this might have happened.
Check in your HTML whether you have something similar to this:
<div class="fb-login-button" scope="publish_stream">
Login with Facebook
</div>
If so, make sure to get rid of the scope attribute.
I'm having a very weird issue with user logins.
I'm building a site where all the content/menus are only available after you login.
I made a 'login' through the Modules and assign it the "userlogin" position.
Now when I go to the home page or any page, the login box comes up, but there's also a second login form. It seems to be coming from com_user.
This com_user login form doesn't work. I can't login using any credentials. If it was working I can simply remove my login module.
Is there a way I can either:
get com_user to work with normal user logins
or
disable this and so I can only see the Module login.
I can hide it from CSS, but I want to know where it's coming from.
Check the menu link which you have created should be public.
If these are not public then whenever user clicks it, he/she will be asked for login. Thats why the second login option is coming up.