- Issue created by @project update bot
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 theinfo.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-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- First commit to issue fork.
- Merge request !12Issue #3434168: Drupal 11 compatibility fixes for remote_stream_wrapper... β (Open) created by jrglasgow
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 theinfo.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-217342These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.4
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- First commit to issue fork.
- πΊπ¦Ukraine pingwin4eg Zaporizhia πΊπ¦
Re: MR !12
Stream wrapper must not have a constructor. Because this breaks
fopen()
and alike functions:[error] ArgumentCountError: Too few arguments to function Drupal\remote_stream_wrapper\StreamWrapper\HttpStreamWrapper::__construct(), 0 passed and exactly 1 expected in Drupal\remote_stream_wrapper\StreamWrapper\HttpStreamWrapper->__construct() (line 53 of .../web/modules/contrib/remote_stream_wrapper/src/StreamWrapper/HttpStreamWrapper.php) #0 [internal function]: Drupal\remote_stream_wrapper\StreamWrapper\HttpStreamWrapper->__construct()
Look at core implementations of
StreamWrapperInterface
- they all use static calls to\Drupal::service(...)
or similar. - πΊπ¦Ukraine pingwin4eg Zaporizhia πΊπ¦
pingwin4eg β changed the visibility of the branch 2.x to hidden.
- πΊπ¦Ukraine pingwin4eg Zaporizhia πΊπ¦
Working on removing constructor from stream wrapper.
- πΊπ¦Ukraine pingwin4eg Zaporizhia πΊπ¦
pingwin4eg β changed the visibility of the branch project-update-bot-only to hidden.
- πΊπ¦Ukraine pingwin4eg Zaporizhia πΊπ¦
PhpUnit previous major (Drupal: 10.3.6, PHP 8.1.30) and next minor (Drupal: 11.1.0-dev, PHP 8.3.13) both pass on all tests except one for HttpMimeTypeGuesserTest, but that should be fixed by π Fix mime-type guesser for Drupal >= 10.3.2 Active .
I'm also going to manually test this MR in one of my projects in the near future. And I'm thinking (not sure) - whether the auto-testing for file functions (fopen, etc.) is needed.
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 theinfo.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-392907These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.6
- mglaman/phpstan-drupal: 1.3.2
- palantirnet/drupal-rector: 0.20.3
- πΊπΈUnited States yorchperaza Denver
Hello! Is there any estimate of obtaining the compatibility merge and being able to have a Drupal 11 version of the module? I need help with something, I am available for anything.
- πΊπ¦Ukraine pingwin4eg Zaporizhia πΊπ¦
@pawelgorski87 Why don't you read issue comments? Please read them, and revert your breaking changes.
- π΅π±Poland Pawelgorski87
@pingwin4eg, right sorry. Constructor removed.
- π΅π±Poland Pawelgorski87
@pingwin4eg I used Your patch for Guesser. Thank you.
Now all pipelines passed. Please test and review. - π΅π±Poland gpietrzak WrocΕaw
I reviewed the code and tested the module locally. I changed the image media type to accept remote streams and successfully added some new items. It worked fine (provided the image styles are not configured to use webp).
- π·π΄Romania Andras_Szilagyi
Looks good, works fine also in my tests
- First commit to issue fork.
- πΊπΈUnited States yorchperaza Denver
Is there any estimate to get this merge into the dev module?
- π§πͺBelgium msnassar
RTBC++
I have tested it with media_avportal https://www.drupal.org/project/media_avportal/issues/3431855 π Automated Drupal 11 compatibility fixes for media_avportal Needs review . All works as expected.