🇦🇹Austria @aurelianzaha

aurelianzaha → made their first commit to this issue’s fork.

@larowlan
It would be great to backport the MR also to 10.3
if there is a way I can help on that, let me know

Create a MR out of the patch
https://www.drupal.org/project/drupal/issues/3080634#comment-14357338 🐛 Catch EarlyRendering Exception for REST-Resources Needs work

I would propose a slightly different approach, by marking the file with locale_translation_update_file_history() instead of locale_translation_status_save()

The patch attached

Patch https://www.drupal.org/project/drupal/issues/3080634#comment-14357338 🐛 Catch EarlyRendering Exception for REST-Resources Needs work applies to 10.2 as well and working fine

Andriy Khomych → credited aurelianzaha → .

Andriy Khomych → credited aurelianzaha → .

for some reason, I was not able to push the changes to the fork, attached the patch

aurelianzaha → created an issue.

attached is the patched re-rolled against 6.0.x

I was trying to reroll the patch the the fork, but failed to do it
attached is the re-roll against the latest 6.0.x

aurelianzaha → made their first commit to this issue’s fork.

aurelianzaha → made their first commit to this issue’s fork.

Hi,

I was able to reproduce the issue when having a view with 50+ items (or whatever the limit of the pager is) and having the sticky header option for the table.

This results in having 2 'select all' checkbox elements
and the JS event listener is attached only to the first one
tableSelectAll[index] = $(this).find('.select-all input').first();
which is the checkbox from the sticky header

MR created https://git.drupalcode.org/project/views_bulk_operations/-/merge_request...

aurelianzaha → made their first commit to this issue’s fork.

aurelianzaha → created an issue.

@drunken-monkey do you want maybe to make a new release that works width Drupal 10?

+1 to merge this and make a new release

thanks @drunken-monkey for the feedback

the re-ordering ->accessCheck(FALSE) has the purpose to silent the errors created by https://www.drupal.org/project/upgrade_status → when checking the D10 compatibility of the module (see screenshot)
if you don't agree with those changes I can revert them

fixed the assert as well

aurelianzaha → made their first commit to this issue’s fork.

D10 readiness MR merged
https://git.drupalcode.org/project/private_file_token/-/merge_requests/1

aurelianzaha → created an issue.

aurelianzaha → created an issue.

+1 to merge this

+1 to commit this

thanks for the feedback ranjith_kumar_k_u and smustgrave

in my case, the field is used to define the unpublishing date of a node (another use case would be a birthday field)
leaving empty means the node won't be unpublished (automatically)

I understand that the widget was designed to work this way, so I would create a custom widget for my use case

aurelianzaha → created an issue.

aurelianzaha → created an issue.

aurelianzaha → created an issue.