Using accordion lists with radio buttons

I am designing a UI for a popup that would allow the user to share a post with one class at a time and select which class. They should also be able to drill into each class and select all or certain students within each class to post to. (The default would be share to all students in the class). I am currently using an accordion list of all classes that expands to then select or unselect students, but each list item is also selectable with a radio button. (see attached). This just seems wrong to me and overly complex interaction specially the fact that with the presence of radio button, I wouldn’t have the ability to unselect all students once expanded if I just wanted to post to one student.

Are there any better approaches or standards to this problem anyone can think of?

enter image description here

How can I reboot my phone without the power or volume buttons?

Title is pretty self-explanatory. My phone’s power and volume buttons don’t work. The home button does. It’s a Lenovo ZUK Z2 Plus.

This phone has always had a tendency to crash unless rebooted occasionally. Now that the power button doesn’t work, I won’t be able to turn the phone on if it crashes and shuts down.

I’ve taken a complete backup, but I’d still like to continue using the phone for as long as possible. In order to prevent the inevitable crash, I’d like to reboot the phone every so often. How can I do so?

Grouped Exposed filters radio buttons : one in two no value ticked. How to programatically force default button be ticked?

Some exposed filters (radio buttons) aren’t systematically ticked when a view is displayed, causing an “An illegal choice has been detected. Please contact admin…” error message and No result found.

Moreover, refreshing the same view, or surfing between similar views with another contextual filter value (taxonomy term ID) : one in two the button is ticked, the other not ! enter image description here

Ticking any radio button once the view is loaded gives correct results.

Errors reported :

  • Warning : Illegal offset type in isset or empty dans convert_exposed_input() (line 1165 of views/handlers/views_handler_filter.inc).
  • Illegal choice 0 in field_statut_depart_value element.

EDIT : I did put below as many details as I could find to illustrate the problem, but after searching and searching, basically the question is : since I can’t find why such behaviour, nor why this is always the same value which is loaded by default, whichever setup I try : How can I alter the form and ensure the default button is ticked on page loading.

This filter filters a field which values can be “Open, Almost confirmed, Confirmed, Full, Closed”, and I need to group the filter values :

  • 1=> Any value excepting Closed, selected by default
  • 2=> Almost confirmed or Confirmed

I played around with Grouped filters and BEF, and achieved the correct radio buttons display with at least 2 different setups. This is the last setup I tried.

enter image description here

I tried then to alter the form :

function MODULE_form_alter(&$  form, &$  form_state, $  form_id) {   if($  form['#id']=='views-exposed-form-my-form'){     $  form['field_status_depart_value']['#default_value'] = 1;     $  form['field_status_depart_value']['#required'] = TRUE;     //dpm($  form);   } } 

I could hide the error message with $ form['field_status_depart_value']['#validated'] = TRUE; . It seems to be solving also the view returning empty result one in two… but now the result are filtered with one or another filter value, while the customer does not know it !

I tried without success to change the UI setup in many manners : with or without ajax, with or without BEF overwriting, optional or not, remember or not.. Same if I set to default select list, the exposed filter value toggles from one to the other at each page refresh.

After night & day fighting with that, I would feel really better to get some help, my most wished Christmas present ! Thanks a lot !

EDIT : this is the relevant parts of code export.

$  handler->display->display_options['exposed_form']['options']['bef'] = array(  'field_status_depart_value' => array(     'bef_format' => 'bef',     'more_options' => array(       'bef_select_all_none' => 0,       'bef_collapsible' => 0,       'is_secondary' => 0,       'any_label' => '',       'bef_filter_description' => '',       'tokens' => array(         'available' => array(           0 => 'global_types',         ),       ),       'rewrite' => array(         'filter_rewrite_values' => '',       ),     ),   ), //...  /* Critère de filtrage: Commerce Product : Statut (field_status_depart) */ //RELEVANT LINES $  handler->display->display_options['filters']['field_status_depart_value']['value'] = array(   1 => '1',   2 => '2', ); $  handler->display->display_options['filters']['field_status_depart_value']['expose']['multiple'] = TRUE; $  handler->display->display_options['filters']['field_status_depart_value']['is_grouped'] = TRUE; $  handler->display->display_options['filters']['field_status_depart_value']['group_info']['remember'] = 1; $  handler->display->display_options['filters']['field_status_depart_value']['group_info']['default_group'] = '1'; $  handler->display->display_options['filters']['field_status_depart_value']['group_info']['group_items'] = array(   1 => array(     'title' => 'Opened',     'operator' => 'or',     'value' => array(       0 => '0',       1 => '1',       2 => '2',       3 => '3',     ),   ),   2 => array(     'title' => Confirmed or almost confirmed',     'operator' => 'or',     'value' => array(       1 => '1',       2 => '2',     ),   ), ); 

WordPress social share buttons without a plugin

After trying to place social media share buttons with all kinds of plugins (and getting sick of them), I'd like to try code them into the theme. I did find few tutorials, but I'm not sure which one to choose. Can you please recommend me one that would allow people to properly share on facebook, pinterest, twitter etc. without any added hassles?

What design pattern should I use to migrate windows lists with buttons to web?

I have a Windows application that I need to migrate to web. This application has many forms that follow the same pattern: (1) a grid on the left with columns and rows than can be selected, and (2) buttons on the right to perform actions. Here is an example:

enter image description here

While this is a very common design layout in windows applications, I noticed that it isn’t quite as common on the web.

For the web version, I considered adding the action buttons inside each line. However, I discarded it because (1) the screen gets quickly polluted with lots of buttons, and (2) some buttons are dangerous and inlining them makes it more likely that the user clicks them by mistake.

Other forms have more columns or more buttons, they all more or less follow the same layout as a Windows app.

What would be the best UX design to migrate these forms to Web? Would it still be a grid with selectable rows and action buttons on the side?

Turn on phone without Power and volume buttons

I own Panasonic Eluga Ray Max phone, How can I turn it on without power and volume button as both are broken. Device is already USB debugging enabled but adb cant see it while only charging. So my basic requirement is to boot the phone.

Now another question is when I connect phone to PC/wall charger, screen lights up, charging status is show and general “power by android” message stay on screen for few seconds. So my question is there must be some sort of kernel gets loads just to display those messages and charging status, so why adb cant see device. and is there any other tool available which can boot a boot with command line when phone is displaying those message or charging status.

Do red “destructive” buttons hurt accessibility?

My organization currently uses red buttons for destructive actions, e.g. Delete A or Revoke X.

I’m wondering if this hurts accessibility, given that our primary CTA buttons are blue and our secondary buttons are gray. I believe colorblind users can make that distinction.

Is there a best practices guide on destruction patterns? One that takes into account accessibility?

To align radio buttons in columns or not

I am building a form with two settings that have two choices each. The two settings are completely independent; the choice for one setting is unrelated to the choice in the other. The design calls for using radio buttons for these choices, and presenting each setting on its own row. The design could align the buttons in the second column:

2x2 grid of buttons

…or intentionally break the alignment:

two rows of buttons

The first is more aesthetically pleasing, but the alignment and proximity of the second column can make the options appear to be related or even exclusive. This problem is exacerbated the farther the proximity with the first column is removed:

two columns of buttons

My engineering side says that the alignment should be removed, as there is no common attribute to the second ‘column’. However, the following image is presented as an argument where alignment of unrelated items improves the design and approachability of a form, and I find the argument has merit:

What metric or guideline should be used to determine when alignment is beneficial to UX vs. detrimental?