hi,

I resolved my precedent problem (see older topics...) so, another one arrived !

I'm working on local. I created blocks, modules....With local connexion (http://127.0.0.1/mysite), it's ok, it's fine
But connecting with another computer, using my IP (http://80.14...../mysite), I obtain only texts !! There's no CSS style, neither pictures !!
so, I edited the distant page's source code, and I saw that the css link is defined with "http://127.0.0.1/mysite/themes/default/style.css" !!!
that's sure, it can't works with distant connexion...Then, I edited may local mainfile.php and I found this :

// XOOPS Virtual Path (URL)
// Virtual path to your main XOOPS directory WITHOUT trailing slash
define('XOOPS_URL', 'http://127.0.0.1/xoops');

okay, that's the problem ! my virtual url is 127.0.0.1, it fails with distant connexion...my question is :

IS IT POSSIBLE TO DEFINE THE 'Xoop Virtual Path' WITH A VARIABLE LIKE $variable='my real ip'; ???
$_SERVER['REMOTE_ADDR'] is used to know the user IP, but how obtaining the server IP ???

Because, my french internet provider ("wanadoo") disconnect every 24h and my IP changes everyday !!!
I see others solutions :
- send mails to my friends every days...(and others ?? they can't access my site ?)
- using a net service like no-ip.info, that serves as a "gate" between my real IP and a "false" domain's name (http://mysite.no-ip.com) but it uses an local executable to inform the no-ip server... about security, hum ? I don't know exactly what these exe send !!!

@mithril

That is a DNS/IP issue. Easy to fix. I suggest not using 127.0.0.1 even from the local machine. Use the actual IP address so it works from any internal machine.

You don't say if this machine is behind a firewall/router. No problem with a dynamic IP if you keep a DNS server updated (automated) with the current IP.

If you need access from inside and outside the network you need to configure XOOPS for the hostname that the external users will use. Then you want an internal DNS or hosts file set to resolve to the internal IP so that internal users still work.

There are other ways that have been discussed here including multi-hostname / single-server hacks, virtual servers, router tricks, etc. I prefer a solution with no code hacks. Do a search, one thread is here.