"If you have last Wappler 3 installed, make sure it was the last stable 3.9.9 and it was ran at least once. Also make sure you have saved all files there."
Does this mean I must open EVERY project I have (even those I have not touched in months) with 3.9.9 before installing Wappler 4?
It is just only if you have some unsaved changes. If everything was already saved then you donāt need to do anything.
If you had 3.9.9 installed then the project list will be auto imported, otherwise you will just have to re-add manually your projects by using the āopen existing project folderā option.
I have one or two projects which I probably havenāt touched for a couple of years. Eg they might use an old version of Bootstrap 4, customised before Theme Manager was available. Obviously there will be many other files which have changed since then. I suppose in theory this shouldnāt be a problem, but I expect files might be updated automatically if I open them in v4, and probably break things.
I was hoping to keep some projects in v3, at least for the moment. It seems this isnāt possible. Is this correct?
Always backup before any update is my advice, Wappler, OS Updates, any critical update where you don't want to risk corruption, just as a precaution. A worthy habit for all to take note of. Can't put a price on a good backup policy!
Good advice indeed. Several times I've clicked 'save' and suddenly something unfortunate has happened to the current site. I've always had the relevant backup files to hand, but it's not always obvious what needs doing. It's obvious if Wappler has replaced a custom Bootstrap theme with a default one - alarming, but easily fixed. Once or twice it's the client who has informed me that's something's broken, which is an uncomfortable situation. (I should mention that things are better than they were in this respect.)
We rely on Git for this. Any new changes just show up as uncommitted changes.
Also, about the old projects.. I had recent instance where I had to work on an almost year old Wappler .NET project. Everything just broke & had to re-build it in 3.9.9.
But it could have been avoided. I had another 7 month old Wappler .NET project, where I was able to get it to "update", but I had to practically re-build almost every multi/single/paged query because Wappler started using Schema in MSSQL few months ago, and now the old queries wouldn't work anymore.
So, if you tread carefully, you can upgrade your old projects to newer Wappler version.
If you need older Wappler version exe, we have hoarded every version from 2.9.1