@teefers Thank you very much for your time to reply. Really appreciate, since most probably you hear mane of the questions very often and still you take the time to reply in details. For the users like me who are just users I have any IT background at all your support is very important. So thanks again.
I started 2 years ago with RW + Stacks 3 and all packs from Foundry, now updated with the Foundry 2 and Stacks 4. The drag & drop function was really one of the options that push me to start with RW.
I had no issues until now and I made copies of my project file on a USB stick, but as I said the issue is the same on my “old” file.
I’m using all available image stack from Foundry (Display, Backdrop, PopUp Gallery, Lazy Load Image, Image and also Joe’s Impact stack). On some pages I tried and worked with a warehouse image but it’s easier to drag & drop image on the page. To be honest I never looked at the Resources window to check whether each image is there (sometime since I have a lot of images is better to take it from the HD on the Mac and drop it then to scroll in the Resources to find it…I know is not the best practice…
I put the question just to know what is the best option for a user like me in this kind of situation. My live site is working and has all pictures (my last publishing was 2-3 months ago), so I just want to follow the action steps, which will allow me to be able still to add new pages and/or adapt existing pages without loosing all images when I push the Publish button, because if I understood it well if I push now Publish button with pages where there are no images (in the RW project) those images will be then removed from the live site too after the Publishing, correct?
As proposed above I can publish ONLY the new pages, not the whole project, which is a plus…So I can make time to prepare the file before be ready to publish again the whole project and that’s why wanted to have your expert opinion what’s the best action to do…Of course the idea is when making the adaptation not to get the same issue next time when there is again an update…
Thanks again for your time and replies.