🇵🇱Poland @alorenc

The updates look good, and all jobs completed successfully without any issues.

It looks fine , thanks

README.md looks file but one job fails - cspell. Please add "_CSPELL_WORDS: 'blackfire, xhprof'" to .gitlab-ci.yml

Pagination sometimes disappears after specific user actions.
Steps to reproduce:
* Click on any page.
* Click on "Show inactive".
* Press Save for a selected translation
* Pagination disappears, but I expect the user to remain on the same page, with only the selected row being updated.

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

alorenc → changed the visibility of the branch project-update-bot-only to hidden.

First, we need to commit #3396336 as it fixes pipeline issues

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

alorenc → changed the visibility of the branch project-update-bot-only to hidden.

Moved to “Needs Work” because the current state generates a fatal error.

Can this ticket be merged, as it blocks #3433991?

I have performed some tests, and it generates a fatal error on both versions of private_messages (v3 and v4).

private_message v4
Fatal error: Declaration of Drupal\private_message_flood\Plugin\PrivateMessageConfigForm\PrivateMessageFloodPrivateMessageConfigForm::create(Symfony\Component\DependencyInjection\ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition) must be compatible with Drupal\private_message\Plugin\PrivateMessageConfigForm\PrivateMessageConfigFormBase::create(Symfony\Component\DependencyInjection\ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition):

private_message v3
Fatal error: Declaration of Drupal\private_message_flood\Plugin\PrivateMessageConfigForm\PrivateMessageFloodPrivateMessageConfigForm::validateForm(array &$form, Drupal\Core\Form\FormStateInterface $formState) must be compatible with Drupal\private_message\Plugin\PrivateMessageConfigForm\PrivateMessageConfigFormBase::validateForm(array &$form, Drupal\Core\Form\FormStateInterface $formState): void in /var/www/html/web/modules/repos/private_message_flood/src/Plugin/PrivateMessageConfigForm/PrivateMessageFloodPrivateMessageConfigForm.php on line 200

In both cases we have
Error: Call to undefined function Drupal\private_message_flood\Plugin\PrivateMessageConfigForm\user_role_names() in Drupal\private_message_flood\Plugin\PrivateMessageConfigForm\PrivateMessageFloodPrivateMessageConfigForm->buildForm() (line 81 of modules/repos/private_message_flood/src/Plugin/PrivateMessageConfigForm/PrivateMessageFloodPrivateMessageConfigForm.php).
which makes sense as user_role_names is no longer aviable in D11

First, we need to resolve/merge https://www.drupal.org/project/private_message_flood/issues/3501011 📌 Private message 4 compatibility fixes Active and issues should disappear.

alorenc → changed the visibility of the branch 3433991-automated-drupal-11 to hidden.

The search string is lost during the following steps:
* Click Translate from the toolbar.
* Paste, for example, "Behavior settings" into the search field.
* Press the Filter button.
* The content updates, but the entered search string is lost.

When I update the string at /admin/config/regional/babel, I can see a message.
However, when I use the modal (by clicking Translate from the toolbar), the messages are not displayed. Is this expected?

Fatal errors and my remarks were resolved.

Found another issue:
* /admin/config/regional/babel
* click on "Translate" from the top toolbar
* modal is displayed on top of /admin/config/regional/babel
* I clicked around and was redirected to babel/pager/ajax page
Do we want to create another follow up?

I have found another error.

Symfony\Component\HttpKernel\Exception\HttpException: The specified #ajax callback is empty or not callable. in Drupal\Core\Form\FormAjaxResponseBuilder->buildResponse() (line 67 of /var/www/html/web/core/lib/Drupal/Core/Form/FormAjaxResponseBuilder.php).

Steps:
* visit /admin/config/regional/babel
* type something in search box and press enter
* system logs a fatal error

Added remarks to MR

After enabling two languages on a fresh instance, I visited /admin/config/regional/babel and encountered the following fatal error:

The website encountered an unexpected error. Try again later.
AssertionError: assert(count($form['list']['#header']) === count($form['list'][$keys])) in assert() (line 252 of modules/repos/babel/src/Form/BabelTranslateForm.php).
Drupal\babel\Form\BabelTranslateForm->buildForm()
call_user_func_array() (Line: 528)

Improved GitLab CI to test code on another Drupal version.

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

alorenc → created an issue.

First, we need to resolve #3537760

alorenc → created an issue.

alorenc → created an issue.

Added some remarks/questions to MR

Performed manual tests for D11, enabled error_page_test and visited the following pages:
/error_page_test/exception: simulates an exception.
/error_page_test/fatal_error: simulates a fatal error.
/error_page_test/user_error: simulates a user error.
/error_page_test/php_notice: simulates a PHP notice.

Looks fine

Removed _TARGET_DB_VERSION in order to simplify

We do not set TARGET_CORE in our configuration.
I think this is a template infrastructure issue on Drupal.org's side. The warning will disappear once they complete the migration and remove all internal references to _TARGET_CORE from their CI templates.

alorenc → created an issue.

Please update ticket description and explain the fix.

I have enabled module on D11, next I have updated settings with
`
// Only if you don't use composer.
require_once 'modules/custom/error_page/src/ErrorPageErrorHandler.php';
set_error_handler(['Drupal\error_page\ErrorPageErrorHandler', 'handleError']);
set_exception_handler([
'Drupal\error_page\ErrorPageErrorHandler',
'handleException',
]);
// Log the UUID in the Drupal logs.
$settings['error_page']['uuid'] = TRUE;
`
what generated a fatal error on homepage

`
Fatal error: Cannot redeclare _drupal_error_handler_real() (previously declared in /var/www/html/web/core/includes/errors.inc:57) in /var/www/html/web/.../error_page/errors.inc on line 78
`

I don’t see a "Skip" button in the UI.
I assume that we need to add a button that will allow the user to change the active value for the selected row.

Manual testing completed. No issues found. Code appears stable and ready for merge.

Performed manual testing to verify JavaScript behavior.
Confirmed that auto-submit is triggered when:
* Pressing Enter
* Selecting a date from the calendar picker

Added BabelHookOrder as separate class to avoid class loading issues on Drupal 10

alorenc → changed the visibility of the branch 1.x-3533695 to hidden.

alorenc → changed the visibility of the branch 3533695-convert-procedural-hook to hidden.