Automated Drupal 11 compatibility fixes for simple_recaptcha

Created on 30 May 2024, 7 months ago

Problem/Motivation

Hello project maintainers,

This is an automated issue to help make this module compatible with Drupal 11.

Changes will periodically be added to this issue that remove deprecated API uses. To stop further changes from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD11" tag from the issue to stop the bot from posting updates.

The changes will be posted by the Project Update Bot โ†’ official user account. This account will not receive any issue credit contributions for itself or any company.

Proposed resolution

You have a few options for how to use this issue:

  1. Accept automated changes until this issue is closed

    If this issue is left open (status of Active, Needs review, Needs work or Reviewed and tested by the community) and the "ProjectUpdateBotD11" tag is left on this issue, new changes will be posted periodically if new deprecation fixes are needed.

    As the Drupal Rector project improves and is able to fix more deprecated API uses, the changes posted here will cover more of the deprecated API uses in the module.

    Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot changes. The bot will still post new changes then if there is a change in the new generated patch compared to the changes that the bot posted last. Those changes are then up to humans to integrate.

  2. Leave open but stop new automated changes.

    If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated changes, remove the "ProjectUpdateBotD11" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated changes again, add back the "ProjectUpdateBotD11" tag.

  3. Close it and don't use it

    If the maintainers of this project don't find this issue useful, they can close this issue (any status besides Active, Needs review, Needs work and Reviewed and tested by the community) and no more automated changes will be posted here.

    If the issue is reopened, then new automated changes will be posted.

    If you are using another issue(s) to work on Drupal 11 compatibility it would be very useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

  1. Apply the latest patch in the comments by Project Update Bot โ†’ or human contributors that made it better.
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.

Using the merge request

  1. Review the merge request and test it.
  2. Thoroughly test the changes. These changes are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the merge request, create a new branch and merge request and work from there.

Warning: The 'project-update-bot-only' branch will always be overwritten. Do not work in that branch!

Providing feedback

If there are problems with one of the changes posted by the Project Update Bot โ†’ , such as it does not correctly replace a deprecation, you can file an issue in the Drupal Rector issue queue โ†’ . For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Project analysis issue queue โ†’ .

๐Ÿ“Œ Task
Status

Needs review

Version

1.0

Component

Code

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @project update bot
  • Open in Jenkins โ†’ Open on Drupal.org โ†’
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update 7 months ago
    38 pass
  • This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.

    It is important that any automated tests available are run and that you manually test the changes.

    Drupal 11 Compatibility

    According to the Upgrade Status module โ†’ these changes make this module compatible with Drupal 11! ๐ŸŽ‰
    Therefore these changes update the info.yml file for Drupal 11 compatibility.

    Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot โ†’ to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

    Debug information

    Bot run #11-185727

    These packages were used to generate the fixes:

    1. drupal/upgrade_status: 4.3.1
    2. mglaman/phpstan-drupal: 1.2.11
    3. palantirnet/drupal-rector: 0.20.1
  • Open in Jenkins โ†’ Open on Drupal.org โ†’
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update 7 months ago
    38 pass
  • Open in Jenkins โ†’ Open on Drupal.org โ†’
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update 7 months ago
    38 pass
  • This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.

    It is important that any automated tests available are run and that you manually test the changes.

    Drupal 11 Compatibility

    According to the Upgrade Status module โ†’ these changes make this module compatible with Drupal 11! ๐ŸŽ‰
    Therefore these changes update the info.yml file for Drupal 11 compatibility.

    Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot โ†’ to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

    Debug information

    Bot run #11-188815

    These packages were used to generate the fixes:

    1. drupal/upgrade_status: 4.3.2
    2. mglaman/phpstan-drupal: 1.2.11
    3. palantirnet/drupal-rector: 0.20.2
  • Open in Jenkins โ†’ Open on Drupal.org โ†’
    Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
    last update 7 months ago
    38 pass
  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia kim.pepper ๐Ÿ„โ€โ™‚๏ธ๐Ÿ‡ฆ๐Ÿ‡บSydney, Australia

    kim.pepper โ†’ made their first commit to this issueโ€™s fork.

  • Pipeline finished with Failed
    4 months ago
    Total: 311s
    #259771
  • Pipeline finished with Failed
    4 months ago
    Total: 684s
    #259779
  • Pipeline finished with Failed
    4 months ago
    Total: 286s
    #259821
  • Pipeline finished with Failed
    4 months ago
    Total: 231s
    #259838
  • Pipeline finished with Failed
    4 months ago
    Total: 268s
    #259855
  • Pipeline finished with Failed
    4 months ago
    Total: 215s
    #259899
  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia kim.pepper ๐Ÿ„โ€โ™‚๏ธ๐Ÿ‡ฆ๐Ÿ‡บSydney, Australia

    I've tried to bump this along by adding a gitlabci build and fixing the phpcs and cspell errors. However, I'm not sure about the eslint warnings and the phpunit test fails.

  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia kim.pepper ๐Ÿ„โ€โ™‚๏ธ๐Ÿ‡ฆ๐Ÿ‡บSydney, Australia
  • Pipeline finished with Failed
    4 months ago
    Total: 251s
    #259910
  • This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.

    It is important that any automated tests available are run and that you manually test the changes.

    Drupal 11 Compatibility

    According to the Upgrade Status module โ†’ these changes make this module compatible with Drupal 11! ๐ŸŽ‰
    Therefore these changes update the info.yml file for Drupal 11 compatibility.

    Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot โ†’ to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.

    Debug information

    Bot run #11-321467

    These packages were used to generate the fixes:

    1. drupal/upgrade_status: 4.3.6
    2. mglaman/phpstan-drupal: 1.3.1
    3. palantirnet/drupal-rector: 0.20.3
  • First commit to issue fork.
  • Merge request !22Drupal 11 compatibility โ†’ (Open) created by abhinavk
  • ๐Ÿ‡ต๐Ÿ‡ฑPoland sandboxpl Poland ๐Ÿ‡ต๐Ÿ‡ฑ

    The merge request is compatible enough to make it all work, but I see the js tests failing and the issue is following:

    1) we switch to recaptcha iframe and click the checkbox, it seems that it somewhat has been clicked:
    https://issue.pages.drupalcode.org/-/simple_recaptcha-3451320/-/jobs/374...
    2) yet on the next screen we can see that checkbox is empty again:
    https://issue.pages.drupalcode.org/-/simple_recaptcha-3451320/-/jobs/374...

    The generated output of recaptcha checkbox is following:

    <span class="recaptcha-checkbox goog-inline-block recaptcha-checkbox-unchecked rc-anchor-checkbox recaptcha-checkbox-clearOutline" role="checkbox" aria-checked="false" id="recaptcha-anchor" tabindex="0" dir="ltr" aria-labelledby="recaptcha-anchor-label">
    	<div class="recaptcha-checkbox-border" role="presentation">
    		
    	</div>
    	<div class="recaptcha-checkbox-borderAnimation" role="presentation">
    		
    	</div>
    	<div class="recaptcha-checkbox-spinner" role="presentation">
    		<div class="recaptcha-checkbox-spinner-overlay">
    			
    		</div>
    	</div>
    	<div class="recaptcha-checkbox-checkmark" role="presentation"></div>
    </span>
    

    And what seems to be missing here is:
    1) Element class remains recaptcha-checkbox-unchecked while it should become recaptcha-checkbox-checked
    2) Aria attribute aria-checked remains false , while it should be switched to true

    It seems that final step of 3 failing js tests is not working with current markup/behavior of recaptcha widget things we can try:
    1) Click on element with ID = recaptcha-anchor and not class = recaptcha-checkbox
    2) optionally wait until aria-checked attribute has been really changed to true , and/or element class has been successfuly changed to recaptcha-checkbox-checked

    Inspiration:
    https://github.com/remarkablemark/remarkablemark.github.io/blob/master/_...
    https://git.drupalcode.org/project/recaptcha/-/blob/8.x-3.x/tests/src/Fu...

  • ๐Ÿ‡ต๐Ÿ‡ฑPoland sandboxpl Poland ๐Ÿ‡ต๐Ÿ‡ฑ

    ah the gitlab-ci.yml file is added via fork , so this test won't trigger the pipeline

  • Pipeline finished with Failed
    about 5 hours ago
    Total: 294s
    #373120
  • Merge request !23[#3451320] Drupal 11 compatibility โ†’ (Open) created by kim.pepper
  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia kim.pepper ๐Ÿ„โ€โ™‚๏ธ๐Ÿ‡ฆ๐Ÿ‡บSydney, Australia

    It seems the Automated Drupal 11 compatibility bot force pushes over our MR.

    I've created a new one.

  • Pipeline finished with Failed
    about 5 hours ago
    Total: 156s
    #373139
  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia kim.pepper ๐Ÿ„โ€โ™‚๏ธ๐Ÿ‡ฆ๐Ÿ‡บSydney, Australia

    The others can be closed by a project owner.

  • Pipeline finished with Canceled
    about 4 hours ago
    Total: 77s
    #373152
  • Pipeline finished with Failed
    about 4 hours ago
    Total: 220s
    #373154
  • Pipeline finished with Failed
    about 4 hours ago
    Total: 230s
    #373161
  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia kim.pepper ๐Ÿ„โ€โ™‚๏ธ๐Ÿ‡ฆ๐Ÿ‡บSydney, Australia

    I was able to reproduce the test fail locally, but wasn't able to work out what the cause is.

    There are a few eslint errors too which could clean up the javascript but I assume that can be done in a follow up.

Production build 0.71.5 2024