Me too @brad, it is literally the reason i used Espresso for so many years, when I open a file and the code starts auto jumping around and changing I could literally feel my heart start skipping some beats.
My old workflow was open Dreamweaver add the component i wanted to a brand new page on a test site not used for anything, copy all code created and files added to my Espresso project and continue working, this was I could feel safe that in 3 years time I could go and make a simple text alteration without breaking anything that was previously working.
I do not blame DMXZone or Dreamweaver or Wappler for that as I know it must be almost impossible to keep backward compatibility spanning over years and years. I would imagine one version or even two versions behind would work fine, so a site I am actively working on for instance where Wappler will update the same site with each new software revision. But when the site has not been opened in 3 years and the client asks for a single image swapped out or a piece of text altered, what then, it might have been created in Wappler 1.2.5 and in three years we could be on Wappler 4, if we keep at a software update each week, then it will be 156 versions old software that created it, will it even recognize the code and how to update it to the latest, and if it does will it alter anything else.
If the client asked to change a single image I am probably charging a cup of coffee, i really do not want to be recreating his entire site because the software broke it.
How about an option saying, This site was created in Wappler 1.2.5 would you like to update the code to the latest available, yes, or no. Then the user has the choice, if they decide to update it, and it breaks, well that was the users choice.