08-08-2011, 11:19 PM
I know this was addressed in the sticky - that the URL needs to be adjusted in order for the images to display properly. That did fix the problem, but....
I believe the programmers should really address this. The code should use relative pathing based on the install.
I'm not sure why others here are experiencing the problem but here's my situation:
I have this script auto-installing at sign-up for a reseller accounts. Works great. Only problem is, until the dns servers are updated, the server ip address is given to the customer to access their site. So, until this happens, they would access like http://123.456.789.123/~mydomain/tht. TheHostingTool is accessible, as you would expect, but the images do not display.
Seriously, most other apps are coded using relative pathing. Try it. You'll like it. *wink*
I believe the programmers should really address this. The code should use relative pathing based on the install.
I'm not sure why others here are experiencing the problem but here's my situation:
I have this script auto-installing at sign-up for a reseller accounts. Works great. Only problem is, until the dns servers are updated, the server ip address is given to the customer to access their site. So, until this happens, they would access like http://123.456.789.123/~mydomain/tht. TheHostingTool is accessible, as you would expect, but the images do not display.
Seriously, most other apps are coded using relative pathing. Try it. You'll like it. *wink*