I had an issue with my WS Form plugin having a conflict with Brizy but it has not been resolved.
Hi,
I had a previous issue with my WS Form plugin not working correctly on my site. It's still not working but you guys marked it "solved." Can you please look into this for me?
-
Hi Steven,
Thank you for contacting us.
Apologies for the slow progress on this issue. Our system automatically closes tickets that remain in a pending status for a certain period. However, please rest assured that the escalated issue is still active.
If you need to follow up on the progress, you can reply to the private ticket, and it will automatically reopen for you.
If you have any further questions, please let us know.
Best regards,
Ariel H.0 -
Hi Ariel,
I'm just checking in on this again since it's been at least a couple of months. I reached out to WS Form, and they said the issue is on Brizy's end. Here is was they sent me:
Hi Steven
The 2nd error is not being caused by WS Form. If you look in the browser inspector you can find the error in the console.
It appears to be a third party component (Brizy) that is breaking the rendering of Select2 fields on your form. So when we initiate Select2 on your form:
$(this).select2(args);
... Brizy seems to be intercepting that and then erroring.
This is not a WS Form bug.
The error on the page is causing the rest of the form rendering to fail.
0 -
Hi Steven,
I sincerely apologize for the delay in getting back to you.
At the moment, we don’t have a solution to offer, but our developers have been reminded about the issue. Unfortunately, we’re unable to provide an estimated timeframe for a fix.
I understand this isn’t ideal, and I appreciate your patience. If there are any updates, I’ll be sure to let you know.
Best regards,
Ariel H.0
Please sign in to leave a comment.
Comments
3 comments