Problem/Motivation
Hello project maintainers,
This is an automated issue to help make this module compatible with Drupal 10.
To read more about this effort by the Drupal Association, please read: The project update bot is being refreshed to support Drupal 10 readiness of contributed projects
Patches will periodically be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches 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 "ProjectUpdateBotD10" tag from the issue to stop the bot from posting updates.
The patches 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:
- Accept automated patches 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 "ProjectUpdateBotD10" tag is left on this issue, new patches 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 patches 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 patches. The bot will still post new patches then if there is a change in the new generated patch compared to the patch that the bot posted last. Those changes are then up to humans to integrate.
- Leave open but stop new automated patches.
If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated patches, remove the "ProjectUpdateBotD10" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated patches again, add back the "ProjectUpdateBotD10" tag.
- 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 patches will be posted here.
If the issue is reopened, then new automated patches will be posted.
If you are using another issue(s) to work on Drupal 10 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
- Apply the latest patch in the comments by Project Update Bot or human contributors that made it better.
- Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
- Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.
Providing feedback
If there are problems with one of the patches 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.
| Comment | File | Size | Author |
|---|---|---|---|
| #21 | 3297809-21.patch | 13.73 KB | andypost |
| #21 | interdiff.txt | 3.26 KB | andypost |
| #19 | panels_everywhere-n3297809-19.patch | 11.27 KB | damienmckenna |
| #19 | panels_everywhere-n3297809-19.interdiff.txt | 614 bytes | damienmckenna |
| #17 | 3297809-17.patch | 10.85 KB | andypost |
Issue fork panels_everywhere-3297809
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
project update bot commentedThis is an automated patch generated by Drupal Rector. Please see the issue summary for more details.
It is important that any automated tests available are run with this patch and that you manually test this patch.
Drupal 10 Compatibility
According to the Upgrade Status module, even with this patch, this module is not yet compatible with Drupal 10.
Currently Drupal Rector, version 0.13.0, cannot fix all Drupal 10 compatibility problems.
This patch does not update the
info.ymlfile for Drupal 10 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Debug info
This patch was created using these packages:
Comment #3
project update bot commentedThis is an automated patch generated by Drupal Rector. Please see the issue summary for more details.
It is important that any automated tests available are run with this patch and that you manually test this patch.
Drupal 10 Compatibility
According to the Upgrade Status module, even with this patch, this module is not yet compatible with Drupal 10.
Currently Drupal Rector, version 0.13.1, cannot fix all Drupal 10 compatibility problems.
This patch does not update the
info.ymlfile for Drupal 10 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Debug info
This patch was created using these packages:
Comment #4
project update bot commentedUpdating bot issue summary.See #3313904: Update project bot templates for RTBC status support and human interaction tips
Comment #5
andypostIt needs to change composer.json and info file
Comment #8
vacho commentedI added to MR changes at composer.json and .info. please review.
Comment #9
andypostComment #10
andypostSomehow tests not started for MR, checking patch
Comment #11
andypostLots of deprecated calls revealed
Comment #12
andypostComment #13
andypostFew tests still fail
Comment #14
andyposttest failure are from ctools #3332913: Fix PHP 8.2 deprecation notices and D10.1 compatibility
But the failure caused by added
assert()AssertionError: Route page_manager.page_view_some_page_id_some_variant_id has broken overridden_route_name in /var/www/html/modules/contrib/panels_everywhere/src/Routing/PanelsEverywhereRouteSubscriber.php:109Comment #15
andypostnew test without assert
Comment #16
andypostFront page test has changed since #3111409: Add new Olivero frontend theme to Drupal 9.1 core as beta
Comment #17
andypostcurly braces could be removed from last variable (phpstorm complains about it), added to MR and here's interdiff and patch to run tests
Comment #18
andypostThis comes from Olivero (core 9.1)
Comment #19
damienmckennaTrying to see if this will fix the following error: Creation of dynamic property Drupal\panels_everywhere\Plugin\DisplayVariant\PanelsEverywhereDisplayVariant::$conditionManager is deprecated
Comment #20
andypostIt should be inherited in
ctools/Plugin/DisplayVariant/BlockDisplayVariant.phpand fixed via #3332913: Fix PHP 8.2 deprecation notices and D10.1 compatibilityComment #21
andypostLooking at implementation this fixes needed to unit test to pass, interdiff vs #17 as *.2 compatibility require to fix ctools
Comment #22
andypostneeded for 10.1 - future proof compatibility from SF
Comment #23
andypostGonna merge as MR and release new alpha
Comment #25
andypostFiled follow-up #3358594: Fix overridden_route_name should not be empty