RP 3.11 - joint registration with PP 5.21

[Chuck S]

If you set your Forum and Photopost Products to the same cookie path cookie prefix and cookie domain .domain.com being the optimum choice because it works with all subdomains you will have no issue.

I can only assume here any weird issues can only be caused by cookies not set exactly the same between the forum and our products. This is my experience on the matter.

I had a user today who swore up and down his forum cookies where set to match photopost and had issues only to find out his forum cookie path was set to /forum/ so cookies not matching are always what I find the issue to be.

[snoopy5]

Hi

after playing around again and again, I found the problem. It was my cookies in my browser. They seem to cause the trouble. After I deleted all cookies in my browser which are dealing with my domain name, the login/logout problem disappeared immediately.

So now my current setting are the following in all 3 installations (PP, RP, CL):

in admin menu/cookies settings:

PhotoPost xxx Cookie Path: "/"
Forum Cookie Prefix: empty
PhotoPost xxx Cookie Domain: ".mydomainname.com"

With this setting it works without any problems so far.

Originally Posted by Chuck S

If you set your Forum and Photopost Products to the same cookie path cookie prefix....

Could you please explain what this "Forum Cookie Prefix" does exactly? And how I have fill the field?

Thanks in advance

[Chuck S]

Cookie prefix is only used in external installs usually so what type of installs are these standalone? If so then empty is fine.

A cookie prefix is one that precedes the cookie name so if cookie is password say in vbulletin it would be bbpassword.

[snoopy5]

My current setup is the following:

I use photopost pro 5.3 as the "master" database/registration system. With Photopost pro, I integrated Reviewpost 3.3 and Classifieds 2.5

There is no discussion forum/bulletin board integrated and I am not planning to do so (at least not with vbulletin)

So I guess I do not need that field "Forum Cookie Prefix", right?

[Chuck S]

Right it would be blank we do not use cookie prefix

[snoopy5]

Hi Chuck,

I am currently with amember their cookie setup to use shared resgitration with different applications, which are on different domain names.

Since Photopost seems to achieve this and we discussed it here in this therad how to set it up in the admin panel, I wonder why this shall not be possible with amember too.

I am not talking about the photopost plugin of amember. This shall work properly with the photopost shared regsitration.

I just mean in general with other applications (forums), why do you succeed to offer this shared user regsitration, no matter on which domain your products are installed and why amember does require the same domain or at least a subdomain name for other software?

So this is a more technical question. Can you help me out here?

The answer of amember:

---------------

> Is there any workaround for this?

No. Cookies will work within one domain only.

----------------

But I thought Photopost is also working with cookies only? So why does it work here and not there?

[Chuck S]

If you logout and are still logged in there can only be one of two things here.

Your applications are not meshed to the same cookie domain and or you have an old cookie on your computer.

I would suggest you make the cookie settings match in the application then clear all internet cookies in your browser and then try you should be fine then.

[snoopy5]

Hi Chuck

this is a misunderatnding. I have no problem with Photopost at all. And I have not yet installed amember on my server.

Currently I try to figure out, what amember can and what it can not do.

It seems that photopost has succeeded something, what amember can unfortunately not do:

This is a single user login even if the applications are installed on different domain names.

If I use amember with other forum software (not Photopost products), it can not provide single user login, if the other applications are installed on different domainnames (although on the same server).

So I remembered that Photopost is able to do that and I was wondering, what the trick is, so that I can use the same "trick" with amember for non-photopost applications.

Sorry for the confusing description, I hope you understand what I mean. Does this make sense to you?

[Chuck S]

Well I do not know anything about amember but you may want to contact them.

I do know they have a Photopost plugin that is suppose to allow you access to Photopost but can not really comment further on that.

Both our Reviewpost and Classifieds applications integrate with the Photopost login meaning the user is in the Photopost users table. Now amember supposedly can register a user and also places that user in the Photopost users table at least thats my understanding.