Weird bug again with library actions. I created a library action in a folder. However after refreshing the list, it shows up in another folder (main folder).
That server action is EMPTY - all my progress is lost\
I saw it coming, as I couldn’t see the server action in my file system. So I took a screenshot of the contents so I can rebuild it quicker. You can see it as proof that there was something…:
This is a bit frustrating as I just lost everything that I did here… I also can’t find it in git, so it really must’ve overwritten the file.
I have saved the file numerous times and debugged in the browser. So it definitely was saving.
I see this regularly. You’ve got to be very careful when creating library actions. It’s not an issue with API versions.
My advice is to create it, save it, add some parame, save it, close it, refresh the view -'if you see duplicates, delete everything, including the folder, refresh the view and start again.
Don’t take any chances as you will lose hours of work otherwise. It’s cost me hours of time this past 2 years.
Once they’re created and running, they’re fine usually.
I’ve said many times before, I don’t do detailed bug reports. There’s a lot of issues and I’d get very little work done if I did. That’s surely an internal process for Wappler with testing teams and automated test processes …
100% Sure I didn’t drag it in there.
I took this screenshot before refreshing the list… I couldn’t open the code view / find it using windows explorer. So I duplicated the server action (see the _copy ) and then started writing a bug report.
I refreshed the list and the server action disappeared. So I thought it was completely removed. Then later I saw it is in the main folder, but empty.
This hasn’t happened to me before.
I just tried it again and can’t reproduce it right now.
It’s very weird, but reminds me of this post:
The fact that at least me and @scalaris frequently have issues with this seems like there must be something going on.
Sadly I don’t know exactly how to reproduce, but there must be something happening that I don’t realise.
And now I’m reading this post from Scalaris again: I did switch target while working on this library action. This is something that I usually haven’t done. So perhaps that has something to do with it. I’ll try test a bit more…
EDIT: I can replicate the issue from Scalaris, and perhaps that also caused the issues in OP.
If you now refresh this view (using refresh icon) you will most likely see two library actions with similar names (_copy) and the copy is the one it recognises in the API.
There was indeed a bug when inserting new Library actions in nested sub folders (when called from the context menu of other library action) , also creating nested sub folders as well.
So this will solve all library action problems. Will be solved in the net update.
