Yesterday, I encountered a serious issue while editing my WeWeb app. Suddenly, all elements stopped displaying on my pages, showing an error message saying “element undefined.” This issue is also occurring in the production version of my app.
I submitted a support ticket yesterday, but the response from WeWeb support has been very slow. This is a critical problem—my users are complaining that they can’t use the app properly, and it’s impacting their experience.
I’m starting to lose confidence in WeWeb as a reliable no-code platform. If the support remains unresponsive and the platform continues to cause bugs in my production app, I might need to reconsider using it.
No, How can I do this? Can you please give me a step by step?
Every page I click, this bug happens (on pages that was working fine before, its starts to happen)
I am afraid that If I restore to a backup version this also happens again.
But maybe it is worth a shot
I think I found out your issue, you have many text bound on some page that come from your database, and some seems to contain invalid html like this one
Please review them and either use the option “sanitize” so it doesn’t interpret the HTML inside or use our HTML element or rich text element to render it
It should fix the issue for Target audience page and most probably every side effect linked to this issue
On your pages, you can search for text elements and check all those that have a binding.
It worked, thank you for your help!
But do you know why a broken field on this “target audience” page broke all my other pages?
All the elements from the other pages like “strategy”, “product”, etc, stopped to work as well
I don’t think they really stopped to work, it’s just once you visited the bugged one it broke the editor
Also, be aware change in the editor does not affect the published app, so, if you did not publish, the issue was probably already there but showed up only later after a change in the data you was binding to the page (broken html introduced in your database afterward for exemple) as you may use the same dataset in the editor and in the published app it probably broke both
