XOOPS Multi Sites - Hacks - XOOPS News - XOOPS Web Application System

Re: XOOPS Multi Sites

M4d3L Published 01/22/2004 14:29 Just popping in Joined 11/18/2002 Comments 60

Re: XOOPS Multi Sites

romu Published 01/22/2004 14:33 Theme Designer Joined 12/05/2002 Comments 22

Nice and so interresting !
Any way for each domain to enter its spécific module ?

What i have in mind :
As a community portail, my XOOPS is now administrated by more than one admin (co-webmasters).

The deal to 'invite' them was to chare webspace and XOOPS system. Then i created a subdomain for each co-web pointing his homepage in a html pages content module (icontent).
Then I get
dom1.domain.net -> page1 (URL in XOOPS modules)
dom2.domain.net -> page2 (URL in XOOPS modules)
...

With you solution i could review my dns table (big problems with it) to point XOOPS root and use your script to point devoted pages...

Any solution ?
If yes, pease contact me privately.
Regards

Re: XOOPS Multi Sites

basby Published 01/22/2004 14:41 Not too shy to talk Joined 01/28/2003 Comments 109

Hi ldapguru,

Thank you for the work! I am looking for something like this so I tried it. It doesn't seem to work for me, however.

I first tried to use your solution for subdamians. I want to have http://www.domain.com and www2.domain.com to point to the same website but I want to keep the www2 in the url.

I created http://www.mainfile.php and www2.mainfile.php (copies of the original mainfile.com)
I changed mainfile.php to:

 if (!(isset($serverName)))  
{  
$serverName = $SERVER_NAME;  
$serverName = str_replace(".domain.nl","",$serverName);  
$serverName = str_replace(".domain.com","",$serverName);  
$serverName = str_replace(".domain.net","",$serverName);  
$serverName = str_replace(".domain.org","",$serverName);  
}  
if (!(empty($serverName)))  
{  
include($serverName.".mainfile.php");  
} 
?>

Now http://www.domain.com works but wwww2.domain.com does not work. It shows a blank page.

Am I doing something wrong? Any idea?

Thanks again!

Re: XOOPS Multi Sites

basby Published 01/22/2004 15:32 Updated 01/22/2004 15:34 Not too shy to talk Joined 01/28/2003 Comments 109

I have to corect myself: both http://www.domain.com and wwww2.domain.com worked but www2.domain.com changed into www.domain.com. It was not sticky.

In order to make it sticky, in www2.domain.com I had to make the following change:

change:

define('XOOPS_URL', 'http://www.domain.com');

into:

define('XOOPS_URL', 'http://www2.domain.com');

That made it all work!!!

Re: XOOPS Multi Sites

Ace_Armstrong Published 01/22/2004 16:08 Quite a regular Joined 01/09/2003 Comments 226

I'm curious as to what kind of load this puts on the server. Is it going to cause a noticable increase?

Re: XOOPS Multi Sites

DonXoop Published 01/22/2004 16:22 Joined 11/27/2003 Comments 1171

Slick. You would have to understand the various combinations and what you really want so there aren't any clashes. I can confirm that multiple sites can hit the same database for content. The real trick is using the same XOOPS base, *some* common data, and *some* unique data.

I'm confused by the stripping of the prefix and suffix to generate the filename. Wouldn't it be easier to just use the whole name as reported by the server?

http://www.mysite.com.mainfile.php

There are more combinations than the common http://www.site.com

site.ca for mine, so
site.ca.mainfile.php

Re: XOOPS Multi Sites

ldapguru Published 01/22/2004 17:22 Just popping in Joined 10/16/2002 Comments 13

BINGO !!! you got it right.

In order to make the URL's sticky the URL's should be entered in 'XOOPS_URL'

i dont see why it shouldnt work !!!

MultiSites with addon

coldbeer Published 01/22/2004 17:44 Just popping in Joined 12/24/2003 Comments 16

Cool!

But...

How could I maintain 2 domains with differente databases (for news, forums, etc) but using the same users table (for only one registering)?

Is it possible?

Re: XOOPS Multi Sites

ldapguru Published 01/22/2004 17:51 Updated 01/22/2004 17:56 Just popping in Joined 10/16/2002 Comments 13

Hi,

True, thats the real trick. If youre comfortable with the core XOOPS code you could do that too.

Quote:

The real trick is using the same XOOPS base, *some* common data, and *some* unique data.

Getting the *common data* and *unique data* stick with the various URL's can be tricky.

What you'd need to do is, first decide on the *common data* that needs to be used. lets assume that all users , themes, avtars and banners are *common data*

All modules are *unique data* elements,

well in mainfile.php or in uniquename.mainfile.php define your XOOPS_PREFIX as xoops_

in the database, all tables would have the xoops_ prefix.

The table structure for the modules can be modified with a independent prefix like site1_

replace site_ with the unique domain name or unique url to be safe...

lets asume that the module "newbb" needs to be *unique* for each URL.
well,

in the code for the module "newbb", you could modify the following lines containing

$sql = {some SELECT statement}

TO : Use the esame method as what is used to have unique mainfile.php included and include

include($serverName."sql.php");

and in EACH $serverName.sql.php file you could have something like :

 $sql = {some OTHER SELECT statement} 
OR 
$sql =  = 'SELECT xyz.* FROM '.$xoopsDB->uniqueprefix('tablename').......

Re: XOOPS Multi Sites

ldapguru Published 01/22/2004 17:53 Updated 01/22/2004 18:09 Just popping in Joined 10/16/2002 Comments 13

oops... please see prior post https://xoops.org/modules/news/article.php?storyid=1222&com_id=5607&com_rootid=5604&com_mode=thread&#comment5607

Re: XOOPS Multi Sites

coldbeer Published 01/22/2004 19:10 Just popping in Joined 12/24/2003 Comments 16

Well... not exactly what I have in mind:

I'm thinking to have the same modules, themes and core (to maintain updates), and diferent databases (or table prefix) for each domain. BUT having the same tables, just for: users, avatars, banners and smileys.

Do you think it is possible?

Re: XOOPS Multi Sites

ldapguru Published 01/22/2004 19:29 Just popping in Joined 10/16/2002 Comments 13

You'd need to do it with the SAME Database and different table prefixes...

having multiple databases makes each site UNIQUE. there would be no "common" element when you use different databases.

Re: XOOPS Multi Sites

coldbeer Published 01/22/2004 21:05 Just popping in Joined 12/24/2003 Comments 16

Well... so that's what I undestood but...

now that I have all that...

how could I to merge the users and avatars to be the same in those domains?

Re: XOOPS Multi Sites

mondarse Published 01/23/2004 9:02 Just popping in Joined 02/03/2003 Comments 96

Hi,
I'm a bit confused, I'm almost new with php and XOOPS code.

Can anybody resume what should I do to make
XOOPS Multi Sites (I mean with all corrections previously posted).

Thanks, MonDarSE

Re: XOOPS Multi Sites

Mithrandir Published 01/23/2004 9:12 XOOPS is my life! Joined 06/21/2003 Comments 6320

I don't think this is recommendable to rookie programmers until it has been ironed a bit more out.

Very nice work, though, I am following the progress with very much interest and look forward to it working seamlessly and easily

Keep up the good work

Re: XOOPS Multi Sites -> multi-themes?

taokrieger Published 01/23/2004 22:56 Just popping in Joined 10/29/2002 Comments 36

Perhaps this is simple - but how would I set it up so that each instance of XOOPS could have its own theme?

Re: XOOPS Multi Sites -> multi-themes?

coldbeer Published 01/24/2004 1:31 Just popping in Joined 12/24/2003 Comments 16

I think it's easy, taokrieger...

Your two XOOPS will see every theme you have in your /themes directory, now, you just need to select a diferent theme on each xoops. Obviously, they must have diferent names.

Re: XOOPS Multi Sites -> multi-themes?

taokrieger Published 01/24/2004 1:36 Just popping in Joined 10/29/2002 Comments 36

well, i've done the mainfile.php change but now all the sites use the same *common* database. I need to set it up so that each site uses a different theme. Currently, if I change the theme for one site, it changes for all of them.

Re: XOOPS Multi Sites -> multi-themes?

ldapguru Published 01/24/2004 17:28 Just popping in Joined 10/16/2002 Comments 13

You gotto be carefull here. If you have multiple themes, and if your users have personalized their user profile with a particular theme, you wouldnt want to corupt that.

You would need to change the table prefix in the DB for each module to be unique to the FQDN.

This obviously means that the entire codebase for XOOPS would need to be modified and hacked. So I'd advise against doing that right now, and simply await a new release of XOOPS that would enable you to do so.

i am parallelly working on stuff that may enable XOOPS to be a hellava lot felxible. I shall be presenting it t the core team and get their input on incorporating it into future releases. So hang in there. features that you have not dreamt of would positively be available soon...

Re: XOOPS Multi Sites

mvandam Published 01/25/2004 2:45 Quite a regular Joined 02/07/2003 Comments 253

coldbeer:

I don't think that will be possible at the moment (without doing some major hacking). XOOPS is currently designed to connect to one database and use ONE prefix throughout. So you can have two sites share the same database but they'll have to share ALL tables or NO tables.

Re: XOOPS Multi Sites

hoobamac Published 01/26/2004 20:11 Updated 01/27/2004 12:49 Just popping in Joined 05/28/2003 Comments 9

So from all of this... is it possible to have one main code base including modules ( for ease of updates and maintenance) and individual databases and themes/uploads directories for each site?

Is it possible that the main codebase is held in one location and the themes & uploads directory and database (and index and mainfile, I presume) is held under thier own domain?

This is starting to sound interesting...

Re: XOOPS Multi Sites

script_fu Published 02/06/2004 8:35 Friend of XOOPS Joined 12/27/2002 Comments 1494

Awesome thread people... Cant wait!

Re: XOOPS Multi Sites

dheltzel Published 02/06/2004 16:30 Not too shy to talk Joined 01/08/2003 Comments 164

If you want a slightly different approach, replace the defines of XOOPS_URL and XOOPS_DB_PREFIX in mainfile.php with this sample code:

define('XOOPS_URL', 'http://'.$_SERVER["HTTP_HOST"]);
if ($_SERVER["HTTP_HOST"] == "www.domain1.com") {
define('XOOPS_DB_PREFIX', 'd1');
} elseif ($_SERVER["HTTP_HOST"] == "www.domain2.com") {
define('XOOPS_DB_PREFIX', 'd2');
}

This assumes you are using the same database and db login credentials, but you could put those in this construct as well. IT also assume you are using Apache named virtual hosting, I don't know if it will work with other setups. If anyone needs help setting up the Apache virt hosting, let me know.

The advantage of this method is that there is still only 1 mainfile.php to manage.

Dennis

Re: XOOPS Multi Sites

fatman Published 02/06/2004 16:57 Friend of XOOPS Joined 12/13/2003 Comments 176

nice example! I never really thought about dynamically adjusting mainfile variables but I like it :)

So I'm assuming this will only work with the same hosting account.

If I want to manage each domain as its own hosting account, ie it's own bandwidth limits, size constrictions, email. Them this example wouldn't work. If im wrong, let me know.

The ideal situation for myself would be to run multiple XOOPS sites that shared the same core and same modules, but kept their own content, and their own cloned templates and I could still manage them (on the cpanel side) as thier own hosting account.

good stuff though, my mind is buzzing with thoughts of changing other things in mainfile on the fly.. happy xoopsing indeed

Re: XOOPS Multi Sites

Mikhail Published 02/06/2004 19:14 Just can't stay away Joined 01/19/2003 Comments 412

code for subdomains:

 if (!(isset($subdominio)))  
{  
$subdominio = $HTTP_HOST; 
$subdominio = str_replace("www.","",$subdominio);  
$subdominio = str_replace(".com","",$subdominio);  
$subdominio = str_replace(".net","",$subdominio);  
$subdominio = str_replace(".org","",$subdominio); 
}  
if (!(empty($subdominio)))  
{  
include($subdominio."mainfile.php"); 
} 
?>

Re: XOOPS Multi Sites

kevincam Published 02/13/2004 18:31 Updated 02/13/2004 18:32 Just popping in Joined 02/25/2003 Comments 14

Is this ability (common data + unique data/tables for modules that depends on some user selection) coming in the core, I'm thinking about doing this with my site. It would be nice if it gets built in the core, also the ability to collect more data than just the default. If it's coming how far along so I can decide whether or not to hack. Thanks. Also if you know if this has been done successfully already that would be helpful too.

Re: XOOPS Multi Sites

oddb0d Published 03/07/2004 19:47 Friend of XOOPS Joined 06/23/2003 Comments 56

Hmmm... I've been playing with this all day as I like the idea of only looking after source code in one place, plus I'd like to create an interface through my website so that sites can be set up automagically, e.g. for subdomains to start with.

Is it OK lots of instances using the same templates_c and cache directory?

A good move I guess would be to seperate these directories for each instance, plus extra theme and upload directories, but you can get in a mess with third party modules who may use their own folders for uploading stuff.

I found the first method was the best - although I've named mine http://www.mysite1.com.mainfile.php, etc. as someone else suggested - easier to automate.

Guess my next task is to work out a standard SQL file for a XOOPS install so I can upload that instead of going through install each time.

Thanks for giving us a good start point!

oddb0d

Re: XOOPS Multi Sites - how I did it in six simple steps...

oddb0d Published 03/07/2004 22:49 Updated 03/07/2004 23:09 Friend of XOOPS Joined 06/23/2003 Comments 56

I've now got multiple instances with separate cache, templates_c, themes and uploads directories. All have own mainfile.php so you can use different databases if you wish (or same one with diff prefixes... eurgh!).

For those interested, this is how I've hacked it so far. Needless to say this is unsupported so don't blame me or anyone else for your inquisitiveness if it all goes wrong

1. Create a directory for XOOPS code

I've put an install of XOOPS in /home/xoops/src

I've changed my httpd.conf so each document root and script alias point to my generic XOOPS install. My logs go to instance-specific directories so you can keep logs for each instance separate. For example:

ServerName http://www.yoursite.com
ServerAdmin you@yoursite.com
DocumentRoot /home/xoops/src
ScriptAlias /cgi-bin/ /home/xoops/src/cgi-bin
ErrorLog /home/username/www/www.yoursite.com/logs/error.log
CustomLog /home/username/www/www.yoursite.com/logs/access.log common

2. Create some instance-specific directories

Make a directory in your XOOPS_ROOT_PATH for the instance, e.g.

cd /home/xoops/src/

mkdir http://www.mysite.com

Now copy the instance-specific uploads, themes, templates_c and cache directories into your newly created http://www.mysite.com directory.

3. Copy original mainfile.php

To make an instance-specific mainfile.php, copy the original and prefix with the URL of the site, e.g. http://www.yoursite.com.mainfile.php

4. Modify http://www.yoursite.com.mainfile.php

After the definition of XOOPS_ROOT_PATH, add the following:

define('XOOPS_LOCAL_PATH',XOOPS_ROOT_PATH.'/'.$_SERVER["HTTP_HOST"]);

After the definition of XOOPS_URL, add the following:

define('XOOPS_LOCAL_URL',XOOPS_URL.'/'.$_SERVER["HTTP_HOST"]);

5. Modify mainfile.php

mainfile.php will now only have the following line:

include($_SERVER["HTTP_HOST"].".mainfile.php");

6. Modify include/common.php

So the instance-specific directories and locations can be found, you need to change the following definitions to how they are here:

define("XOOPS_CACHE_PATH",XOOPS_LOCAL_PATH."/cache");
define("XOOPS_UPLOAD_PATH",XOOPS_LOCAL_PATH."/uploads");
define("XOOPS_THEME_PATH",XOOPS_LOCAL_PATH."/themes");
define("XOOPS_COMPILE_PATH",XOOPS_LOCAL_PATH."/templates_c");
define("XOOPS_THEME_URL",XOOPS_LOCAL_URL."/themes");
define("XOOPS_UPLOAD_URL",XOOPS_LOCAL_URL."/uploads");

THAT'S IT!

I could do with some advice on security though - as the local site files are all under the main root web directory there may be some issues there, and as I'm not a sysadmin expert I'm not sure how to fix this (if there is a prob!)

HTH

oddb0d

I've done exactly what you said, but have a blank page

antah Published 03/12/2004 13:21 Just popping in Joined 01/12/2003 Comments 29

I've done exactly what you said, but have a blank page.

Maybe you suggest me smth. I've checked $SERVER_NAME param - it's working and giving me domain.com.

i edited

include($serverName."mailfile.php");

string to

include($serverName."mainfile.php");

Maybe I have to change some rights? like 755 or 777?

Thnx for helping

Re: I've done exactly what you said, but have a blank p

ullone Published 05/05/2004 18:14 Friend of XOOPS Joined 04/24/2003 Comments 49

Multi Server Installations. ...
I need to use different installations of Xoops, each one using a different server. Each Installation of XOOPS stand on a different server . The server for the first installation is different than the others. Each XOOPS installation have a separate Server. My problem is to allow a UNIQUE User Sign Up for ALL My XOOPS Installations. I hate that every User Make a Sign Up separately to each Server. I prefer that the registration is Unique. I need to Save the User registration for ALL different Server. ONE and ONLY. When a Member Sign Up for an installation i would like that this registration is Saver forever for all my XOOPS portals. I see this : https://xoops.org/modules/news/article.php?storyid=1413 https://xoops.org/modules/newbb/viewtopic.php?topic_id=19384&forum=27 But this module is only good if the server is the same. In my case i have different server for different installations. Is it possible to save the result of the register.php (the member sign up for a single XOOPS Installations) in ALL DataBases of the other installations of XOOPS ? Is it possible to Save Username and Password of the registration of the new User on the other XOOPS Installations ?

almost there!

adrock Published 02/09/2005 17:42 Quite a regular Joined 12/07/2004 Comments 291

Quote:

In my case i have different server for different installations. Is it possible to save the result of the register.php (the member sign up for a single XOOPS Installations) in ALL DataBases of the other installations of XOOPS ? Is it possible to Save Username and Password of the registration of the new User on the other XOOPS Installations ?

This is the direction I have been trying to go in for a while. I help develope/maintain sites for a large 'web ring' and the other site admins and I hate the fact that we have to have the visitors create an account on every site in the ring.

I'm looking at seeing if we can have the result of register.php, or the activation link e-mail that is generated, provide 2 links;
1. to activate the user for the site you went to, and
2. a link to activate the user in all or only selected sites in the ring.

Eventually I see it as a seperate registration module entirely....and of course you would need to know the localhost of each database, and have a DBA with appropriate access on each localhost/domain location. Good for one owner of many sites....has issues with many owners of many sites.

Re: almost there!

SkYYDoGG13 Published 11/01/2005 4:37 Just popping in Joined 01/08/2005 Comments 5

Looking to do the same as adrock.
Multiple sites, same server, virtual environment, using only one user name / password for all.

Different databases per site are fine.
I just don't want my users to have to register for each site.

The objective is one "portal site" then about 16 "sub" sites. The "sub" sites will all have their own content and will be run by their own "webmaster".

Any more done with this before I start the hacking?

Re: almost there!

adrock Published 12/23/2005 21:12 Quite a regular Joined 12/07/2004 Comments 291

hehe...hack away....

this place has been dead for a while!

Re: almost there!

fungus Published 05/06/2006 16:05 Just popping in Joined 10/15/2002 Comments 72

Yep, I have noticed work seems to have dried up, just when i need a module to allow 1 signup allows access to all sites, nothing too flash...

Anyone know where I can get it from if it is available????

Sharing User tables...

krewl Published 10/27/2006 3:43 Just popping in Joined 03/14/2006 Comments 39

Any progress? Multisites or multix doesn't work for a user to register once for 2 sites. (Same localhost, 2 different databases).

Stats
Goal:	$100.00
Due Date:	Nov 30
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Hacks: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

MultiSites with addon

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites -> multi-themes?

Re: XOOPS Multi Sites -> multi-themes?

Re: XOOPS Multi Sites -> multi-themes?

Re: XOOPS Multi Sites -> multi-themes?

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites

Re: XOOPS Multi Sites - how I did it in six simple steps...

I've done exactly what you said, but have a blank page

Re: I've done exactly what you said, but have a blank p

almost there!

Re: almost there!

Re: almost there!

Re: almost there!

Sharing User tables...

Login

Search

Recent Comments

Re: New Admin Theme for XOOPS (Beta)

Sanford Pharmacy: Exceptional Pharmacy Services Tailored to You

Re: New Admin Theme for XOOPS (Beta)

Re: XOOPS 2.5.12 Beta-2 available for Testing

Re: XOOPS 2.5.12 Beta-2 available for Testing

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}

Archives

News archives