Yo all. I recently got a broadband internet connection, and have decided to set up a web server now. I recently learned of various portals, and XOOPS came highly recomended. I downloaded it, and installed it, and to my dismay, only people on my network, or people on the internet could see Xoops, not both at the same time.
To explain: I started out with a regualar installation, thinking that inputting my Web Server's LAN IP address would work fine, as it did in HTML. Alas, I was wrong. It turned out that only users on my LAN could see Xoops, while internet users found broken links and images.
This scenario simple reversed itself once I re-installed Xoops, and put in my Internet Web Server address only to find that myself and my LAN machines were unable to access the XOOPS main page, and internet users were able to see it perfectly. Is there a back door to this? I've tried opening the index.php file on the server itself, to no avail. http://localhost:1337/ doesn't work, either. I'm wondering if there is a way to make XOOPS work with two IP addresses. Is this possible? If so, it would be greatly appritiated. XOOPS seems to be an excellent portal, if only both the internet and my LAN could see it..

mainfile.php in the XOOPS root is what defines your websites location. XOOPS needs to know what IP or domain name its running under for everything to work.

Everyone accessing the site should use the same IP. Internal users on your LAN should use the external IP for your web server, not the internal address.

Also make sure your firewall/router or which every device is managing your internet connection is set up to forward HTTP or port 80 requests to your web server.

HTH

I don't know if this will work, but wouldn't it be possible to do a little processing in mainfile.php to look at the browser's IP and if it is a 10.x.x.x or 192.168.x.x then it should use the internal address/IP and if not, it should use the global URL/IP?

alternatively you need to setup some intermediary naming service (Not a networking expert myself) to name the webserver with the global URL also on the local network. Something to do with hosts or something... I know it's been discussed somewhere else on these forums.

I think you should not add any information about your host in XOOPS_URL variable in mainfile.php (no IP address nor protocol, just /xyz or simply /) You should use semi-relative URL instead and apply the small hack described here https://xoops.org/modules/newbb/viewtopic.php?topic_id=13171&forum=21#forumpost69343
One day it will be incorporated in the core... I should document that in the XOOPS wiki but I am too busy (not too lazy, trust me )

This is the only way to make a single XOOPS site available from various different URL's.

Please rad carefully the hack wrap-up and I am sure you will understand.

Hope this will help.

Benoit

Hmm.. Thanks. Hopefully your hack will provide me with the workaround that I need.
Awesome work!

May I ask you to keep us informed of your problem resolution ? It would be nice. Thank you.

Benoit

As much as I would like to spend the time troubleshooting code, alas, I cannot. I applied the patches you recomended, and they did not work. I got the same error as usual. Because of this stumbling block, I'm going to go ahead and use CGP-Nuke for now until XOOPS works properly with multiple URL's. I am not a coder, for one, and two, I lack the time to sit down and work on these things. I will be watching from the sidelines, though. Waiting for an even cooler XOOPS release.
Keep up the good work, all. It looks great so far, but I'm not up to snuff yet.

This is a bad news... If you are interested I could send you by mail (just send me a PM - private message with your email) a copy of my 2.0.6 version correctly patched (it works on 3 production sites accessed by 4 different URL's). I feel sad that you forget about XOOPS because of that...

Best regards,

Benoit