Checkboxes should be selected after completion of action.

Created on 3 April 2025, about 1 month ago

Problem/Motivation

Checkboxes should remain checked after action completion.

Steps to reproduce

  • Install VBO module.
  • Enable the module.
  • Create view of article nodes and add Bulk operation field.
  • Now select nodes using checkbox and perform action
  • After confirm action when page redirect to view listing back, checkboxes should not unchecked.

Proposed resolution

Removed $this->deleteTempstoreData function from ConfigureAction and ConfirmAction Forms.

Remaining tasks

On manually selection, solution is working but for Select All button, checkboxes does not remain checked.

User interface changes

API changes

Data model changes

Feature request
Status

Active

Version

4.1

Component

User interface

Created by

🇮🇳India shailja179 India

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @shailja179
  • 🇨🇦Canada joelpittet Vancouver

    I would say this adds lots of complexity for little value, I would suggest closing as won’t fix. Consider deleting would have no rows to select for example. I’ll let Graber decide though, he might have another take

  • 🇮🇳India shailja179 India

    I understand the concern about added complexity, but I think this could be a useful special-case feature. If there are other operations that need to be performed on the selected content, this would save the user from having to select the same items again. It could also help users clearly see which content was updated. Just wanted to add that perspective while we wait for Graber’s input.
    Attaching patch if someone can work on select All.

  • 🇵🇱Poland Graber

    There’s the statement in the issue description:

    Checkboxes should remain checked after action completion.

    The question here is: why?
    I think this qualifies rather for a custom project-specific solution.
    I’d start from checking if you can hook into tempstore somehow and if not, just override the entire service and add your special cases.

    If more users of the module will need such a feature, it can be configurable I guess but this is the first such a feature request since.. 5, 10 or how many years already and the patch will definitely not do.

Production build 0.71.5 2024