Add Status Message after Bulk Editing Contents.

Yeah that makes sense, showing the results and checking the status. Could someone please prepare a proper MR?

I am working on this request.

I have created the MR for this. I have applied the success/failure messages by checking the number of successful and failed entities. And also applied the logger for failed entities. Please review once.
Thank You !!

It's working properly on my end and here is the screenshot. (This is my first contribution.)

Unfortunately, I see that the PHPUnit is failing. I will look into it to make it work.

Created a bit shorter version of the original MR, adds a status message after editing

Hi,

I installed and enabled the Views Bulk Edit module against 8.x-2.x-dev on my D10 site, and confirmed the Status message is now working after applying MR!33.

Please see the attached file for reference.

I'm moving this now to ‘RTBC’.

Thank you!

Thanks. I think we should improve the wording a bit. Any native EN speaker here?

I'd vote for something like

Successfully modified %total_count entities

. Any similar string in core?

Working on it.

Modifed the status message as per suggestion.

Attaching the screenshot for reference.

Thank you! Sadly both MR's still have failing tests and we should add tests for the new message to appear, please.
Code style is also incorrect.

Working on the code style and trying to make pipeline green.

Hi @anybody,
Fixed all the phpcs issues and made phpcs pass. But still there is phpunit failing. I have no prior experience of writing tests. Therefore, unassigning myself from the issue.

I am currently working on this at DrupalCon SG 2024 until the end of the day.

I fixed the test, but I made a mistake with the branch name (Sorry about that).

Great, thank you!

Hi @anybody,
I noticed that a new MR was generated for this issue which includes the changes I did in MR 33 previously. While I appreciate the progress that the issue has been fixed, I’d like to kindly request due credit for my contribution to this issue as it motivates me to continue contributing to Drupal.
Looking forward to your response!

@chhavi.sharma yes of course, sorry!

Thank you for this fix.
Hoping for a release.

Hopping for a tag release.
Thank you :)

Not really critical, I think... @rajab natshah did you test the current dev branch? Everything else fine? Then I'd be fine to tag a new release of course. Thanks for your help.

Thanks, Julian, for following up.

This issue has the fix committed for #3561886: Implicit nullable AccountInterface parameters for PHP 8.4 compatibility in Views Bulk Edit

---

Yes, using the commit as a patch in our projects
#3569371: Add a patch for the Views Bulk Edit module on Issue #3561886 : Implicit nullable AccountInterface parameters for PHP 8.4 compatibility
and
Add a patch for Views Build Edit module on Issue #3561886 : Implicit nullable AccountInterface parameters for PHP 8.4 compatibility in Views Bulk Edit #228

The PHP 8.4 what important in our case
( as Drupal ~11.3.0 and ~10.6.0
#3554384: Recommend PHP 8.4 for Drupal 11.3 and 10.6 )
As we are moving with PHP 8.4 and ~11.3.0 in most projects

@rajab natshah what about #3563973: Deprecated nullable parameter? Sorry very busy currently.

Thank you for your time Julian.

• Both created a new issue.
• then created an issue fork
• But noticed that it was already fixed in the DEV branch.

So we only managed with a patch

Created: 7 Dec 2025 : #3561886: Implicit nullable AccountInterface parameters for PHP 8.4 compatibility in Views Bulk Edit ( I closed mine as wont fix as it was already fixed in this issue - managing with local patches, and a patch from the commit)
Created: 18 Dec 2025 : #3563973: Deprecated nullable parameter

@rajab natshah so TL;DR: 3.x-dev is fine, we just need a tagged release, right?

Yes for sure, the dev was fine.
I had 5 testing rounds before the release
and
2 post release testing rounds ( ~11.3.0, and ~10.6.0 )

Thanks for the release, Julian, and your time today.

Thank YOU @rajab natshah it's always a pleasure! :)