Thread

Since EE is only going to be used for a small part of my site, I installed it in a folder named EE. When users log into my MAIN site, the database in which their data is stored is not the EE database.
How can I make the login transition WORK when users who are logged in go to the EE area of my site? I need the login to function for my pre-existing site AND EE… so that users will not have to log in twice with different user names and all.
IF you can imagine that I might find a solution, please check out my description below and give me some help or direction:

My website has a login problem when EE is employed…

Go to http://www.accomplishtheimpossible.com

See that you are not signed in (upper right)

Go to my EE Blog Test Dev Area:

http://accomplishtheimpossible.com/EE/index.php?/tutorial/BlogTest_002/

It appears to be OK

Now, go back to http://www.accomplishtheimpossible.com and sign in

Using my TEST ACCOUNT so you don’t need your own:
user: .(JavaScript must be enabled to view this email address)
pswd: systemtest

You will see that you are logged in as “System” (upper right)

Now go back to the EE Blog Test Dev Area:
http://accomplishtheimpossible.com/EE/index.php?/tutorial/BlogTest_002/

SEE the PHP error:

Notice:

Use of undefined constant user - assumed ‘user’ in /home/content/s/t/e/steffans/html/AccomplishTheImpossible/EE/system/core/core.functions.php(663) : eval()‘d code on line 16

EE Login and my ATI login would have to be COMPATIBLE for my site to really use EE in a way that would include Comments on Blogs and Searches within Blogs and all that.

I ASSUME it would cost TOO MUCH and take TOO LONG to figure this out BUT if I am wrong, I would like to achieve this!

-Steffan

magicss,

This thread would definitely benefit in our Community Help forum so moving it there.

Go to my EE Blog Test Dev Area:

http://accomplishtheimpossible.com/EE/test333.php

This does not look like an EE URL. Did you rename the index.php to test333.php?

Not sure if this is really on-topic, but if you manage logins exclusively through the main part of your site, you might then use (for example) the LogMeIn plugin to log the user into EE at the same time.

See: LogMeIN

I corrected my link to the test page that will produce the error. (Thank you, you were right. My original posting has been corrected.)

So, the LogMeIN looks good, but I would still have a problem I think: at my custom (non EE) PHP site I have USERS with their own login and password. When they go to my BLOG, I would like my blog to be powered by EE.

So, I could make an entry notice to my blog that says “Dear User, please create a second username and password for my EE BLOG and then you can use this one part of my site too…!”, OR I could fix this problem so that the USER is already logged into EE as an INDIVIDUAL.

LogMeIN seems to log in a GROUP of some kind and the info about it appears to assume that the entire site is EE based whereas mine is custom php until the user enter the blog. (There is a good reason for these previous choices, and I can not rebuild all to fit EE.) So, I either solve the login problem which could involve LogMeIN if I am willing to not have any individuals post comments to blogs which would be an unhappy compromise, OR I FIX IT. But, I am not good enough with code yet to even know where to fix it. I suppose line 663 [EE/system/core/core.functions.php(663)] might give someone a clue. Basically the user name and password and cookie variables between the two PHP systems must be resolved and handled somehow! I do not know how….

In an ideal world when one of my users creates a new account in my php system, the code would go to the EE database and create the same account there. And, when the user logs into my main system, the code would go to EE and log them in too, so, in the event that they go to my blog, they would be logged in there too. Or something like that.

Many Thanks,
-Steffan

Sorry if LogMeIn wouldn’t work for you.  I haven’t actually used it, and didn’t know what would happen if you specified a username that already exists.  (Did you try that out?  The change log for EE2 suggests that the plug-in does check the member table.)

Of course, that would be only half the issue even it if worked for your application; you’d still need a mechanism to create parallel accounts.  I wasn’t sure if users self-registered or not.  If you only created accounts manually, it might be more feasible.

Maybe you could consider moving your whole site into EE!  :roll:

I like EE but I can not move my whole site to EE.

Users self register at my main site.

I am using ver 1.7 of EE, not EE2.

So how would LogMeIN work for me?