odoo / odoo/docker

UncaughtPromiseError > OwlError Promesse non interceptée > Invalid prop suffix

Open
#443 12 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
1.2k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

Hello everyone.

I need help, I have an error on my Odoo Docker 16.0.
I can no longer access modules such as invoicing, settings, sales...

Here is the error message that appears.

OwlError: Invalid prop suffix
at CodeGenerator.formatProp (https://odoo.alfagroup.fr/web/assets/183-d5e93cc/web.assets_common.min.js:1787:12)
at https://odoo.alfagroup.fr/web/assets/183-d5e93cc/web.assets_common.min.js:1789:68
at Array.map ()
at CodeGenerator.formatPropObject (https://odoo.alfagroup.fr/web/assets/183-d5e93cc/web.assets_common.min.js:1789:50)
at CodeGenerator.compileComponent (https://odoo.alfagroup.fr/web/assets/183-d5e93cc/web.assets_common.min.js:1792:113)
at CodeGenerator.compileAST (https://odoo.alfagroup.fr/web/assets/183-d5e93cc/web.assets_common.min.js:1684:558)
at CodeGenerator.compileTDomNode (https://odoo.alfagroup.fr/web/assets/183-d5e93cc/web.assets_common.min.js:1720:368)
at CodeGenerator.compileAST (https://odoo.alfagroup.fr/web/assets/183-d5e93cc/web.assets_common.min.js:1684:140)
at CodeGenerator.compileTIfBranch (https://odoo.alfagroup.fr/web/assets/183-d5e93cc/web.assets_common.min.js:1736:101)
at CodeGenerator.compileTIf (https://odoo.alfagroup.fr/web/assets/183-d5e93cc/web.assets_common.min.js:1740:59)``

What should I do? I am completely stuck.

Thank you. :)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Odoo Docker 16.0 deployment and the web asset URL in the stack trace. The issue does not identify a source file, component, failing test, or reproducible configuration; done would require identifying the invalid prop and restoring access to the affected modules.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, javascript
Domain
backend, devops
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.