Luis, I assume that you are adding a new photo but noticing that all previously loaded photos are also being uploaded again?

Unfortunately this is the nature of the beast. WX5 does not look at the host to verify the name, size and date of a file pending upload is identical, it looks at changes within your project to see whether changes have been made to a page. One change on a page could mean the whole page and it's content is uploaded again.

Holding CTRL when selecting preview will cause the whole site to be refreshed and result in almost all website content to again be uploaded.

If you find this behaviour troubling you may wish to try filezilla or similar (first export project to disk in it's own folder). The first time will result in all files being uploaded to the host, subsequently you will have the option of uploading only new and changed content.

If you opt for filezilla or similar, please make frequent use of export project (to create an iwzip). The automated backup of the project only happens when you upload from within WX5

Thanks for your quick response. Dind't understand that blog works that way. As I understand, if I post one new Mbyte photo every day, WX5 upload all blog again, and agaig, for over all weeks, months, years... right ? One question, it's only WX5 or all blog's work that way?

I think it's just how WX5 works.

Once again, thanks for quick response. Does it make any sense? Upload hundreds of files because I change 1 photo ...? Can WX5 think about this and change way how it works? It that possible? Regards

Note: One thing I love in WX5 is precisely upload only I change in websites ... (discover now that blog don’t work that way) Please change that 

Hi Luis, 

thank you for getting in touch.

Please consider that there are some modifications which might seem minimal, but which in realty require the entire project regeneration and, consequently, its entire export. Such modifications affect, for example, the header and footer, the menu, the e-commerce section and  the blog, like in your case. 

If we for example add a picture to the blog, the entire blog has to be regenerated. Now, the new picture is necessarily on a page, which has to be regenerated as well. In the page some links can be present, so that also the linked pages will have to be regenerated. I made this example mentioning the blog, but this operation affects other project aspects as well. In this way, we avoid the coexistence of old and new parts of the website.

I hope having clarified your doubts. Please feel free to get back to me if you still have questions related to this issue. Have a lovely day!

Hello Luis

When you need images and don't want your site filled up with unwanted "copies" then you could use links.

You upload the images to a folder you make/create for this purpose.

Then - when you need an image, you specify the link (URL) to this image, instead of specifying a file on your PC.

This should decrease the amount of "copies". 

To be completely sure that no "new" images is created, you could use a html-object and in here specify the image and the appearance of the image ( size shown, hovering and other things )