In a tableselect entity, one can supply an array of default values, but with a normal array with index starting at 0, the first element will never get checked by default.
In core function form_process_tableselect in form.inc, I notice that effectively, the index of the row is copied in the row's default checkvalue, so if the index is 0, it will get a 0 value and uncheck the box instead of check it. Since I didn't find any documentation stating that the default_values array must not start with element 0, I assume that this is a bug in the construction of the tableselect layout.
Example:
for( $j=0; $j < $max; $j++ ) {
$default_value[$j] = 1;
}
$form['candidates2'] = array
(
'#type' => 'tableselect',
'#header' => $header,
'#options' => $table,
'#multiple' => true,
'#default_value' =>$default_value,
);
This leaves the first box unchecked, but if you supply the array
for( $j=1; $j <= $max; $j++ ) {
$default_value[$j] = 1;
}
Then all boxes are checked.
TBA
See #16 🐛 Default check values in tableselect aren't set properly for a 0-based array. Needs work
Needs work
9.5
Last updated
After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
As a bug this will need a test case