All topics

Component attributes not updating in editor...

mdxwired

5 months ago

Hey all. Has there been a recent change to how/when the editor updates component attributes when the underlying linked variable or formula changes?
My page worked perfectly in the editor yesterday and still works perfectly in 'preview' mode, but is now very erratic within the editor itself.
I have cleared all site data (browser cache, cookies, etc...) and everything else that I can think of...
When I pause the 'test' run and click on the attribute, the contents say that they are what they should be, they just do not pass to the component or display correctly on the page.

Thanks in advance!!
Andreas Møller

5 months ago

No not we are not aware of any changes that would cause this
Jacob Kofoed

5 months ago

Are there any errors in the browser console? (f12)
mdxwired

5 months ago

Nope. All clear.
mdxwired

5 months ago

Ooop! Hold that thought. Found a 'buried' issue... I'm checking...
mdxwired

5 months ago

OK. Error unrelated but fixed just in case. Problem still exists.
Further interesting diagnostic... everything updates instantly and correctly if I make any change to any other attribute of any component on the page (includng the component with the issue). That seems to force an update of ALL components on the page.
needtheanswers

5 months ago

+1 I have the same issue
I need to manually refresh the page in order for my component attributes to update
mdxwired

5 months ago

Interesting... for me that does not work. Some attributes display the correct information (including many that are pulling from an API on load), and others will only refresh correctly if I change some other attribute.
Also have tried it in two different browsers... Chrome and Opera.
Jacob Kofoed

5 months ago

Can you link the project or make a short screenshot/video so I'm 100% sure on the issue. I have not been able to recreate it thus far.
mdxwired

5 months ago

@Jacob Kofoed I will add you to the project... hang on.
mdxwired

5 months ago

@Jacob Kofoed is it just jacob?
@mdxwired
@Jacob Kofoed is it just jacob?
Jacob Kofoed

5 months ago

Yup 👍
mdxwired

5 months ago

You will need to use the login page first to estalish auth for the API calls.
mdxwired

5 months ago

Hold please... trying to change a password in Supabase. I foolishly used a common one for me. Duh.
needtheanswers

5 months ago

@Jacob Kofoed In my case I´m trying do delete cart items. The calculations and the button are both components, fed with the same data. As you can see the button is updating as soon as the request finishes but as for the calculations I would need to refresh the page manually
needtheanswers

5 months ago

@mdxwired Any news on this? Were you guys able to solve this?
@needtheanswers
@Jacob Kofoed In my case I´m trying do delete cart items. The calculations and the button are both components, fed with the same data. As you can see the button is updating as soon as the request finishes but as for the calculations I would need to refresh the page manually
Jacob Kofoed

5 months ago

I think I would need to see the project to help you with the specific issue. Do you have a link to it that I can see? For @mdxwired we tried some different approaches. I'm not sure we know for sure, but the issue might have been related to how APIs are not guarenteed to be loaded server side in the editor vs. preview.
@Jacob Kofoed
I think I would need to see the project to help you with the specific issue. Do you have a link to it that I can see? For @mdxwired we tried some different approaches. I'm not sure we know for sure, but the issue might have been related to how APIs are not guarenteed to be loaded server side in the editor vs. preview.
needtheanswers

5 months ago

Gonna send you a DM right away. And thank you for the information regarding @mdxwired 's project
@needtheanswers
@Jacob Kofoed In my case I´m trying do delete cart items. The calculations and the button are both components, fed with the same data. As you can see the button is updating as soon as the request finishes but as for the calculations I would need to refresh the page manually
needtheanswers

5 months ago

So in my case the problem was that I was using a variable to set the lines of the calculations when I should have used a formula to do so instead. "Variables with a default value are only updated the first time, but will not update their values automatically when attributes change" Thank you @Jacob Kofoed for explaining this to me and solving my issue.
💪1
👍1
mdxwired

5 months ago

Sorry. Yes. I needed to use internal component variables because one cannot directly change attributes from within, and I did not want my components 'bouncing' in and out with every click. That said, a reasonably clever use of the "Attribute Changed" event allowed me to 'catch' the delayed update of the API-fed attribute that was lagging behind. I simply grab the initial state of all attributes on the way in the first time, set my internal variable(s) accordingly, and then use "Attribute Changed" to check to see what changed and decide if I need to update the variable first set above. Works every time now.!!! 😎
💪1
mdxwired

5 months ago

The 'need' for internal variables described above is due to the interdependence of some of my internal mechansisms (things that change or update based upon the changing states of other things).

Component attributes not updating in editor...

mdxwired

Andreas Møller

Jacob Kofoed

mdxwired

mdxwired

mdxwired

needtheanswers

mdxwired

Jacob Kofoed

mdxwired

mdxwired

Jacob Kofoed

mdxwired

mdxwired

needtheanswers

needtheanswers

Jacob Kofoed

needtheanswers

needtheanswers

mdxwired

mdxwired

Stop scrolling. Start building.

Chat with @team-toddle

Video call our CEO

Get in touch!

Product

Company

Resources

Community