Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By zoon_unit on
I've got a problem that's driving me crazy. I decided to try this forum because it seems that this would be a universal problem for developers moving their site from a development environment to the live web.
When I upload an inline image using the img_assist module, it stores the href link to the image as a full http path.
The problem with this is that I've uploaded a ton of images on my development server. Now, when I move my drupal site to the internet, all the image hrefs read as follows:
href="http://localhost/drupalfolder/files/foo.jpg"
The problem with many ISP's is that localhost is inoperable, or as in the case of Dreamhost (my ISP) all domains are stored in subfolders off the user's root. So when I type in "mydomain.com" it points directly to the subfolder "mydomain.com" in my user folder, which is now the home directory as far as Drupal is concerned.
Shouldn't img_assist use relative urls? Shouldn't the image href="/files/foo.jpg" ? Is there a way to set this behavior?
How do others handle the transfer of inline images from a development site to a live site without breaking all the links?
Comments
caching?
I just came across a symptom like this. Using img_assist to attach images on the development server, and then finding them with a localhost absolute path when I dumped and restored the database. The solution was to delete the filter cache entries. That can be done with the SQL delete from cache_filter;