8 comments

• 

  Owen

  9 months ago

  See, there's a good idea. I had it back in 2006. That WordPress doesn't include such an obvious idea, even at the suggestion of its users (and developers), is one major reason why Habari exists.
  
  I actually suggested several options for reducing the menu jumble that plugins inevitably produce. One alternate solution was a unified page of one-off options for small plugins. The trouble was, you had to install a plugin to display the unified options, and explicit plugin dependencies didn't exist, so if you didn't code an alternate way to display your plugin options, your plugin had no config!
  
  Maybe you can get more traction for the concept and have it integrated into WordPress core code. It's hard to get developers to universally use something that requires more code because the core software won't support it for some reason.
  
  Sorry to invade your WP with Habari, but reading your recent twitter exchange, I know where your ideas spawned from. ;)
  reply
• 

  Andrew Rickmann

  9 months ago

  I figured you had probably put that forward at some point given the way Habari works (i.e. very well) but given the newfound desire to make WordPress usable I thought it might be a welcome addition.
  
  My prefered method of reducing the jumble is to require people to learn how to change variables at the top of plugins but I don't think that would go down too well. :-)
  
  It is quite simple to do so I'm not even sure it is necessary in the core. If people can see how to do it quickly and easily then they have the option.
  reply
• 

  Jeffro2pt0

  9 months ago

  They may have the option, but what happens if this becomes yet another place I have to browse to, to see if the plugin settings link is there or not. I wish plugin authors would settle on a one stop shop where all configuration links are located.
  
  Although I understand that because of how some of the administration panels are named, settings links sometimes don't belong in a certain menu versus others. This is a usability issue. Still, I'd like to see some sort of unofficial standard to make the end users life a little less complicated.
  reply
• 

  Andrew Rickmann

  9 months ago

  I doubt this debate will end any time soon Jeffro. It would be nice to be told to put config panels in place A (as distinct from adding extra capabilities which is fine to go wherever they should go) but that isn't the WordPress way.
  
  For sure there will be people who will think the plugin page is a stupid place to put config details as it takes it out of the menu system and others who think that is precisely why it is a good idea.
  reply
• 

  Frank

  8 months ago

  Nice workflow and i like this.
  I have tested this code and i have a probelm, maybe you can help me?
  How it is possible to use a input-field type checkbox for update the vaule in options?
  I can't see the resoltion.
  Thanks!
  reply
• 

  Andrew Rickmann

  8 months ago

  Which part is it that you are have a problem with? Is it the javascript side, or the PHP side?
  reply
• 

  Frank

  7 months ago

  THanks for yout time. I use thsi in php/html
  <input type="checkbox" name="secure_wp_index" id="secure_wp_index" value="1" <?php if ( $secure_wp_index == '1') { echo "checked='checked'"; } ?> />
  Wth this is it possible to save the value of the checkbox. How i make this in the form with wp_ajax?
  reply
• 

  Andrew Rickmann

  7 months ago

  Frank, I'm not quite sure which bit of it you don't know so I have tried to guess.
  
  You need to add a new value in the jquery using
  
  if ($('#secure_wp_index').is(':checked'))
  {
  SecureWP = 1;
  } else {
  SecureWP = 0;
  }
  
  Then add it to the post object right after "pcsc_config-API" : API_Val, so you change that to read:
  "pcsc_config-API" : API_Val , "SecureWP" : SecureWP
  
  you can then check what value is set in PHP using $_POST['SecureWP'] == 1
  reply