I am with a host who no longer allows temp URL access - or if it is allowed it is for very few days at a time.

I am a web designer. I create sites. Hosting is secondary to what I do. When I move a site from one host to my reseller account, I re-design the site as well. I was brought in to my position to do this. We have around 6 sites hosted elsewhere, that I want to move to my reseller account, and as such, I am needing to re-design them as well.

This is the problem:
I create a new navigation structure, completely re-do the code, etc. for the site. To do this, I need to have a working location to access (m.y.i.p/~site was ideal). The site is not accessed outside of myself. I work on the temp site as my dev area, then DNS point to the location when complete. This can take months, as I am juggling multiple sites on top of my other duties here at work.

I now have no way to have a dev area on the server to work on.

How can I set up a dev are for the redesigns on a server that doesn't allow temp URLs? Dedicated IPs for each site is NOT an option. I am unable to do local development, either. On server is a requirement.

Thanks

You could modify your hosts file to view the site under the domain on the new server without having to actually update the DNS of the domain.

This way you would see the site on the new server where as everybody else would still see it on the old server. That's probably the best way to go about doing it.

Thanks Michael. How could I mod the hosts file if I can point to a location or the temp area? I would need an IP location correct? No way to get it that I know of, since temp URL is off. Am I wrong?

You would just need to provide the IP that your account is on and then the domain you wish to access it on in the hosts file.

The method is the same no matter your OS but the location of the hosts file varies. http://www.fpweb.net/support/managed-hosting/hostfile-editing-support.asp should give you a decent idea of where to find the files.

What you would want to add is:
The.IP.Address.Here thedomainhere.com
The.IP.Address.Here www.thedomainhere.com

At least that is how I do it - if you add the one without the other then the one without the www will work but not the other way around etc...

you can host the website on your own computer for a while.
on localhost

you can host the website on your own computer for a while.
on localhost

Another decent option for development but you would want to make sure that you have all of the same plugins/modules on your local PC as the server has and that you don't have any the server doesn't so that you don't run into an issue when you try to go live :)

Actually, can't do the host file. Client needs to pull it up to approve. Can't do that with the HOST file way around it. Can't do local on this laptop. Locked down here at work.

Is it standard to disallow temp urls? There is no easy way of handling this - and there should be.

Actually, can't do the host file. Client needs to pull it up to approve. Can't do that with the HOST file way around it. Can't do local on this laptop. Locked down here at work.

Is it standard to disallow temp urls? There is no easy way of handling this - and there should be.

Well if the site isn't already live just point a domain to it and go live and then restrict access to specific IPs via .htaccess - or you could put it live in a sub-domain for testing and restrict it by IP or by username/password.

The reason many hosts prevent temporary URL usage is because the bandwidth used in this way counts against the server as a whole but not against the particular account being accessed meaning you could host all of your images/videos/audio via the temp URL and the site itself via the full URL and have minimal bandwidth reported on your account.

I wouldn't suggest anybody try doing what I just mentioned however or you could very quickly find your account suspended/terminated with some fees depending on the Terms of Service and how much you used - this is something that can be detected/accounted for but it's a manual process.

That's the problem. All the sites I work on are live. I am redesigning them, but they reside on another host.

I was asked, so Innohosting is my host who has disallowed Temporary URLs. I understand why hosts don't like them. But I use mine STRICTLY for dev. NO linking to anything from live to the dev area. Everything stays within. This kills my ability to work on a site. Don't understand the blanket turn-off, instead of shutting off for those abusing it.

That's the problem. All the sites I work on are live. I am redesigning them, but they reside on another host.So as I suggested - create a subdomain and lock it via username/password and/or IP address restrictions and work on the server there.

I was asked, so Innohosting is my host who has disallowed Temporary URLs. I understand why hosts don't like them. But I use mine STRICTLY for dev. NO linking to anything from live to the dev area. Everything stays within. This kills my ability to work on a site. Don't understand the blanket turn-off, instead of shutting off for those abusing it.I'm not aware of a way to enable/disable this on a per-account basis. Many hosts allow temporary URLs but even then many times PHP doesn't run properly under a temporary URL due to username/permission issues.

Your best bet is to do the work on the live server but in a protected subdirectory.

SWEET! Works perfectly. Thanks Mike. I really like Innohosting...will be sticking with them.

SWEET! Works perfectly. Thanks Mike. I really like Innohosting...will be sticking with them.

Glad I could help :)