Wappler Version : 6.5.0
Operating System : Mac OS 14.4.1
Server Model: NodeJS
Database Type: MySQL
Hosting Type: Docker
Expected behavior
What do you think should happen?
Dynamic bindings in content generated from the database in a repeat to work as they did before updating to 6.5.0.
Actual behavior
What actually happens?
I’m working on a custom CMS and I store some content in the database that contains dmx bindings and it’s been working great until I updated to 6.5.0. Some content that is generated in a repeat with data from the database that contains bindings suddenly doesn’t work as it did before.
How to reproduce
All I did was update to the 6.5.0 and now pages that worked fine, are not having their bindings replaced with the data, alerts are showing when they shouldn’t and don’t have the proper styling, the button spinners appear when they shouldn’t. Images are missing. Here is a couple examples.
BEFORE THE UPDATE:
Image, alert and form all render normally.
AFTER THE UPDATE:
Image is missing, alert shows by default without styling, checkbox in form not checked by default as it should be and button spinner appears when form is not submitting.
Have you tried opening that specific page up in Wappler then saving it again? I had something similar with charts, when I went to open the page, before it loaded Wappler identified some changes that had occurred and asked me to update. Once that was done it worked as it should.
In the network tab, the correct data from the database query does appear correctly.
Also, I did what @TMR said and resaved my main layout file and it did give me the alert that some components had changed and I saved, but didn’t fix it. I have also redeployed with no luck.
I tried rendering some of the content from the database outside of the repeat, and it still doesn’t work.
If I copy and paste the html from the database field directly onto the page, everything renders normally.
I’m wondering is the issue is with how the data from the database is rendered using dmx-html=“text_html”? Like I said, it worked flawlessly until I updated.
I’m working locally so there shouldn’t be anything to upload if everything updated when I updated Wappler, correct?
Is there a way to force everything to update? Would downloading Wappler and installing over it help?
Ah yea, forgot about that extension updater. Unfortunately that didn’t fix it. I also fixed all the console errors (except the .map ones) and that didn’t help either.
Ok, it definitely appears to be an AppConnect 2 issue. Earlier when I switched from Stable to AppConnect 1 channel, I did it from the “Options” menu and that didn’t work. I just swtiched it from the Extensions Update Channel and now everything works as it should.
If I take the code that is stored in the database and place it directly on the page, it renders fine in App Connect 2, but it doesn’t render correctly in App Connect 2 if pulled from the database in a query and rendered via dmx-html="" or using {{value}}
I’m basically storing html along with bindings in a column in a database table called ‘content’ in a column called ‘text_html’. Each page can have multiple content connected to it. So when the page loads, I get the content that is for that page in a server connect query, then I have a repeat that renders out the content.