9 replies to this topic

[kmf]

I'm getting mixed responses for this question (according to sales it's not possible, according to this forum it is), so I thought I'd throw it into this so I can get some feedback here.

In short:
I want my forum to be on one domain say: domainX.com
I want portal (ipcontent, blog, gallery) to be on another domain. Say domainY.com

They have to share the same database. So they also share the members table.

I know that the users can't autologin in the portal when they're logged in on the forum due to the cookies being on different domains.
But that's no problem. As long as a register on the forum also counts for the portal.

Replying/commenting on articles (if these were forumtopics) should reflect to the forum too.

Can I get a definitive answer if this is possible?


Also, what would be nice is if ipcontent can import certain topics from the forum and display as article and leave a "redirect topic" in place.
This is meant to migrate a (sub)forum to the portal.
So... ipcontent pull topicid123 from the forum and save it as article+comments (say article123). It should then change the topic123 into a redirect topic linking to article123

Is this possible?

[ADKGamers]

I've felt the same way.  Based on some things that have been said on the forums here, it seems possible.   BUT I did contact support and they said it wasn't possible.   So I just kind of left it at that and didn't say anything else.   But I'm glad I'm not the only one who seems confused about the different responses.    

If it's really not possible, I'm fine with that.   I just would love to be able to do everything that you stated pretty much.

[LeeGrant]

I would have thought that using two domains would not comply with the licence terms for one, especially if one is on domainX.com and one on domainY.com

[bfarber]

The answer is....both yes and no.

IP.Content includes a custom index.php that can be used outside of your forums to load it.  This lets you run IP.Content at domain.com and the forums at domain.com/forums (or forums.domain.com).  In theory, you could technically run this custom index.php from domainx.com while the forums are at domainy.com, however the two domains would need to be pointed to the same server and domainx.com would need to be able to include and read/write files at domainy.com (the special index.php is not completely stand alone - it still needs to load the IP.Board framework files).  This would require special permission setup on the hosting side.

As you noted, you would not be able to login to domainx.com.  IP.Board only has one configuration option for the cookie domain, so it would set cookies for domainy.com always.  This would severely limit the capabilities of IP.Content running at domainx.com (since no one would ever be able to login to it).

If we are talking about subdomains (domain.com and forums.domain.com) that should work fine.  Some AJAX functionality would not work from IP.Content (because of cross-domain javascript restrictions), however work arounds for that have been added to IP.Content 2.3.0 (currently in alpha stages).

[kmf]

hmm... that is not good... i thought it was possible for the ipcontent-users that they just login into domainy, while the forumusers log into domainx.

If the domainsetting is set as "." or just empty, would that help then?

[bfarber]

IP.Content is not a fully complete and separate application.  It is an addon application for the IP.Board framework (at this time), so it runs within the IP.Board framework and not fully separate.

If you specify no domain in the cookie settings, cookies are set for the domain that was visited.  That *may* work, but I would caution that such an approach is unsupported (in that, I can't guarantee you won't run into miscellaneous issues having cookies being set for separate domains from one install).

[kmf]

is there a way to test that first? I think that if the cookies are seperated by domain, it should work in theory like I want to.
But 50 bucks to test that theory is a bit too much.

[ADKGamers]

That you for all that info Brandon.  And just for clarification, there would still be issues if you had 2 domains running the same database (even if you had 2 licenses and installs) due to the cookie issue correct?     Sorry for all the questions, just trying to see if there is a way to make it so that my users from one website don't have to sign up on a completely different website.

[TM4]

Plain simple but maybe helps:

if you just point the standalone domain to a subdomain for your ip board?

You´d have all content, logins and license under one hat and peoples still be able to type in the other domain.


You may thought of this already.. just wanted to help out

[bfarber]

kmf, on 03 February 2012 - 11:38 AM, said:

is there a way to test that first? I think that if the cookies are seperated by domain, it should work in theory like I want to.
But 50 bucks to test that theory is a bit too much.

I cannot think of a way to test this in advance, I'm afraid.  You're looking at doing some complicated setup that the software wasn't really designed to do.

ADKGamers, on 03 February 2012 - 06:18 PM, said:

That you for all that info Brandon.  And just for clarification, there would still be issues if you had 2 domains running the same database (even if you had 2 licenses and installs) due to the cookie issue correct? Sorry for all the questions, just trying to see if there is a way to make it so that my users from one website don't have to sign up on a completely different website.

Cookie issues will exist regardless of how many licenses you own I'm afraid.  If you use subdomains, as I mentioned above, cookies can be shared - they cannot be shared across two completely different domains.