initial $value not set in radio.php • Piklist Support

Tagged: conditions, defaults, fields

This topic has 8 replies, 5 voices, and was last updated 9 years, 1 month ago by chris.

Viewing 8 reply threads

Author

Posts
- September 27, 2012 at 8:35 pm #223
  
  pers
  Member
  
  1st, you should have a way of reporting bugs, like trac, jira or http://asana.com/
  
  anyway, found this bug:
  
  in radio.php (and most likely in the rest), when you set the default value (‘value’ => ‘no’) in your piklist, like:
  piklist('field', array( 'type' => 'radio' ,'field' => 'subscribe_to_newsletter' ,'value' => 'no' ,'position' => 'wrap' ,'choices' => array( 'yes' => 'Yes' ,'no' => 'No' ) ))
  
  $value in this line in radio.php is not set since $value is empty (echo $value before this line doesn’t display anything):
  $value = (is_array($value) && count($value) == 1 && !empty($value[0])) ? $value[0] : $value;
  
  However, $value is set after you have selected ‘yes’ or ‘no’ in your settings page and saved it.
- September 28, 2012 at 3:35 am #224
  
  pers
  Member
  
  html.php has the same problem
  piklist('field', array( 'type' => 'html' ,'field' => 'ingress' ,'value' => __('Lorem ipsum dolor sit amet, consectetur adipiscing elit.') ));
  The piklist above produces the correct html tags, but the content is blank
- September 28, 2012 at 11:31 am #225
  
  Steve
  Keymaster
  
  @pers– Thanks for looking into this. We are aware of the issue, and we’re working on it. (it’s actually a bit larger than what we originally thought)
  
  Hope to have a fix soon.
- November 12, 2012 at 5:34 pm #404
  
  Steve
  Keymaster
  
  @pers– fixed in v0.6.7
- November 13, 2012 at 12:45 pm #409
  
  razu
  Member
  
  @Steve – conditional radio for hiding other fields doesn’t work for me both using the codes from tutorial and in piklist-demo (conditional fields). Apart from that, this is a super awesome plugin.
- November 13, 2012 at 2:27 pm #410
  
  Kevin
  Keymaster
  
  @razu-
  
  We actually submitted that issue for testing today so it will be released to you soon, stay tuned 😉
  
  Thanks,
  
  Kevin
- December 19, 2012 at 10:19 am #567
  
  chris
  Member
  
  Was this fixed?
  The conditional fields don’t seem to work on the frontend. (Although I’m still learning piklist’s style, so I’m probably _doing_it_wrong(). But thought I’d check if this was fixed.)
- December 19, 2012 at 10:30 am #569
  
  Steve
  Keymaster
  
  @chris– Frontend support is not 100%. Once backend is fully stable, we will move to the front.
- December 19, 2012 at 2:27 pm #572
  
  chris
  Member
  
  Thanks for the quick reply Steve. In that case, it might be worth removing the line “Powerful Fields: Backend, Frontend, Widgets… it all works the same.” In your readme file and then adding it back in during the update when its actually true, might avoid a lot of confusion.
  
  I assumed that it was a bug due to that message.
  
  Can’t wait until the frontend is supported. Beautiful plugin.
Author

Posts