Community forum for knowledge and support

Updated 7 months ago

Relume pro for multistep forms via formly not working as expected

At a glance

The community member Bilal is having issues with Relume Pro's Multistep Forms when using Formly. Checkboxes, radio buttons, and the step-back button are not working, even when trying multiple templates. However, Bilal notes that Formly's own templates work fine. The community members suggest that Bilal may need to implement the Finsweet Attributes Input Active script in the < head > section to get the Relume Multistep Forms to work properly. A new Resources document from Relume is also mentioned as a potential source of information on this issue.

Useful resources

πŸ‘‹ Hi, I started using Relume Pro for MultistepForms via formly now. I have formly setup and working but using relume Multistepforms no Checkboxes or Radio Buttons respond - even the step-back button is not working - I tried multiple Multistep templates and got always not working buttons. Btw I just got formly Pro and their templates work.. Did the formly-attribute-system change? New to this, Please help!

Best, Bilal

E
B
M
9 comments

Hey, could you share a read-only link? I just set up forms using Formly, with checkboxes and had no issues

Did you change anything on the attributes or did you just customised the template and thats it? Because templates used from formly (not relumes) do work right away for me..

I just used a form component from Relume

So the attributes were already set up

there is not much to get out of the read only link..

its just a relume styleguide with a untouched multistep form from relume and the formly script added to the body..

In order to get those to work you will also need to implement the Finsweet Attributes Input Active script in your <head> - <a target="_blank" rel="noopener noreferrer" href="https://finsweet.com/attributes/input-active">https://finsweet.com/attributes/input-active</a> - we have a new <a target="_blank" rel="noopener noreferrer" href="http://relume.io/resources">Resources</a> doc coming soon on exactly this.

Add a reply
Sign up and join the conversation on Slack