Maintainer note

Please upgrade to the latest 4.3.x before upgrading to 4.4.0. More information in the release docs.

Sorry for inconvenience, 4.4.0 had a beta release (with a notice in Drupal Slack #contribute channel), a week later a RC and a week later a stable release so there were two weeks to test everything. Looks like nobody was interested then.

Problem/Motivation

Changes introduced in 4.4.0 added database updates however these got removed in the release.

https://git.drupalcode.org/project/views_bulk_operations/-/commit/ea0e24...
- This added views_bulk_operations_update_8036 to update the configuration to match schema.

https://git.drupalcode.org/project/views_bulk_operations/-/compare/4.3.4...
- The release removes all database updates and sets hook_update_last_removed to 8034.

https://git.drupalcode.org/project/views_bulk_operations/-/commit/ee38f9...
- This looks like the commit responsible. It also removed the views_bulk_operations_update_8035 update.

Proposed resolution

Reintroduce missing database updates.

Issue fork views_bulk_operations-3553049

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

joegl created an issue. See original summary.

joegl’s picture

joegl commented
Issue summary: View changes
joegl’s picture

joegl commented
Priority: Normal » Major
ressa’s picture

ressa
he/him
commented

Thanks for reporting this. Also, all earlier versions were set to not "Supported", resulting in warning emails, see #3553118: False warning about Views Bulk Operations (VBO) security update. This may cause more users to feel an urgency to update, even if it's not necessary.

graber’s picture

graber commented

Added info to the release notes to upgrade to latest 4.3.x prior to upgrading to 4.4.0.

graber’s picture

graber commented
Status: Active » Closed (won't fix)

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

graber’s picture

graber commented
Issue summary: View changes
joegl’s picture

joegl commented
Status: Closed (won't fix) » Needs work

I don't think you totally understood. The database update I'm referring to was never in a 4.3.x release. It was only in the dev version and should have been part of the next release.

joegl opened merge request !117

joegl’s picture

joegl commented
Status: Needs work » Needs review

Created a merge request to restore the update.

graber’s picture

graber commented

Oh dear 🤦‍♂️
I’ll handle it as soon as I’m back at my desk

  • graber committed 975ddee8 on 4.4.x authored by joegl 
    Issue #3553049 Restore 'Update force_selection_info configuration'...
graber’s picture

graber commented
Version: 4.4.0 » 4.4.x-dev
Status: Needs review » Fixed

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

joegl’s picture

joegl commented

Thanks Graber!

jwilson3’s picture

jwilson3
Primary language English
Location Ecuador
commented

I arrived here via release notes https://www.drupal.org/project/views_bulk_operations/releases/4.4.2

If the 4.3.x hook_update_Ns have been added back, is the warning in the issue summary above to update to the latest 4.3.x version still relevant? If not can it be removed? If its still needed could this warning be mentioned also all 4.4.x release notes pages?

joegl’s picture

joegl commented

4.3.x hooks were not added back, they were still removed (so the warning is still relevant) and upgrading to 4.3.4 is still necessary before jumping to 4.4.x. This was to restore a database update that was meant to be part of the new code and had never been released prior. I can't comment on the other bit about release notes, but probably not a bad idea?

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.