- Issue created by @project update bot
- last update
about 1 year ago Composer require-dev failure 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.1, 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-121090This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- last update
about 1 year ago Composer require-dev failure - last update
12 months ago Composer require-dev failure 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-137198These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.10
- palantirnet/drupal-rector: 0.20.1
- last update
12 months ago Composer require-dev failure - Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.2 & MySQL 8
43:18 43:18 Queueing 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.3, 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-199781These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- Open on Drupal.org βCore: 10.2.1 + Environment: PHP 8.2 & MySQL 8
43:06 43:06 Queueing - π©πͺGermany Anybody Porta Westfalica
Drupal 11 is out and compatibility is important!
- π©πͺGermany Grevil
grevil β changed the visibility of the branch project-update-bot-only to hidden.
- Merge request !11Issue #3431903: Automated Drupal 11 compatibility fixes for media_migration β (Open) created by Grevil
- π©πͺGermany Grevil
Unsure, how the backwards compatibility should be handled inside this, as it isn't a "normal" module. This simple version fix should be all we need to make the module functional again.
To bring the Tests up to D11 standards, we still need to apply (and adjust) the test changes from https://www.drupal.org/files/issues/2024-06-18/media_migration.1.x-dev.r... β and adjust the "StringInputStream" calls, if we want to remove D8/D9 compatibility:
Instantiation of deprecated class
Masterminds\HTML5\Parser\StringInputStream: since 2.4, to
remove in 3.0. Use a string in the scanner instead.Otherwise, the attached patch, will make it D11 ready.
- π©πͺGermany Anybody Porta Westfalica
Ok let's first fix this simple and then prepare a 2.x branch in a separate issue. Currently this block D11 upgrades!
RTBC for the simple solution.
- First commit to issue fork.
- First commit to issue fork.
- πΊπΈUnited States joegraduate Arizona, USA
Remaining GitLab CI composer test failure is blocked by the require-dev dependency on
drupal/entity_embed
not having a D11 compatible release yet. - π©πͺGermany Anybody Porta Westfalica
π Automated Drupal 10 compatibility fixes Needs review rector adds a trait to the tests, should we copy that over and close the D10 issue already?
- heddn Nicaragua
This is mostly postponed on getting entity_embed compatible. But while we are waiting for that, there are still some obvious failures, both in phpstan and in the unit tests that should be rectified to help keep this moving. We should investigate if we move to the new version of
Masterminds\HTML5\Parser\StringInputStream
and what version of that we should support. Secondly, we should fixFileEntitySourceFieldInstanceTest
and any other failures of similar nature. - π©πͺGermany Anybody Porta Westfalica
@heddn: See π Drupal 7 to Drupal 11 migration runs forever Active for a major issue in D11 - could you maybe review that one?
Please decide, if we should incorporate these changes here or keep them separate. Afterwards indeed we should fix the tests, as written above.
- π©πͺGermany Grevil
π Drupal 7 to Drupal 11 migration runs forever Active isn't finished yet anyway and the current MR there, doesn't solve that issue as explained in the comments.
- π©πͺGermany Grevil
This should be it. Let's wait for entity_embed to get official D11 compatibility.
- π©πͺGermany Anybody Porta Westfalica
Thanks for the fixes @grevil! Hopefully entity_embed will become D11 compatible soon...
- π©πͺGermany Grevil
HA, no way. We actually run into π Drupal 7 to Drupal 11 migration runs forever Active through the tests now!
ERROR: Job failed: execution took longer than 1h0m0s seconds
@heddn, so it actually makes sense now, to merge π Drupal 7 to Drupal 11 migration runs forever Active and this issue!
- π©πͺGermany Anybody Porta Westfalica
@heddn, so it actually makes sense now, to merge #3494209: Drupal 7 to Drupal 11 migration runs forever and this issue!
Merge now and proceed here also fixing that issue? (To simplify testng).
Important note is: The other issue is still unsolved and we have not found the root cause yet.
Leaving for @heddn to decide how to proceed. We could also copy the D11 changes from here over to the other issue for now to keep them separate for now...
- Status changed to Postponed
27 days ago 1:05pm 6 March 2025 - π«π·France musa.thomas France π«π·
hello there,
I read that some people already try this module on D11 but how ? did u download the module then require each dependencies inside the composer.json (also change the .info )?
Should I wait this issue to be ready ?
we need it as soon as possible specially with the end of life of drupal 7 and lots projects require this migration. - πΊπΈUnited States mortona2k Seattle
@musa.thomas - here's how you can use an issue fork as the source: https://jaybeaton.com/blog/how-use-version-module-drupal-issue-fork-comp...
- π©πͺGermany Grevil
@musa.thomas you can simply go to the latest commit via the gitlab UI and add a ".diff" at the end of the URL. This will give you the plain diff (patch). Then you can simply add this patch as you desire (e.g. through using cweagans/composer-patches).
I commented in the other issue, how I got a D7 to D11 media_migration to work. It is a hacky workaround, but it seems to do the job just fine:
Media Migration Patches:
- The D11 compatibility patch
- The dirty early return fix, avoiding an exception, which stops the migration
Drupal core Patches:
- πΊπΈUnited States trackleft2 Tucson, AZ πΊπΈ
@musa.thomas Also, you need to use drupal-lenient if would like to install on Drupal 11 via composer as far as I can tell https://www.drupal.org/docs/develop/using-composer/using-the-lenient-com... β
- πΊπΈUnited States trackleft2 Tucson, AZ πΊπΈ
Entity embed has had Drupal 11 support since 2 February 2025 https://www.drupal.org/project/entity_embed/releases/8.x-1.7 β
- Merge request !15Draft: Resolve #3431903 "Automated drupal 11 trackleft2" β (Open) created by trackleft2
- πΊπΈUnited States trackleft2 Tucson, AZ πΊπΈ
trackleft2 β changed the visibility of the branch 3431903-automated-drupal-11-trackleft2 to hidden.
- πΊπΈUnited States trackleft2 Tucson, AZ πΊπΈ
I haven't been able to figure this out.