In that case, a cookie path of / without specifying a cookie domain would do it. (I have no idea if setting a domain works without also setting a path.)
The login cookie names should be ignored in favor of what's in the integration file.
I asked in the EE forum about the cookie setting as well and they told me this: ------------ EE gives all of its cookies a prefix of 'exp_' by default, which prevents EE from interfering with other scripts that might have similar cookie names (this prefix is settable in the Cookie Configuration area in the Admin section of the CP). I doubt that EE is interfering with your script's cookies for that reason. I know nothing about what this script is doing but you should be able to be logged into EE and this script at the same time unless your script is removing all cookies somehow. ------------- Then he wrote that maybe he read wrong but I think the info on the prefix might help in some way.
I just dont know anything about how cookie settings work so I am at a loss on how to set them to work properly. I just dont get the big picture on how they interact with the login.
Should I be setting the cookie setting in wsn the same as EE? Also for the login cookie name, wsn has it as wsnuser and wsnpass, are these right or should they be named something from EE?
I was presuming you'd already specified your cookie info. Looking back at the integration file you posted, actually you left it all blank I see. Did you mean to fill in that part of the integration generator? It looks like you skipped all the cookie info.
I asked about these settings on EE and they said this: --------- EE can use cookies, but it does not store the password information in a cookie. Your best bet is to leave that section blank. ---------
I asked about that before the generator use.
SO if I leave everything blank becasue EE doesnt have this how will I get this to work correctly?
Paul this does not seem to be working for me. It was able to integrate memberstable but for some reason the login part of it messes up somewhere somehow. So , because of this I have decided that maybe it will work better if I try to use a php include function into the EE system templates. Now I tried the php include but once I click on a link such as category or details of a link I do not go to the proper page. I assume the reason is because the links template does not have the full url to those pages and so it doesnt know exactly where to look for them.
1. So knowing this, Im wondering what it would take to fully make the include work. What other setting could I make other than the just the url to the links and turning off header and footer , do I need to make this work smoothly?
2. It seems that making the urls to all templates a full url to the pages will be a long process. Is there another way to do it?
1.I can login to one or the other.If I try to get my password from one by using forgot password and I use it on one login area , it does not work on the other script then. I can definitely see the members in both scripts. Yes , I am sure about EE using md5 because upon installing EE I get to choose what type of encryption I want to use and I chose md5 especially because I knew it was needed for wsn integration. I installed them both one after the other.
2. As far as the include, I thought you would know about it as you are a php programmer right? its the code that allows me to include other php files into another page with php extension.
it usually looks like this:
<?php include("index.php"); ?>
so I would include the index of wsn but remove the wrapper from the templates so that the EE templates would serve as the directory wrapper. So really the page would be embedded in the EE site and the links would not work correctly unless the link paths were full urls of the wsn script. SO thats what I meant about that.
1. Actually md5 isn't needed for WSN integration. But anyhow, if password reseting is your only problem then edit the templates to link to EE's password resetting.
2. You may as well just insert it with javascript, you're not actually getting any PHP when you use a full url, only HTML. And I still have no idea what you're doing, except that I guess you're trying to actually run one script inside the other, which is really a bit absurd.
0/5
1
2
3
4
5
This thread is closed, so you cannot post a reply.
Comments on integration script generator
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
In that case, a cookie path of / without specifying a cookie domain would do it. (I have no idea if setting a domain works without also setting a path.)
The login cookie names should be ignored in favor of what's in the integration file.
Experienced
Usergroup: Customer
Joined: Oct 10, 2003
Total Topics: 19
Total Comments: 69
I asked in the EE forum about the cookie setting as well and they told me this:
------------
EE gives all of its cookies a prefix of 'exp_' by default,
which prevents EE from interfering with other scripts that might have
similar cookie names (this prefix is settable in the Cookie Configuration
area in the Admin section of the CP). I doubt that EE is interfering with your script's cookies for that reason. I know nothing
about what this script is doing but you should be able to be logged into EE
and this script at the same time unless your script is removing all cookies
somehow.
-------------
Then he wrote that maybe he read wrong but I think the info on the prefix might help in some way.
I just dont know anything about how cookie settings work so I am at a loss on how to set them to work properly. I just dont get the big picture on how they interact with the login.
Should I be setting the cookie setting in wsn the same as EE?
Also for the login cookie name, wsn has it as wsnuser and wsnpass, are these right or should they be named something from EE?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
I was presuming you'd already specified your cookie info. Looking back at the integration file you posted, actually you left it all blank I see. Did you mean to fill in that part of the integration generator? It looks like you skipped all the cookie info.
Experienced
Usergroup: Customer
Joined: Oct 10, 2003
Total Topics: 19
Total Comments: 69
I should have reposted my integration file here again, I assumed you knew I had not filled that cookie part.
I asked about these settings on EE and they said this:
---------
EE can use cookies, but it does not store the password information in a cookie. Your best bet is to leave that section blank.
---------
I asked about that before the generator use.
SO if I leave everything blank becasue EE doesnt have this how will I get this to work correctly?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
If it doesn't store anythign related to passwords in a cookie, you can't integrate cookies. Just leave it blank and let WSN use the WSN cookies.
Experienced
Usergroup: Customer
Joined: Oct 10, 2003
Total Topics: 19
Total Comments: 69
Paul this does not seem to be working for me. It was able to integrate memberstable but for some reason the login part of it messes up somewhere somehow. So , because of this I have decided that maybe it will work better if I try to use a php include function into the EE system templates. Now I tried the php include but once I click on a link such as category or details of a link I do not go to the proper page. I assume the reason is because the links template does not have the full url to those pages and so it doesnt know exactly where to look for them.
1. So knowing this, Im wondering what it would take to fully make the include work. What other setting could I make other than the just the url to the links and turning off header and footer , do I need to make this work smoothly?
2. It seems that making the urls to all templates a full url to the pages will be a long process. Is there another way to do it?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
If you can't login, and it's not a cookie matter, are you sure EE actually uses MD5 encoding for passwords?
I can't help with the includes stuff because frankly I have no idea what it's about and it's probably something that requires knowledge of EE.
Experienced
Usergroup: Customer
Joined: Oct 10, 2003
Total Topics: 19
Total Comments: 69
1.I can login to one or the other.If I try to get my password from one by using forgot password and I use it on one login area , it does not work on the other script then. I can definitely see the members in both scripts. Yes , I am sure about EE using md5 because upon installing EE I get to choose what type of encryption I want to use and I chose md5 especially because I knew it was needed for wsn integration. I installed them both one after the other.
2. As far as the include, I thought you would know about it as you are a php programmer right? its the code that allows me to include other php files into another page with php extension.
it usually looks like this:
so I would include the index of wsn but remove the wrapper from the templates so that the EE templates would serve as the directory wrapper. So really the page would be embedded in the EE site and the links would not work correctly unless the link paths were full urls of the wsn script. SO thats what I meant about that.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
1. Actually md5 isn't needed for WSN integration. But anyhow, if password reseting is your only problem then edit the templates to link to EE's password resetting.
2. You may as well just insert it with javascript, you're not actually getting any PHP when you use a full url, only HTML. And I still have no idea what you're doing, except that I guess you're trying to actually run one script inside the other, which is really a bit absurd.