CMS Made Simple Forums

I am trying to edit our company site inside of a firewall on the server that is hosting the site. When I, for instance, try to access the login admin screen, I have to type in www.mentalhealthcareofcullman.com/home/login.php adding the actual page address each time. When i proceed to log in, I can't get it to roll over to the main admin page. Same thing for the actual site. I'm thinking maybe it has something to do with the addresses being hard coded? Can I make the site have a dynamic addressing system? or is there another fix i am not aware of. Thanks. - Aaron

Are all paths in config.php set correctly?
It is possible to use relative URL's (or PHP to determine the correct URL) in config.php.

Regards,
D

How would I go about making all urls relative? Thanks.

You can use PHP variables like _SERVER['HTTP_HOST'] in config.php to set the $config(***_url) values correctly if they should change in some situations.
It's not completely clear to me what problems you're experiencing and what the difference is between "normal" access and access from the server in your case (what do you mean by "have to ... add the actual page address each time"?).

Regards,
D

Alright, let me come at this from a different angle. I have a user who is trying to edit cmsmadesimple from a machine that is on the same network at the server that is hosting the site. As a result, when he navigates to www.mentalhealthcareofcullman.com/home he gets a page with no css styling and when he clicks a link to go to another page in the site he gets the a "not found" page. The network technican for his facility seems to think that this is occuring because the addresses in the site are hard coded and not dynamically set. The user is, in essence, attempting to connect to the server on his network by going out through the firewall to the web and then back in through the firewall to the sever. Thanks.

- Aaron

This is the message I received from their network tech:

When he tries to access cms locally (behind the firewall) everything on the machine returns paths to the external address. In other words the outside world views him at www.abc.com while behind the firewall he has to resolve it as http://192.168.1.100 … when he accesses it from behind the firewall the css and images are all firing back a hard coded address of www.abc.com/ehatever  instead of allowing apache to resolve them to http://192.168.1.100/whatever  …

Shouldn't your inside network resolve host.abc.com to 192.168.1.100 ?
Pierre M.