Unexpected token N in JSON at position 0

Wappler Version : 5.2.1
Operating System : Windows
Server Model: NodeJS
Database Type: Mariadb

What do you think should happen?

I realize that parseJSON cause error.

Before updates to 5.2.1 my page worked normally.
In Server Action:
Set Value = query.config_value.parseJSON() with no error:

At same time.
In UI a dynamic JSON value comes from SC works normally wihout using .toJSON().

What actually happens?

After update to v5.2.1
In server actions if exists any Set Value with .parseJSON outputs it throws the error., e.g…

Set Value = query.config_value.parseJSON() throws next error:


If I remove the .parseJSON() the error disappears.
Set Value = query.config_value

At same time:
In UI a dynamic JSON value comes from SC it’s mandatory to use .toJSON() without it cause [object Object]

Temp workaround to solve this

Fortunately I don’t have much JSON parse in SC and UI, so, I just remove it.

Would be great to know if this will keep permanent from now or I should later have to revert this again?

Other option is downgrade the files from the new v5.2.1
Not uninstall Wappler just replace this files:

image
v5.2.0.zip (34.5 KB)

Community Page
Last updated: