Answers.Body: <p>webform conditionals is native to D7 webform module - and independent of webform civicrm module.</p>
  
  <p>If conditionals for D7 webform module are not working as expected you may have some javascript issues on your site. Look in the browser's console to check for errors. </p>
  
  <p>If your test system is using a different front end theme and if admins with permissions are able to use admin theme - then it's very likely that your javascript issues are inadvertently caused by your front end theme. Perhaps it requires jquery update module e.g.?</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-27T22:31:22.673Z
Answers.Text: Karin Thanks for your suggestions.  Both sites use Bartik and Seven for Admin.  There are the same versions.  The browser console shows fourteen errors in the main system and none in test.  They all start with Uncaught TypeError: Cannot read property
Answers.UserDisplayName: gcpower
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-27T22:45:51.037Z
Answers.Text: I have installed the jquery update module and the version is set to 1.10. The status page confirms this.   Errors now reduced to five, but the conditionals still not working.
Answers.UserDisplayName: gcpower
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-27T22:48:57.650Z
Answers.Text: I have checked whilst logged in and conditionals not working now..
Answers.UserDisplayName: gcpower
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-28T01:05:30.130Z
Answers.Text: Check everything (modules, versions, config) across test and production - there has to be a difference.
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-29T08:30:16.663Z
Answers.Text: Since installing the jquery update module, the module listing order has changed. It also means that the drop downs are no longer active, preventing me from checking version numbers.  Other than the jQuery module, the module list is the same.  The two config files are identical.
Answers.UserDisplayName: gcpower
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-27T17:15:51.667Z
Answers.LastActivityDate: 2018-12-27T17:15:51.667Z
Answers.UserDisplayName: KarinG - Semper IT
Answers.Body: <p>Matthew Wire has solved this for me.  It was a jquery error. It seems to happen if the new CiviCRM menu (kam extension) is enabled - so must be some interaction going on with loading CiviCRM resources.  Disabling that seems to resolve the javascript issues and hence webform starts working again.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-06T22:23:38.060Z
Answers.Text: does this mean a fix is needed for kam or for webform and are you or matt following up on this?
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-09T22:36:05.880Z
Answers.Text: I'm not quite sure what is actually causing the error (which is a browser console function undefined error) (other than I assume that some resources being loaded for kam are overriding resources used by webform).  The difference in this case was that the dev site did not have the kam extension installed - and I haven't tried installing it.  @gcpower perhaps you could try installing the kam extension on your dev site and if it's an issue there report it as an issue at https://github.com/aydun/uk.squiffle.kam
Answers.UserDisplayName: Matthew Wire
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-11T13:03:05.410Z
Answers.Text: https://github.com/aydun/uk.squiffle.kam/issues/32
Answers.UserDisplayName: Matthew Wire
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-01T11:56:28.390Z
Answers.LastActivityDate: 2019-01-01T11:56:28.390Z
Answers.UserDisplayName: gcpower
Body: <p>Seasons greetings I am using conditionals to hide content on a civicrm webform using Drupal 7 with Civicrm 5.8.2.  It has been working fine, but the form now presents with all the conditional fields displayed. This does work correctly, if the user is logged in.  That is not acceptable as all users are anonymous. My test system using the same versions is working correctly.  I have ensured that all versions are the same across the two systems.  Any clues on where to look now would be much appreciated. 
  Regards Graham</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-27T16:24:49.360Z
Comments.Text: Have you compared the permissions settings between your live site and the test system?
Comments.UserDisplayName: Lesley Carter - BackOffice
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-12-27T22:11:12.750Z
Comments.Text: Lesley  Thank you.  Yes I have and they are identical.
Comments.UserDisplayName: gcpower
Tags: <drupal><webform-civicrm>
Title: Webform civicrm Conditionals not working
ThreadText: # Webform civicrm Conditionals not working
  
  (Asked by: username_0 on 2018-12-27)
  
  Seasons greetings I am using conditionals to hide content on a civicrm webform using Drupal 7 with Civicrm 5.8.2. It has been working fine, but the form now presents with all the conditional fields displayed. This does work correctly, if the user is logged in. That is not acceptable as all users are anonymous. My test system using the same versions is working correctly. I have ensured that all versions are the same across the two systems. Any clues on where to look now would be much appreciated.
  Regards Graham
  
  **Tags:** drupal, webform-civicrm
  
  > **Comments:**
  > **username_1**: Have you compared the permissions settings between your live site and the test system?  
  > **username_0**: username_1  Thank you.  Yes I have and they are identical.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2018-12-27. Score: 2
  
  webform conditionals is native to D7 webform module - and independent of webform civicrm module.
  
  If conditionals for D7 webform module are not working as expected you may have some javascript issues on your site. Look in the browser's console to check for errors.
  
  If your test system is using a different front end theme and if admins with permissions are able to use admin theme - then it's very likely that your javascript issues are inadvertently caused by your front end theme. Perhaps it requires jquery update module e.g.?
  
  > **Comments:**
  > **username_0**: Karin Thanks for your suggestions.  Both sites use Bartik and Seven for Admin.  There are the same versions.  The browser console shows fourteen errors in the main system and none in test.  They all start with Uncaught TypeError: Cannot read property  
  > **username_0**: I have installed the jquery update module and the version is set to 1.10. The status page confirms this.   Errors now reduced to five, but the conditionals still not working.  
  > **username_0**: I have checked whilst logged in and conditionals not working now..  
  > **username_2**: Check everything (modules, versions, config) across test and production - there has to be a difference.  
  > **username_0**: Since installing the jquery update module, the module listing order has changed. It also means that the drop downs are no longer active, preventing me from checking version numbers.  Other than the jQuery module, the module list is the same.  The two config files are identical.  
  
  ---
  
  ### Answer by username_0 on 2019-01-01. Score: 1
  
  username_4 has solved this for me. It was a jquery error. It seems to happen if the new CiviCRM menu (kam extension) is enabled - so must be some interaction going on with loading CiviCRM resources. Disabling that seems to resolve the javascript issues and hence webform starts working again.
  
  > **Comments:**
  > **username_3**: does this mean a fix is needed for kam or for webform and are you or matt following up on this?  
  > **username_4**: I'm not quite sure what is actually causing the error (which is a browser console function undefined error) (other than I assume that some resources being loaded for kam are overriding resources used by webform).  The difference in this case was that the dev site did not have the kam extension installed - and I haven't tried installing it.  @username_0 perhaps you could try installing the kam extension on your dev site and if it's an issue there report it as an issue at https://github.com/aydun/uk.squiffle.kam  
  > **username_4**: https://github.com/aydun/uk.squiffle.kam/issues/32  
  
  ---
  
  