Hi team,
I would like to check if there have been any recent changes that might be causing formName to no longer display the form in the live environment.
We’re currently using this ID across multiple pages in our Shopify webstore, and we noticed that there was a change from formName to formId, which seems to be causing our current forms to appear blank or fail to load their content.
Could I please seek your assistance in resolving this issue?
Thanks,
Hi Team,
We haven’t made any updates that would affect how the formName is displayed via the Context API. You mentioned that you noticed a change “from formName to formId.”
Just to clarify, do you mean that formName is now returning the formId in your setup? If so, could you please share some code snippets or error logs so we can review them?
Please make sure to blur out any keys or other confidential information.
Hi Kenny,
It is not changing the variable but our current form with formName seems does not working properly (the form is showing blank for all pages in our website). when we try to get the embedded links through feathery today from that particular form, it seems the embedded link has changed. so when we use the new links from feathery (with formId), it seems to be working properly.
from above, we had assumption that the link with formName is not working properly might be due to some updates from your end? if this not due to any recent changes, do you have any solution for this matter? because changing the links might be high effort for us at the moment
Hi Sandy,
Could you please send me the link you’re using with the formName, along with the one that’s working? Please message me directly instead of posting it here.
Hi Sandy,
I apologize for the confusion earlier. Yes we did had an update and using formName to initialize/load forms are no longer supported. You can change your feathery react version to 2.4.103 or later and your current setup should work. Giving you time to update the scripts to use formId instead of formName.