Hi All, Need some help with what I think is the $url model object. Let me see if I can describe my problem in the right manner (forgive me if my terminology is a bit off, I'm still learning all of this stuff).
I currently have Roller 3.1 running on Windows XP and Tomcat 5.5.23. I am currently running a test run of Roller as a team blogging application at my work. Currently team members in our American offices (network) can access the app via a web browser by typing in http://nameofmymachine/roller/ where "nameofmymachine" is the short name of my machine (not fully qualified). All the links in the application, which seem make use the $url model object, direct the user to some subdirectory of this. The problem I'm running into is that we have a team member that works out of our China office and cannot access the site this way. He has to enter the fully qualified name of my machine in order to access it because he is on a different company network, for example, http://fullyqualifiednameofmymachine/roller/ . This would be fine, but if he clicks on any links in the app, it just reverts back to linking to a subdirectory of the short name of my machine (not fully qualified), therefore not finding the page. So basically, since he is on a different network, the DNS looking up "nameofmymachine" does not recognize it unless it is the fullyqualified name of my machine. We can work around this by having him assign the IP address of my machine to "nameofmymachine" in his Windows host file, but I'd rather not do this. So I'm wondering if it is the $url model that is always returning the short name of my machine whenever a link is selected? What I would like to happen is whenever anyone selects a link in the app, it links to http://fullyqualifiednameofmymachine/roller/something . Is this possible? Do I need to be building from source and changing the $url model object code? Thanks. -Jeff Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
