Wappler Version : last stable
Operating System : MacOS Sonoma
Server Model: NodeJS
Database Type: PostgreeSQL
Hosting Type: custom
the expression itself works fine in the code, but is not editable
How did you initially added this, was it through the UI?
in the usual way, through the editor. - UI . The new one fills normally, but if you open it a second time, the contents are inaccessible
Ok, we’ll check this.
For reference, I have the same issue most of the time in 3.9.7 so it is a very old piece code you’ll need to look at!
This has been fixed on the beta channel only.
It is advisable to switch to the beta channel and make sure everything is working fine as it will be soon made stable and then the old app connect 1 will get deprecated.
I switched to beta, update and logoff and restart - but nothing changed - expression content is still empty
Perhaps the reason is that in the expression Wappler automatically changes the syntax and receives an incorrect option, which next time it cannot open correctly
I have no idea if this is related… I have experienced a phenomenon where I edit the code through the visual editor (e.g. - to have the page execute some commands onLoad or onReady) and the visual editor shows the changes graphically. However, when I “save” the changes (within the graphical editor), the actual code is unchanged. I have to make the programmatic changes in the code itself as the visual editor doesn’t make the changes. I may not be explaining this particularly well, so let me know if you want more information. By the way, this doesn’t happen on all pages and I haven’t found why some pages behave this way while other do not.
1 Like
yes, this is also an old problem, it also happens to me often, it seems that it also occurs when you use some formatters and wappler incorrectly cleans the old version of the code
Has this Flow Not Saved issues come back? 
It was a very old problem… early Wappler version 3.
I use Wappler 3.9.7 with some absolutely massive page flows, and it has been completely stable.
If this problem had come back, it is a huge reason for me not to move to Wappler v6…
If you think it is related to specific code in the flow, is there a way this can identified?
And can this topic please be put into another bug report, as it is very important and not related to the original bug…
1 Like
Please keep different issues in different topics.
Also, post quality bug reports, saying “sometimes id doesn’t save” is really not clear. What it doesn’t save? Where? Which component are you using? What are the steps to reproduce this? What is the code generated?
No Antony, there are no any “issues that came back” from version 3. And it’s really time to upgrade, as we’re already on version 6.
1 Like
Teodor, As per you request, here is the new topic I created. Thank you so much for the outstanding support and if you need more information, please let me know. I included a video in the new topic for precise illustration of what is happening.
https://community.wappler.io/t/editing-changes-via-graphical-interface-not-saved/53758
Thank Antony for the feedback. I don’t know if this is the same issue but I opened a new topic and included a video for clarification. If you could take a look at this and see if this is indeed what you had previously experienced… I’d appreciate it.
https://community.wappler.io/t/editing-changes-via-graphical-interface-not-saved/53758
Seems there was also an old topic about this:
Yes - this seems to be an old problem and it has not changed since then 