Check All | None on Content and Comments List Page

-1. Its up to the client to provide such interface tricks. Most clients can do this with bookmarklets already.

How would you propose that a client implement this? As of now, there's no common attribute that the client could use to determine that the checkboxes are related. Theoretically, it could be done if the checkboxes shared a common name. But what would the UI look like?

My point is, no UA has implemented this and there's a working solution used throughout the Web. Let's use that solution.

http://www.squarefree.com/bookmarklets/forms.html is the one you are looking for. See "Toggle checkboxes".

Checking all checkboxes on a page is not a viable solution for most cases (though it may work here).

It is silly to require users to install bookmarklets from 3rd party web sites in order to easily use our pages. Every web mail application I've used provides a 'check all' feature. This is not a "client hack". It is ECMAscript, which is a web standard. +1

Bookmarklets are not a viable solution when viewing a site on kiosk/school web browser. +1 for this functionality, but I really think that these scripts belong in a drupal utility.js file, similar to Rails' prototype.js file.

It also seems to me that there needs to be a bit more logic about where this kind of "check all" | "deselect all" link shows up. As it is, I couldn't tell if it gets added to the table header, footer, or shows up after... I think tossing it in the admin UI makes good sense for now, but I imagine that this would also be useful in more user-facing UIs.

+1 to the concept. It should be in core.

I can't comment on the code since I haven't looked at it.

The same patch now both in header and footer of the table & I adapted it to cvs.

this satisfies a great nead, but i'd rather see a more generic version of check(what) in drupal.js. the one here is defined within BODY tag which isn't so clean

+1 for concept, -5 on implementation:

• It does not degrade. Preferably these extra controls would be added onload through JS. At worst, we generate them with an inline <script> tag which calls an API.
• The code belongs in a .js file with a killswitch, like the other JS in Drupal.
• DOM methods are preferred to legacy accessors like document.forms IMO. We should use getElementsByTagName() instead.
• Instead of a link, why not use a checkbox in the header row? Check it to select all, uncheck it to select nothing. It is ugly to use a separate table row for each of them this.
• We should be more selective with this. We should restrict the list of boxes to check by id/name.

come on folks. how long must we suffer without a 'check all' function? get to it :)

Still seems to work great in 4.6.. Thanks! Hopefully it gets into 4.7 as a usubility thing.

Mike

Here is a new try to implement the check all functionality. It adds a master checkbox to the header of the tables on admin/node and admin/comment.

It's implemented as a new form item 'check_all' and is used as every other form item.

$form['nodes'] = array('#type' => 'checkboxes', '#options' => $nodes);
$form['checkall'] = array('#type' => 'check_all', '#value' => 'nodes');

As you can see the '#value' field is set to the key of the form element that represents the set of checkboxes.
You can also let '#value' point to this form element:
$form['checkall'] = array('#type' => 'check_all', '#value' => &$form['nodes']);

Attached is a patch that adds the 'check _all' form element's theme function to form.inc and does the required changes in node.module and comment.module.

The next comment has the required checkall.js attached.

Here the checkall.js. Place it in the 'misc' folder.

praise to tenrapid for finally submitting a winning patch for this. i tested this and it works as advertised. the API is easy for module developers to use ... rerolled to fix a bad hunk.

RTBC.

-1 on implementation.
The className set on the div is never used. Instead of the regexp in the autoAttach, you can just use hasClass(). Then to extract the id of the target checkboxes, you can use .substring().

Setting the checkbox's name attribute to the parent id sounds like a bad idea, because as per HTML 4.0 name is deprecated and id should be used instead. Does it even need a name attribute? It is not used on the server side...

Related: http://drupal.org/node/57341

-K

Thanks for reviewing and rerolling.

Following Steven's advice I improved the checkall.js.

Also the naming is more consistent. The form element is called 'checkbox_check_all' now.
$form['checkall'] = array('#type' => 'checkbox_check_all', '#value' => 'nodes');

So here's the patch ...

... and the checkall.js.

as this is a feature (a very cool feature, i love it!) it won't be in 4.7. I propose to start a small project out of it, it will be popular, I bet :) from what I saw, this is pretty much doable with form_alter anyways.

This would make a great addition to the Javascript Tools package, http://drupal.org/node/57285, for the 4.7 cycle. tenrapid, would you like to rework it as a module and add it to the package? You could use one of the other jstools modules as a model.

So is this going to finally get in to 4.8 core then?

Great stuff.. this will save a lot of time. +1 :)

I am looking at the 4.7 node.module and I am coming to the thought that the patch above was developed on a 4.6 node.module, is the correct?

EX. 4.7 has no line that shows:

$form['#method'] = 'post';

Thanks for help.

Attached is a small 4.7 module I threw together based on tenrapid's patch that adds a "check all" box to the admin/comment and admin/node screens. One minor issue with this module is that the "check all" box appears at the top of the admin/comment form and the bottom of the admin/node form because of complexities with the node form that I didn't have time to hash out.

Anyhow, I think this may be useful to folks who want that 'check all' box.

Duplicate: http://drupal.org/node/84961