I see that this issue stretches back over a year ago.
It is frustrating that there is no way to LOCK UP Working Pages from any more changes that make the pages inoperable overnight from Project Development Tuesday Night to Project Development Wednesday morning.
What I am finding is that because Wappler does so many behind-the-scenes actions on SAVE
that I cannot be sure when I do a Save All and Quit that the next time I open Wappler that pages working yesterday are still connecting and functioning without errors .
I have a page saved last night after verifying that it worked perfectly (enabled login, checked the table for username & password, connected with a matched User & then passes on a Browser GoTo ‘anotherpage.php’
Reopening Wappler on the same project folder I find the same page is showing “Failed to load resource” for the input username & password.
I have to REBUILD the page from the Security Provider steps forward to the Form Input class names, variables, etc.
Only then does the form work again as it did yesterday.
I have even taken the whole Project folder and copied and pasted into a new backup Project file so that I have an unchanged Project with exactly the same page construction & files.
HOW CAN I LOCK up the already working php pages so that they are immune to any “Wappler update on save”.
I want to Protect Working pages from Wappler, essentially.
Last updated: