Visforms Subscription: Conditional Display Fields are Not Displayed - Question | JoomShaper
SP Page Builder 6 is Here! Learn More →

Visforms Subscription: Conditional Display Fields are Not Displayed

C

Christoph

Template 1 month ago

Hello, I use the “wimble” template on my homepage and use Visform components for forms (https://vi-solutions.de/de/subscribe) . Unfortunately, this conditional display of form fields no longer works correctly.

According to the Visforms administrator, however, this is due to my template and not the Visforms component.

Here is the link to the affected page: https://www.landlerhilfe.at/home/index.php/christkindl-aus-der-schuhschachtel/seiten/unterstuetzung-beim-making-of

When you make a selection from the “Wählen Sie die Art der Unterstützung aus*” list, additional fields should appear after the selection, but they do not.

The following error appears in the developer tools from browser: Uncaught TypeError: Cannot read properties of undefined (reading 'localName') at HTMLInputElement.<anonymous> (main.js:238:30) at HTMLInputElement.dispatch (jquery.min.js?3.7.1:2:40035) at v.handle (jquery.min.js?3.7.1:2:38006) at Object.trigger (jquery.min.js?3.7.1:2:70124) at HTMLInputElement.handler (jquery.min.js?3.7.1:2:37521) at HTMLInputElement.dispatch (jquery.min.js?3.7.1:2:40035) at v.handle (jquery.min.js?3.7.1:2:38006) at HTMLInputElement.handler (jquery.min.js?3.7.1:2:37391) at HTMLInputElement.dispatch (jquery.min.js?3.7.1:2:40035) at v.handle (jquery.min.js?3.7.1:2:38006) https://www.landlerhilfe.at/home/templates/wimble/js/main.js

jquery.min.js?3.7.1:2 jQuery.Deferred exception: Cannot read properties of undefined (reading 'localName') TypeError: Cannot read properties of undefined (reading 'localName') at HTMLInputElement.<anonymous> (https://www.landlerhilfe.at/home/templates/wimble/js/main.js:238:30) at HTMLInputElement.dispatch (https://www.landlerhilfe.at/home/media/vendor/jquery/js/jquery.min.js?3.7.1:2:40035) at v.handle (https://www.landlerhilfe.at/home/media/vendor/jquery/js/jquery.min.js?3.7.1:2:38006) at Object.trigger (https://www.landlerhilfe.at/home/media/vendor/jquery/js/jquery.min.js?3.7.1:2:70124) at HTMLInputElement.<anonymous> (https://www.landlerhilfe.at/home/media/vendor/jquery/js/jquery.min.js?3.7.1:2:70726) at ce.each (https://www.landlerhilfe.at/home/media/vendor/jquery/js/jquery.min.js?3.7.1:2:3129) at ce.fn.init.each (https://www.landlerhilfe.at/home/media/vendor/jquery/js/jquery.min.js?3.7.1:2:1594) at ce.fn.init.trigger (https://www.landlerhilfe.at/home/media/vendor/jquery/js/jquery.min.js?3.7.1:2:70701) at ce.fn.<computed> [as focus] (https://www.landlerhilfe.at/home/media/vendor/jquery/js/jquery.min.js?3.7.1:2:86549) at HTMLDocument.<anonymous> (https://www.landlerhilfe.at/home/index.php/christkindl-aus-der-schuhschachtel/seiten/unterstuetzung-beim-making-of:651:65) undefined ce.Deferred.exceptionHook @ jquery.min.js?3.7.1:2 t @ jquery.min.js?3.7.1:2 setTimeout
(anonymous) @ jquery.min.js?3.7.1:2 c @ jquery.min.js?3.7.1:2 fireWith @ jquery.min.js?3.7.1:2 fire @ jquery.min.js?3.7.1:2 c @ jquery.min.js?3.7.1:2 fireWith @ jquery.min.js?3.7.1:2 ready @ jquery.min.js?3.7.1:2 P @ jquery.min.js?3.7.1:2

https://www.landlerhilfe.at/home/media/vendor/jquery/js/jquery.min.js?3.7.1

main.js:249 Uncaught TypeError: Cannot read properties of undefined (reading 'localName') at HTMLInputElement.<anonymous> (main.js:249:34) at HTMLInputElement.dispatch (jquery.min.js?3.7.1:2:40035) at v.handle (jquery.min.js?3.7.1:2:38006)

In an earlier version that I restored on my backup web space, the handling still works correctly: https://christl.it/landlerhilfe/index.php/christkindl-aus-der-schuhschachtel/seiten/unterstuetzung-beim-making-of

Here is also the feedback from Visforms: https://vi-solutions.de/de/forum/19-joomla-extension-visforms/2934-bedingte-anzeige-felder-werden-nicht-angezeigt#11805

"Hallo Christoph,

der Javascript Fehler entsteht im Javscript deines Templates (in der Datei main.js). Dieses Javascript läuft auf Visforms an. Der Code prüft aber nicht, ob $(this).prev()[0] existiert (was es im Falle von Visforms nicht tut) und versucht dann direkt auf eine Eigenschaft dieses nicht exsitierenden Elements zuzugreifen. So etwas erzeugt in Javascript immer einen Fehler. Was zur Folge hat, dass dann auch Visforms nicht mehr funktioniert.

Es müsste also der Fehler im Javascript des Templates behoben werden.

Herzliche Grüße, Aicha"

Joomla! 5.3.3 Stable [ Timu ] 19-August-2025 16:00 GMT Wimble 2.1.2 Visforms Version 5.5.1, Subscription Version 5.5.1

I hope you can help me. thank you!

0
7 Answers
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 1 month ago #204205

Hello,

Thanks for reaching out to us. Could you please share temporary administrator access to your Joomla backend? You can provide the credentials securely in the hidden content section. Also, please take a full backup of your site before we make any changes.

Once I have access, I’ll investigate further and see what’s causing the issue. Let me know once you’ve shared the details!

Best regards,

0
C
Christoph
Accepted Answer
1 month ago #204256

Hello Ziaul Kabir, thanks for your help. I have taken a backup now. I received a tip from the visforms administrator that there may be overrides for the component, but how can I delete them? How can I ensure that the original files are used? Can you tell me how to do this or delete them for me? I'm not aware of having created any. thx!

Please find the access data in the hidden field.

Br Chris

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 1 month ago #204261

Please, re-check your provided credentials. It's seems to be incorrect.

Thanks

0
C
Christoph
Accepted Answer
1 month ago #204264

I have just successfully logged in.

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 1 month ago #204275

Please, check now, I have fixed issues from our end.

Thanks

0
C
Christoph
Accepted Answer
1 month ago #204282

Hi, I just reopened the form (after clearing the Joomla and browser cache), but the conditional fields are still not displayed.

i get in the developer tools this message: A <label> isn't associated with a form field.

To fix this issue, nest the <input> in the <label> or provide a for attribute on the <label> that matches a form field id

According to the developer of Visforms, this is caused by overrides. Can you please delete the overrides so that the original Visforms files are used? Is that possible?

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 1 month ago #204286

Hi Christoph,

Thank you for checking and providing the details.

The issue you’re seeing in the developer tools:

A <label> isn't associated with a form field

is related to how the form HTML is rendered. This is something the Visforms developer would be best suited to assist with.

Best regards,

0