When creating my website, with some randomness, I can place an image, and it looks fine in WSIWYG VSD, but when I preview, the image will change. An example of this is on the following page (which I'll leave unfixed for a couple of days). At the bottom right of the page, there is supposed to be a picture of two kilns, but it copied a picture of the logo.
What is apparently happening here is that when VSD compiles into html, it renames each image file as IMG_##. In this case, the missing image of the kiln came from an old version of my website, and I pulled it from the files folder of the prior website directory. It has the name in the old directory of IMG_82, which was apparently already a file name used by VSD for one of the logo images on one of the pages. The conflicting name is apparently never resolved. Sometimes a new image will change an image on another page that already exists, as if the new file simply overwrites the old file. In this case, adding the new image never makes it to the file folder, and the old IMG_82 is displayed instead of the image that I created with VSD.
This scenario has happened to me periodically, particularly when I used to reduce the size of the image with a simple editor that wrote out files as IMG_###.
There is an obvious workaround of renaming the image to a different file name, which is what I do, but I think there is a defect in the software here.
In this case, it seems limited to dealing with file names with the convention of IMG_##. I've played with it more this morning, and can reliably reproduce, so I'm thinking I'll avoid that file name, and open a support ticket.
I did just look at your links. Wow! I'm having another problem with favicons that I would appreciate your advice with. I'll describe that in a different forum post.
And renaming the files does work. It just takes time. I think they'll probably fix this in the next release, it seems relatively easy to check for a file name conflict and resolve it as the images are placed into the files directory.
So I opened a support ticket. The result from support is that you cannot use images from different directories. In other words, they all must come out of the same folder so that Windows can resolve the name conflict.
I understand Scott's direction in the forum to not be negative, but this is amateurish at best. I wasted about 6 hours of my life trying to debug why my site was not rendering correctly. It would take 5 lines of code to fix this.
This forum is full of people unhappy because what they see in VSD is not what's rendered in html. This is one more example. It's a shame that Coffee Cup is not sweeping these things up, fixing them and making the product better.
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.