1
sceilig
Multisites Module/Hack
  • 2006/3/1 11:20

  • sceilig

  • Just popping in

  • Posts: 53

  • Since: 2006/3/1 1


I have searched through the forum and Google for a Xoop module that would manage multisites/subsites but didnt come up with much.
I did see a modules posting by Mithrandir (Jan Pedersen) but the downloaded tar file containing the module is corrupt.
http://xoops.web-udvikling.dk/modules/wfdownloads/viewcat.php?cid=1

Does anyone happen to have a valid copy of the .tar file for this module, or perhaps some direction as to where I might find more info/module for a XOOPS multisite solution.

thanks!

2
davidl2
Re: Multisites Module/Hack
  • 2006/3/1 11:27

  • davidl2

  • XOOPS is my life!

  • Posts: 4843

  • Since: 2003/5/26


Which version of XOOPS do you need this for?

3
stefan88
Re: Multisites Module/Hack
  • 2006/3/1 13:32

  • stefan88

  • Community Support Member

  • Posts: 1086

  • Since: 2004/9/20


I downloaded it from your link and the file was ok. Try to download it again.

I also have somewhere 2.0.9.2 hack from mithh and 2.0.13.2 from codeplus ...
..

4
nbecu
Re: Multisites Module/Hack
  • 2006/3/1 17:20

  • nbecu

  • Just popping in

  • Posts: 11

  • Since: 2005/9/16


Hi stefan88,
I'm interested in the 2.0.13.2 version of this hack.
Could you be so kind to post it here or send it to me by email.

Thanks

5
davidl2
Re: Multisites Module/Hack
  • 2006/3/1 17:23

  • davidl2

  • XOOPS is my life!

  • Posts: 4843

  • Since: 2003/5/26



6
nbecu
Re: Multisites Module/Hack
  • 2006/3/2 15:22

  • nbecu

  • Just popping in

  • Posts: 11

  • Since: 2005/9/16


Thanks for the link.
I've installed the module with no problem.

However, I just found out that, as far as I understood, I need to install a second time XOOPS and its modules on the URL of my second site.

This was not what I was looking for actually. I thought I could use the same kernel/xoops class/module files etc... and create a kind of "virtual" second site in which I could customize in a different way (than my main site) the modules that I wanted to show, the welcome page, the theme etc...

So unless I missed something I think this multisite module/hack is not what I need :(

7
sceilig
Re: Multisites Module/Hack
  • 2006/3/3 8:26

  • sceilig

  • Just popping in

  • Posts: 53

  • Since: 2006/3/1 1


It seems the problem I had with extracting the multisites module file was my own. Usually I tar -xzvf filename.tar.gz but that didnt gave me errors on Mithrandir's file. Instead I did a gunzip and tar -xvf and it extracted fine. Thanks for the help on that.

nbecu, the whole purpose of the multisite module was to have one source code driving multiple websites.

Here is Mithrandir's explanation:

Quote:

You first have to understand that basics of how this hack works.

It works by running ALL sites from the SAME code. For example, I have http://www.bfsb.dk pointing to the same physical location as xoops.web-udvikling.dk, so it is the SAME index.php that is accessed.

You can do it with subfolders on Apache with the ALIAS directive in the apache's httpd.conf file, making an alias for the (non-existing) subfolder to point to the root.

In your example, you would

1) install XOOPS on 127.0.0.1
2) install site administration on this site.
3) Create a new site in the site administration module, with the URL http://127.0.0.1/humor and the prefix zxcvb
4) Create an ALIAS in your apache's httpd.conf file
5) Restart apache
6) access 127.0.0.1/humor and start configuring this site. The first thing I do is to change the name of the site in the site's normal XOOPS general preferences and then I uninstall the Site admin module from this site to avoid confusion

To install a module and share it with other sites do this:
1) Install module on all the sites that should have the module - include the "base" site (127.0.0.1/ in your case)
2) Edit each site in the "base" site's Site Administration module to share the new module's tables

To uninstall a shared module from a subsite do this:
1) Edit the subsite in the "base" site's Site Administration and set the module's tables to not be shared anymore
2) Uninstall the module on the subsite

Especially the uninstallation procedure can cause problems if you don't un-share the tables first (since the tables will then be removed by the uninstallation - but all the other subsites will still have references to the module in their database tables)

Login

Who's Online

305 user(s) are online (263 user(s) are browsing Support Forums)


Members: 0


Guests: 305


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits