01-08-2017, 04:33 PM
Dealing with google/fb might be the easiest part of it because we do those with their own includes. So let's take a look.
Let's say you have
mydomain.com
mydomain.com/youroldfiles
mydomain.com/users (The bulk of the userspice files)
Let's say you have your login page (just for reference at)
mydomain.com/youroldfiles/yourlogin.php
If you open OUR login.php file and go to lines 117-124, you'll see that just above our actual login form, we have
That is all of our fb/google logic being included. So you could put that on your own login form in one of two ways...
1. Change the require once statements to "back out" of your folder and go over to the UserSpice folder.
2. Put in the full url
I hope that helps.
Let's say you have
mydomain.com
mydomain.com/youroldfiles
mydomain.com/users (The bulk of the userspice files)
Let's say you have your login page (just for reference at)
mydomain.com/youroldfiles/yourlogin.php
If you open OUR login.php file and go to lines 117-124, you'll see that just above our actual login form, we have
Code:
<?php
Code:
if($settings->glogin==1 && !$user->isLoggedIn()){
Code:
require_once $abs_us_root.$us_url_root.'users/includes/google_oauth_login.php';
Code:
}
Code:
if($settings->fblogin==1 && !$user->isLoggedIn()){
Code:
require_once $abs_us_root.$us_url_root.'users/includes/facebook_oauth.php';
Code:
}
Code:
?>
That is all of our fb/google logic being included. So you could put that on your own login form in one of two ways...
1. Change the require once statements to "back out" of your folder and go over to the UserSpice folder.
Code:
require_once '../users/includes/google_oauth_login.php';
2. Put in the full url
Code:
require_once 'http://mydomain.com/users/includes/google_oauth_login.php';
I hope that helps.