Automated Drupal 11 compatibility fixes for default_content

Created on 15 March 2024, 8 months ago
Updated 19 July 2024, 4 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

Fixed

Version

2.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: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 8 months ago
    13 pass
  • This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request 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 , even with these changes, this module is not yet compatible with Drupal 11.

    Currently Drupal Rector, version 0.20.0, cannot fix all Drupal 11 compatibility problems.

    Therefore these changes did not update the info.yml file for Drupal 11 compatibility.

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

    Debug info

    Bot run #11-115424

    This patch was created using these packages:

    1. drupal/upgrade_status: 4.1.0
    2. mglaman/phpstan-drupal: 1.2.7
    3. palantirnet/drupal-rector: 0.20.0
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 8 months ago
    13 pass
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 8 months ago
    13 pass
  • This comment was forced and has ignored the check if a change was already posted. This is only done when we want to update the issue without waiting for changes to happen.

    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 , even with these changes, this module is not yet compatible with Drupal 11.

    Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.

    Therefore, these changes did not update the info.yml file for Drupal 11 compatibility.

    The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.

    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-136651

    These packages were used to generate the fixes:

    1. drupal/upgrade_status: 4.1.0
    2. mglaman/phpstan-drupal: 1.2.10
    3. palantirnet/drupal-rector: 0.20.1
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 8 months ago
    13 pass
  • First commit to issue fork.
  • Merge request !46Drupal 11 compatibility. → (Merged) created by deepakkm
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Failed
    6 months ago
    Total: 163s
    #186964
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Failed
    6 months ago
    Total: 253s
    #186967
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Failed
    6 months ago
    Total: 184s
    #190412
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Failed
    6 months ago
    Total: 462s
    #190413
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Failed
    6 months ago
    Total: 203s
    #190417
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Failed
    6 months ago
    Total: 189s
    #190420
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Failed
    6 months ago
    Total: 37s
    #190654
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    Composer require-dev failure
  • Pipeline finished with Failed
    6 months ago
    Total: 39s
    #190657
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Failed
    6 months ago
    Total: 200s
    #190658
  • Status changed to Needs work 6 months ago
  • 🇮🇳India chandu7929 Pune

    @mishradeepak1991 - I verified MR 46 and can see following deprecations hence needs work.

    modules/contrib/default_content/tests/src/Kernel/ExporterIntegrationTest.php
    
    STATUS         LINE                           MESSAGE                           
    --------------------------------------------------------------------------------
    Fix later      26   Usage of deprecated trait                                   
                        Drupal\Tests\field\Traits\EntityReferenceTestTrait in class 
                        Drupal\Tests\default_content\Kernel\ExporterIntegrationTest.
                        Deprecated in drupal:10.2.0 and is removed from             
                        drupal:11.0.0. Use                                          
                        Drupal\Tests\field\Traits\EntityReferenceFieldCreationTrait 
                        instead.                                                    
    --------------------------------------------------------------------------------
    
    FILE:
    modules/contrib/default_content/tests/src/Kernel/MenuLinkContentNormalizerTest.p
    hp
    
    STATUS         LINE                           MESSAGE                           
    --------------------------------------------------------------------------------
    Fix later      19   Usage of deprecated trait                                   
                        Drupal\Tests\field\Traits\EntityReferenceTestTrait in class 
                        Drupal\Tests\default_content\Kernel\MenuLinkContentNormalize
                        rTest. Deprecated in drupal:10.2.0 and is removed from      
                        drupal:11.0.0. Use                                          
                        Drupal\Tests\field\Traits\EntityReferenceFieldCreationTrait 
                        instead.                                                    
    --------------------------------------------------------------------------------
    
    FILE:
    modules/contrib/default_content/tests/src/Kernel/ParagraphNormalizerTest.php
    
    STATUS         LINE                           MESSAGE                           
    --------------------------------------------------------------------------------
    Fix later      24   Usage of deprecated trait                                   
                        Drupal\Tests\field\Traits\EntityReferenceTestTrait in class 
                        Drupal\Tests\default_content\Kernel\ParagraphNormalizerTest.
                        Deprecated in drupal:10.2.0 and is removed from             
                        drupal:11.0.0. Use                                          
                        Drupal\Tests\field\Traits\EntityReferenceFieldCreationTrait 
                        instead.                                                    
    --------------------------------------------------------------------------------
    
    FILE:
    modules/contrib/default_content/tests/src/Kernel/TranslationNormalizerTest.php
    
    STATUS         LINE                           MESSAGE                           
    --------------------------------------------------------------------------------
    Fix later      19   Usage of deprecated trait                                   
                        Drupal\Tests\field\Traits\EntityReferenceTestTrait in class 
                        Drupal\Tests\default_content\Kernel\TranslationormalizerTest
                        . Deprecated in drupal:10.2.0 and is removed from           
                        drupal:11.0.0. Use                                          
                        Drupal\Tests\field\Traits\EntityReferenceFieldCreationTrait 
                        instead.                                                    
    --------------------------------------------------------------------------------
    
  • Status changed to Needs review 6 months ago
  • 🇮🇳India deepakkm

    @chandu7929 - There is a separate issue to fix those deprecations hence i reverted those commit and added it here - https://www.drupal.org/project/default_content/issues/3415901 📌 EntityReferenceTestTrait deprecated Needs review

  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Success
    6 months ago
    Total: 194s
    #191544
  • Status changed to RTBC 6 months ago
  • 🇮🇳India chandu7929 Pune

    Verified MR 46 change and its look good to me, hence RTBC.

  • Status changed to Needs work 6 months ago
  • 🇨🇭Switzerland berdir Switzerland

    D11 is not going to work with a phpstan deprecation like this:


    Line tests/src/Kernel/TranslationNormalizerTest.php
    ------ -----------------------------------------------------------------
    19 Usage of deprecated trait
    Drupal\Tests\field\Traits\EntityReferenceTestTrait in class
    Drupal\Tests\default_content\Kernel\TranslationormalizerTest:
    in drupal:10.2.0 and is removed from drupal:11.0.0. Use
    \Drupal\Tests\field\Traits\EntityReferenceFieldCreationTrait
    instead.

    Unfortunately, fixing this means we can no longer test on 10.1 and lower.

    One way to verify D11 test are actually working is to use a lenient configuration. like this: https://git.drupalcode.org/project/paragraphs/-/merge_requests/115/diffs..., then it should be able to install and only the tests that actually require those additional modules should fail.

  • 🇮🇳India deepakkm

    @berdir - There is a separate issue created for fixing these deprecations, kindly have a look at this - https://www.drupal.org/project/default_content/issues/3415901 📌 EntityReferenceTestTrait deprecated Needs review

  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • First commit to issue fork.
  • Pipeline finished with Failed
    6 months ago
    #192358
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Success
    6 months ago
    Total: 166s
    #192364
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Success
    6 months ago
    #192383
  • 🇮🇳India ankitv18

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

  • Status changed to Needs review 6 months ago
  • 🇮🇳India ankitv18

    MR!46 is ready for review ~~ I've made a fix of deprecation trait in this and its related issue i.e https://www.drupal.org/project/default_content/issues/3415901 📌 EntityReferenceTestTrait deprecated Needs review (If you merge this one first then I'll revert the changes in MR!46)

  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 6 months ago
    13 pass
  • Pipeline finished with Success
    6 months ago
    Total: 338s
    #192693
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 5 months ago
    14 pass
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 5 months ago
    14 pass
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 5 months ago
    14 pass
  • Pipeline finished with Skipped
    5 months ago
    #198389
  • Open in Jenkins → Open on Drupal.org →
    Core: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
    last update 5 months ago
    14 pass
  • Status changed to Fixed 5 months ago
  • 🇨🇭Switzerland berdir Switzerland

    I was a bit concerned about the hal related test fails I saw locally, but it's caused by hal, not default_content and it's fixed by compatible with Drupal 11 Needs review

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

  • 🇮🇳India vipin.mittal18 Greater Noida

    Hello Berdir,

    Thanks very much for development release of default_content module that help us to validate our module acquia_cms_starter depend on this module. It would be appreciated if you could let us know your timeline for releasing a pre/stable version of the default_content, especially since Drupal 11 stable is nearing its release date

Production build 0.71.5 2024