After updating drupal/views_bulk_operations (4.3.4 => 4.4.1) I got a fatal error.

Fatal error: Declaration of Drupal\moderated_content_bulk_publish\Plugin\Action\AssignOwnerModeratedNode::defaultConfiguration() must be compatible with Drupal\views_bulk_operations\Action\ViewsBulkOperationsActionBase::defaultConfiguration(): array in /var/www/html/web/modules/contrib/moderated_content_bulk_publish/src/Plugin/Action/AssignOwnerModeratedNode.php on line 121

A fix will be provided.

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:

Comments

ruslan piskarov created an issue. See original summary.

ruslan piskarov’s picture

Assigned: Unassigned » ruslan piskarov
Issue summary: View changes

ruslan piskarov’s picture

Assigned: ruslan piskarov » Unassigned
Status: Active » Needs review

Fixed in MR !55.

joseph.olstad’s picture

Reviewing now to see if this affects 2.0.x

joseph.olstad’s picture

@ruslan piskarov, are you running PHP 8.4 by chance?

sbubaron’s picture

I'm having the same issue:
Drupal 10.5.4
PHP 8.3.25
Moderated Content Bulk Publish 3.0.0-rc3
Views Bulk Operations 4.4.2

While running update.php
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /update.php/start?id=81&op=do_nojs&op=do
StatusText: parsererror
ResponseText:
Fatal error: Declaration of Drupal\moderated_content_bulk_publish\Plugin\Action\AssignOwnerModeratedNode::defaultConfiguration() must be compatible with Drupal\views_bulk_operations\Action\ViewsBulkOperationsActionBase::defaultConfiguration(): array in /var/www/html/web/modules/contrib/moderated_content_bulk_publish/src/Plugin/Action/AssignOwnerModeratedNode.php on line 121

joseph.olstad’s picture

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.

joseph.olstad’s picture

Only affects 3.0.x

Status: Fixed » Closed (fixed)

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