Wappler saves lib server action in the root instead of the subfolder

Wappler 7.3.9
MacOS 15.6.1

Wappler saves lib server action in the root instead of the subfolder:

Hi. Take a backup of current file and close/quit Wappler.

I see two files - one in lib and other in stats.
Delete both the files.

Restart Wappler.

Create the lib where you need again.

Hi. What do mean with create again?

This here is a Wappler bug that saves the file, when updated, on the wrong path. Means the updated file is being writted into the lib roots.

The bug here could actually be that if you would have moved the library action, Wappler would not have done so correctly.

Hence I suggested to delete the file, recreate it in the right place, and see if it still does the same.

It does the same. I’ve just left it in the screenshot to show where the original files is and where the saved on is being placed.

1 Like

I have come across a similar issue. I created a new lib API with this folder structure

Library -> 1 -> 0 -> FileManagement -> lib_upload_tenant_docs

It has auto created two additional subfolders and APIs.

  1. A new subfolder with the new API: Library -> FileManagement -> lib_upload_tenant_docs, and
  2. Another copy of the same lib API in the Library -> lib_upload_tenant_docs.