First, I would like to thank Coffeecup for making VSD compatible with PNG files. I've waited almost 2 years for this special day. Now I can finally make a great looking webpage.

But here is the problem.

I'll make a page. I'll add an image to page that spans the width. Then I'll add text and objects on top of that, then hit preview. Everything is fine.

I'll make a replica of that page in a new page, change things accordingly but keep the same image spanning the width of the page and hit preview. Everything looks fine.

Then I go back to the previous page. I'll hit preview, and WHOA! Suddenly, I'm seeing the replicated page underneath all of the objects of the current page.

I know whats going on though. When VSD creates the HTML, it re-creates all the images so they are compatible and easily uploaded. But, from my memory (which is getting bad), VSD always created a new image name for each page even if it was replicated.

This is not happening now. So I can make changes, but since its not changing the image file name for the page, it effects all pages that uses that same source image file.

This seems to me like a mistake, a big one. Otherwise, the whole function of replicating a page is pointless.

If anyone has some thoughts on how to solve this problem, I'd love to hear. I've included a jpeg image. All the stuff squared in red show how VSD is rendering things together.

The only ways I think that can solve this problem is to create the individual pages separately (in separate VSD files), upload them, and go back and put in my links accordingly. Or, I can do iframes...but I'd rather not.

Thanks! I look forward to peoples thoughts on this.

http://i160.photobucket.com/albums/t168/dlwatsonfilmeditor/siteerrors.jpg " class="bb-url">http://i160.photobucket.com/albums/t168/dlwatsonfilmeditor/siteerrors.jpg

I have tried to follow your steps in order to see if I got the same error, but I didn't.

I made a page with a picture background, then added some text and picture buttons on top of it.
Made the next page by clicking Add page and selected 'Duplicate page'. I changed the contents leaving the background pic as it was, previewed both pages - no problem.

Then I started out again, creating a page with a colour background, added a pic on top of the background and spread it out to cover the whole width. Again added text and buttons on top.
Next page was created duplicating the first one, new text and pics added, hit preview for both - again no problem.

Did you do anything differently?

And BTW: The heading I made for my test pages (Text heading with 'Allow advanced text') was found in the files folder in three instances (I made three pages), but the pictures I used had the same filename as I had originally given them, and there was just one instance of each, despite me having used some of them more than once. But - as I said - no problem.

These are my layers for each page:

Background Image (the one you set up when you create a page)

An image on top of of the page.

Objects with effects turned on and PNG image files

and Text.

Not sure if the amount of files is causing the problem or not. But im going to try and rebuild the site and see if it does it again.

Looks like the solution is to rename the image files and change the fill. When creating a brand new web page from scratch again, the problem didn't occur.

So, off to finish the site.

Thanks everyone for the help

D.L. - the CC team changed the way images are created in VSD in version 6. I also have the same issues, but it was with multiple images on different pages. It seems that in VSD 6 they are re-using the same image to reduce files.

Scott said to do this and this, and it is a pain, believe me...

On the page and image that is not correct - On your hard drive where the original image is make a copy and call it something else. Then in VSD on the page that you are having an issue with, re-fill the current image with the new copy you just created.

Yes, you are filling it with the exact same image, but the key point is it is a different file name and when VSD bulds the page it will use that one instead of "reusing" the one from another page.


I hope they correct this....

Larry

Yeah, thats what I had to end up doing.

Its a pain, but, eh...life isn't life without pain.

--> “Scott said to do this and this, and it is a pain, believe me...

On the page and image that is not correct - On your hard drive where the original image is make a copy and call it something else. Then in VSD on the page that you are having an issue with, re-fill the current image with the new copy you just created.

Yes, you are filling it with the exact same image, but the key point is it is a different file name and when VSD builds the page it will use that one instead of "reusing" the one from another page.” <--

Larry,

I have approximately 400 images in my website that are used at least once in a 100x100 square on the jewelry grouping page and then once again on each jewelry item’s Description and full 400x400 picture page square. However, only 72 of the 400 images on my website that are displayed in the smaller grouping page squares and also on the Description page larger squares are reduced to thumbnail size by VSD 6.0, causing the Description page picture to be fuzzy or unclear. The remaining 328 images are display in both the smaller and larger squares correctly. So I am not sure using different file names as suggested by Scott is the correct solution.

Tom

Why does CC staff not say anything about this? Arrghh! Aggravating! Looks like somebody screwed up... ooops!

There was actually a lot more issues going on with Tom's site that took our staff forever to help track down. I actually think I got a few new gray hairs from trying to track all that down

Right now what Tom is basically describing is how the core of Visual Site Designer works. It is not a bug, it is just how the overall infrastructure of the software functions. An alternative would be to use our HTML Editor 2008 instead.

So, yes I agree it can be frustrating, but in the end you will still have a great Website

I dont mean to question the VP of Product Development, if the problem we are all experience with VSD is in its infrastructure, then why hasn't happened before? This only started with me with the two most recent versions of VSD?