Ctrl+z doesn't work on css files after saving

Wappler General Bugs
1

Thanks for reporting an issue! Spend 60 seconds reading this…

Wappler Version : 3.7.3
Operating System : windows 10
Server Model: PHP 7.x
Database Type: mysql
Hosting Type: ftp

Expected behavior

After saving a css file, wappler should remember a set of last actions that can be reverse-applied via an undo command (ctrl+z).

Actual behavior

I ran into this whilst attempting to reproduce Ctrl+s on code view randomly deletes all content of the page - I’m unsure if they are related.

Undo commands work well on css pages until you save them. Once saved, the history is lost and ctrl+z does nothing. PHP pages work as expected. Reproduced with and without debugging on.

How to reproduce

  1. Create a css page
  2. add some code, don’t save.
  3. undo your changes, several times - all should work fine.
  4. redo your changes, and now save.
  5. try to undo your changes, nothing will happen.
3

Tested this but can’t recreate it. I can undo after saving, as well as before saving the file. Are you sure you don’t restart Wappler after saving the CSS file?
How do you add the changes there - i tested by manually adding different properties and rules in the CSS file in code view.

4

Maybe it has to do with the length of the css file? When recreating I was pasting from a very large file (no restarts of wappler involved). I’m uploading that file to see if you can reproduce on your end, as I’ve left my computer idle for an hour or so and right now it’s working. It seems that it could also have to do with long working sessions. style.zip (2.0 KB)

5

Tested with your file as well as in another by copy-pasting parts of your code - still couldn’t recreate it. Does it always happen to you?

6

I just noticed it today and it was systematic this morning until I had to leave the computer for other things. I upgraded to 3.7.3 yesterday night and I had never noticed this before.

8

If this happens again, please recreate the issue with logging enabled and send us the debug log.

9

I had debug enabled for a while and I’m pretty sure the error was captured, although what I was trying to capture was the ‘blank on save’ issue. Please ignore the error where I was using random words on the css file to see if it saved, that’s to be expected.
This seems interesting:

0202/130354.187:INFO:CONSOLE(0)] "save upload tab.url=file:///C:/Users/natha/Dropbox/dev_www/circles/css/style.css", source:  (0)
[10596:3224:0202/130354.194:INFO:CONSOLE(0)] "START: e[36mStart upload for css/style.csse[39m", source:  (0)
[10596:3224:0202/130354.341:INFO:CONSOLE(0)] "onErrorOccurred [object Object]", source:  (0)
[10596:3224:0202/130354.342:INFO:CONSOLE(0)] "onErrorOccurred [object Object]", source:  (0)
[10596:3224:0202/130355.412:INFO:CONSOLE(0)] "UPDATE POSITION [object Object]", source:  (0)
[10596:3224:0202/130355.982:INFO:CONSOLE(0)] "UPDATE POSITION [object Object]", source:  (0)
[10596:3224:0202/130356.375:INFO:CONSOLE(0)] "UPDATE POSITION [object Object]", source:  (0)
[10596:3224:0202/130356.972:INFO:CONSOLE(0)] "UPDATE POSITION [object Object]", source:  (0)
[10596:3224:0202/130359.459:INFO:CONSOLE(0)] "save tab.url=file:///C:/Users/natha/Dropbox/dev_www/circles/css/style.css", source:  (0)

chrome_debug.zip (28.6 KB)

11

Thank you so much for posting this.
Was never able to capture this nor reproduce this reliably.
We have been seeing this issue in one of the systems where we keep a v2.x Wappler copy for an older project. It has been there since then I think.
Hope the bug is found an fixed.

13

This is probably related to the issues reported here:

which will be fixed in this week's update.

1 Like
14

This should now be fixed in Wappler 3.7.4

16

This topic was automatically closed after 46 hours. New replies are no longer allowed.