New Library Action does not show the steps

[guptast]

Hi,

Wappler 3.7.3, MacOS, ASP.NET

When I create a new Library Action (Right Click on Library -> Add Library Action), the UI for managing Settings for the new action remains empty. The settings for other Server Connect actions are appearing correctly.

Do I need to change any setting before adding library actions?

Any assistance would be greatly appreciated.

[Teodor]

Hello, do the steps and properties appear if you click refresh?

[guptast]

Hi @Teodor, the UI remains blank even after refreshing. I have restarted the app a couple of times as well and these still do not appear.

[Teodor]

Please restart Wappler with logging, recreate the issue and attach the debug log there:

How to report bugs together with the Wappler debug log

Updated for Wappler Version 5.0 and higher We have a built-in bug reporting in Wappler that auto post a topic in this forum together with the debug log. Starting from version 1.1.0 the logging isn’t available per default, so you need to restart Wappler with logging. You can do that by clicking on the Wappler’s tray icon (Windows right click) and then choose “Restart with Logging” Then reproduce your problem and choose to submit a bug report from the Wappler menu File / Submit error report … o…

[guptast]

OS info

• Operating System : Mac OSX 20.2.0
• Wappler Version : 3.7.3

Problem description

Adding a new library action is not showing Steps and Properties

Steps to reproduce

1. Add a new library Action
2. Name the action
3. A new action is added and file is saved
4. No Steps and Properties appear

report_2021-1-2_17-46-46.zip (328.8 KB)

[sid]

There seems to be a bug with file path in ASP.NET projects.
We have used library with PHP & NodeJS without any issues.

We are seeing exactly as described in this post. The library SA is blank after creation.
When trying to open the SA in editor, using menu/icon, it returns error saying bad path… so it looks like Wappler created the library SA file in one path, and when opening its searching for it in another.

chrome_debug.zip (2.2 KB)

[Teodor]

This has been fixed in Wappler 3.7.5