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:

  1. 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.

  2. 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.

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

  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.

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.

CommentFileSizeAuthor
#4 Screenshot 2023-02-09 at 9.43.14 AM.png262.01 KBrohan-sinha
#4 Screenshot 2023-02-09 at 9.42.50 AM.png1.33 MBrohan-sinha
#4 3297411-D10-Readiness.patch1.04 KBrohan-sinha
#2 image_slider.1.x-dev.rector.patch752 bytesproject update bot

Issue fork image_slider-3297411

Command icon 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:

About issue forks

Comments

Project Update Bot created an issue. See original summary.

project update bot’s picture

project update bot commented
Status: Active » Needs review
StatusFileSize
new image_slider.1.x-dev.rector.patch752 bytes

This 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.yml file 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

Bot run #139

This patch was created using these packages:

  1. mglaman/phpstan-drupal: 1.1.24
  2. palantirnet/drupal-rector: 0.13.0
project update bot’s picture

project update bot commented
Issue summary: View changes

Updating bot issue summary.See #3313904: Update project bot templates for RTBC status support and human interaction tips

rohan-sinha’s picture

rohan-sinha commented
Issue summary: View changes
StatusFileSize
new 3297411-D10-Readiness.patch1.04 KB
new Screenshot 2023-02-09 at 9.42.50 AM.png1.33 MB
new Screenshot 2023-02-09 at 9.43.14 AM.png262.01 KB

Uploading a patch for D10 readiness, verified on D10 environment, working fine[ screenshots attached ].

rohan-sinha’s picture

rohan-sinha commented
Status: Needs review » Reviewed & tested by the community

Reviewed the patch made by me, working fine.

urvashi_vora made their first commit to this issue’s fork.

urvashi_vora’s picture

urvashi_vora commented

Reviewed and tested the patch #4, works well for me as well.

LGTM, RTBC++

Committing the changes for helping the maintainer.

urvashi_vora opened merge request !2

drupaldope’s picture

drupaldope commented

I copied v. 1.3 to my Drupal 10.0.7
patched it

and then I enable the module from the "extend" page.

the next page shows "this page encountered an unexpected error"

the PHP error log contains:

[31-Mar-2023 13:48:12 Europe/Vienna] Uncaught PHP Exception Error: "Call to a member function getPath() on null" at C:\wamp64\www\***\web\core\modules\config_translation\src\ConfigNamesMapper.php line 247

My superficial investigation points to a missing route

dabley made their first commit to this issue’s fork.

dabley’s picture

dabley commented

I found that the upgrade_status module complains that image_slider is using the deprecated core/jquery.once library. This should be replaced by the core/once library (see https://www.drupal.org/node/3158256).

I have made the necessary change and pushed it to the issue fork.

Note: I cant find any usages of once functions in the image_slider code, so perhaps the library isnt actually needed?

arunkumarkit’s picture

arunkumarkit commented

Hi @drupaldope, dabley

Above issue fixed in this release: https://www.drupal.org/project/image_slider/releases/6.0.0

Thanks for your support.

arunkumarkit’s picture

arunkumarkit commented
Status: Reviewed & tested by the community » Closed (works as designed)
dabley’s picture

dabley commented

@arunkumarkit shouldn't the status of this issue be Fixed rather than "Closed (works as designed)"?

arunkumarkit’s picture

arunkumarkit commented
Status: Closed (works as designed) » Fixed

Status: Fixed » Closed (fixed)

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