Skip to Content
Menu
You need to be registered to interact with the community.
This question has been flagged
1 Odgovori
1970 Prikazi

I just updgrade my custom addon, please help to solve this error message:

UncaughtPromiseError > ParserError

Uncaught Promise > parsing error

ParserError: parsing error

    at parsePrefix (http://localhost:8069/web/assets/469-00577f6/web.assets_backend.min.js:1310:461)

    at _parse (http://localhost:8069/web/assets/469-00577f6/web.assets_backend.min.js:1334:66)

    at parsePrefix (http://localhost:8069/web/assets/469-00577f6/web.assets_backend.min.js:1313:79)

    at _parse (http://localhost:8069/web/assets/469-00577f6/web.assets_backend.min.js:1334:66)

    at parse (http://localhost:8069/web/assets/469-00577f6/web.assets_backend.min.js:1336:71)

    at parseExpr (http://localhost:8069/web/assets/469-00577f6/web.assets_backend.min.js:1149:709)

    at evaluateExpr (http://localhost:8069/web/assets/469-00577f6/web.assets_backend.min.js:1150:86)

    at makeContext (http://localhost:8069/web/assets/469-00577f6/web.assets_backend.min.js:245:375)

    at _preprocessAction (http://localhost:8069/web/assets/469-00577f6/web.assets_backend.min.js:5864:16)

    at Object.doAction (http://localhost:8069/web/assets/469-00577f6/web.assets_backend.min.js:5948:170)

Avatar
Opusti
Best Answer

Hi,
if this is test db, uninstall the custom addons and see if the error disappears, if yes, you can confirm the issue is coming from that app.

Once confirmed, you have to cross check the view files from that module and ensure everything is okay in it.
 
Thanks

Avatar
Opusti
Related Posts Odgovori Prikazi Aktivnost
1
dec. 24
11624
0
okt. 23
1688
1
okt. 23
1833
2
jul. 25
470
1
dec. 24
3295