Dreamweaver will not refresh remote images in the design view. Ever. No amount of refreshing, right clicking, select sourcing, size resetting will fix it - I simply have to quit and restart Dreamweaver. As far as I am aware, this problem has existed in several if not all versions - I have always restarted the program to refresh remote images, and that was fine for making the odd HTML email, but now my day-to-day work has changed and its becoming a real problem.
The only remote images I have seen DW have problems with is those that have spaces in their pathnames. And I work with remote images all day, especially when testing other people's layouts on this forum. Can you give a specific example of an image that won't refresh for you?
Hi Murray - Thanks very much for your reply. Can you tell me which button or command you use to refresh your remote images? I don't want to sound difficult, but this is a well established bug in DW which I have personally experienced in versions 8 (MM) through to CS5.5 on all available platforms - so in the absolutely nicest way possible, I doubt very much that you are able refresh edited/replaced remote images without restarting the application. If so, any chance of a video? I have never in all my years seen it work - a video of a working install may help diagnose whats going wrong for the rest of us.
Re. a specific example - I can't really give you a URL of a live file that won't refresh - too sensitive I'm afraid. However, I never use spaces in my paths, only hyphens or underscores - so that is not the issue. The bug rears its head with all file types, with any file/path names, on every server I have ever used even with explicit firewall passthroughs.
Example URL which fails to refresh: http://www.myclient.com/emails/xxxxx2012/main.jpg
Thanks again for your reply
1 person found this helpful
I had never noticed this before, I guess I never make edits to server copies, I always make a local version first, then upload (even on eBay). I found at least a partial work around in CS4/Windows 7 anyway...
Under View > Live View Options > HTTP Request Settings...
I clicked the + and set the name as pic and the value as the http address of my image. It shows in Live View with the updated image now. After closing the file window (not DW itself) and re-opening it, it also appears correctly in Design view for me.
1 person found this helpful
I have always restarted the program to refresh remote images, and that was fine for making the odd HTML email, but now my day-to-day work has changed and its becoming a real problem.
I am not entirely sure I understand the problem but from the quote above I gather you are building your HTML email locally (now websites maybe?) and including images that are stored on a web server and/or your email clients server. I do the same work and although I also do not experience a "refresh" as you put it, there is a simple way around it.
My understanding of design view is to help you layout the design and add what you need without a constant live connection - this is where Live View comes in. If you turn on Live View, the connection is re-established and it renders the updated image from the server. Sometimes if you are updating an image on a server with the exact same name, your browser cache or Dreamweavers cache doesn't recognise the change. If this is the case, you need to clear out the temp folder where DW stores the downloaded image samples. In OSX, you can normally find it here:
User > Library > Application Support > Adobe > Dreamweaver CS5.5 > en_US > Configuration > Temp
Another way around it which I sometimes use is to upload the image with a new filename and link to the new name - this will force DW to pull down the new sample.
If you're building a web site, and have the site defined, use the dropdown from your site module and "recreate site cache".
Hi Jon - thanks for your reply. I am at home now, so I will give the workaround a go in the morning. Does seem quite long winded though - I assume I would have to add an http request setting for each individual image? Some of the files in question have over a hundred images, so probably not workable in this particular case.
You are totally correct that in most circumstances, it is normal to simply use relative paths to local files, then upload - simple. However with HTML emails for instance where the paths must be absolute, I would have to do a find/replace on all the src parameters of the image tags prior to each and every upload. Sometimes hundreds of uploads are required before a project is signed off, so again it would seem simply restarting the application is the easiest method.
I just can't understand why a bug which was reported on here about 5 years ago still makes its way into each and every update of commercial software. I know that several bug reports have been submitted; Are these simply ignored? Or is the process of refreshing remote files more difficult than I imagine?
Thanks again for your help guys
1 person found this helpful
It may just be that there aren't many people conducting their design using the same steps you are so the number of reports made doesn't warrant the development team's full attention?
Either way, talking about it here doesn't necessarily mean anyone from the dev department will ever see it since this is essentially a user to user forum.
Definitely report it here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
and get anyone else who has the problem to do the same.
1 person found this helpful
I think I see what you are describing. If I have a page like this -
<img src="http://www.gws-sandbox.com/_img/combo-copy.jpg" width="800" height="307">
Once I bring that up in DW's Design view, even though I have made a change to that image and uploaded the new changed image, DW's Design view does not reflect that change. Is that it?
I would file a wish by filling out the form here - these go directly to the dev team....
Hi Rick, thanks for your reply. I was not aware the design view was intended to not have a live connection. If that were true, surely it would negate the need for a 'refresh design view' command, as all local changes appear to refresh automatically anyway. Also while the deign view is obviously able to display remote content, what would be the point of restricting refreshes? Surely the live and design views being out of sync with eachother is basically a problem regardless of the cause?
I appreciate what you are saying about uploading with a new filename, but the fact is, as with all the workarounds I have found, its still far quicker to simply restart the application each time I need a refresh.
I will have a go at defining a site and refreshing the site cache tomorrow - if my memory serves me correctly, it still only refreshes local files, but I can't be sure without checking. I only tend to use the site manager if I am doing a find/replace on a large site. Otherwise i have never found any real use for it. Perhaps I have been a little naive
Thanks everyone, I will let you know the results in the morning!
Hi Murray, Yes that pretty much sums it up. Although in all fairness to DW, I would never expect it to automatically update anything but local files. I would however expect the 'refresh design view' command to do just that.
I will request it as a feature rather than report it as a bug, although I know both have been done several times over the past 5 years. Hardly inspires confidence in the dev team
Many thanks for your help, as I said I will report back after some testing with the site manager.
Hi Jon, you are right - I don't see everybody having the same workflow as myself. To be honest I only actually use DW for previewing style sheets and building tables for HTML emails, I do all my coding by hand. Perhaps with a particular view to the site manager, I am not using DW in the way it was intended. And perhaps there are other applications which would complement my workflow better. However fixing/adding this simple function would change all that.
Thanks again everyone, i didn't imagine I would get much of a response considering the issue seems to have been flogged to death, but everyone is keen to help, Good times!
Just bear in mind how many of these the dev team gets, and how they might deal with prioritizing them. In my mind, while this issue is clearly important to you, I feel as if there are MUCH MUCH more important things to deal with in DW, and I think it's likely that situation won't change much over the coming years.... It's just the reality of product development. Everything has a ROI that is considered.
Good morning everyone I have double checked and can confirm that recreating the site cache does not refresh remote images on a fully defined site; neither does synchronising, or any other functions I can find. That is with all remote settings defined and working correctly. One thing I must say is how the Site Manager and FTP are very slow, exactly the same as I remember them being years ago; I certainly won't be using them again any time soon.
Murray, thanks again for your response, but I entirely disagree with your sentiments re. the importance of this bug/feature. I appreciate the volume of bug reports and feature requests the dev team must receive; but the number of people having to restart DW to achieve a function which should be included in a button or menu item is frankly shocking in my opinion. If I were solely creating HTML emails for my day-to-day work in the long term, this would more than likely be enough reason to stop using DW altogether.
The idea of plotting bugs against ROI before deciding whether to fix them or not boils my blood a little if I'm honest. I really hope the dev team don't take that attitude, else we're not likely to see any improvemement in the near future.
Thanks everyone for your time and your help. I'm disappointed there is no efficient workaround for this, and have been left with less confidence in the software than when I started. Rather than chase my own tail trying to get the dev team to acknowlege the bug, I feel my time may be better spent finding more capable/suitable software for editing HTML files with remote assets; a colleague has suggested Eclipse SDK, although I have not used it myself.