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.

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:

Comments

Project Update Bot created an issue. See original summary.

project update bot’s picture

Status: Active » Needs review
StatusFileSize
new2.12 KB

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.12.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 #127

This patch was created using these packages:

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

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 this patch makes this module compatible with Drupal 10! 🎉
This patch updates 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

samitk’s picture

Assigned: Unassigned » samitk
Issue summary: View changes
Status: Needs review » Reviewed & tested by the community

I am reviewing #3

samitk’s picture

Assigned: samitk » Unassigned
StatusFileSize
new186.66 KB

I reviewed that patch, applied successfully. Moving to RTBC.

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

luke.leber’s picture

StatusFileSize
new3.49 KB

Given that #3 explicitly drops support for Drupal 8 in the info.yml file, the whole EventProxy thing that supports Symfony 3 and 4 concurrently is unnecessary.

There are also numerous problems with the patch in #3 that would make a site fail with fatal errors.

  1. The Event Dispatcher service's dispatch method has changed.
  2. drupal_get_path has been removed from Drupal 10.

Reviews can/should not be based on whether a patch applies. The bot wouldn't have posted a patch if it did not apply.

Quality reviews should be based on real user testing of the module.

My mistake! I reviewed the interdiff file from #3, not the patch!

That all said, I've updated the patch such that I was able to confirm that:

  1. The admin form loads properly and persists changes to active configuration
  2. A social media field can be added to a node and toggled on/off with the expected results
  3. A social media block can be added to a theme region and displays appropriately

No interdiff here. The original patch didn't really work.

This module could use some automated tests!

luke.leber’s picture

Status: Reviewed & tested by the community » Needs review

Setting NR for #9

chandra gowsalya kannan’s picture

I have applied patch #9 and checked in Drupal 9.5.7 , got below errors in drupal check

10/10 [============================] 100%

------ ------------------------------------------------------------------------------------------------------------
Line src\Form\SocialMediaAdminForm.php
------ ------------------------------------------------------------------------------------------------------------
261 Method Symfony\Contracts\EventDispatcher\EventDispatcherInterface::dispatch() invoked with 2 parameters, 1
required.
------ ------------------------------------------------------------------------------------------------------------

------ ------------------------------------------------------------------------------------------------------------
Line src\Plugin\Block\SocialSharingBlock.php
------ ------------------------------------------------------------------------------------------------------------
89 Method Symfony\Contracts\EventDispatcher\EventDispatcherInterface::dispatch() invoked with 2 parameters, 1
required.
139 Method Symfony\Contracts\EventDispatcher\EventDispatcherInterface::dispatch() invoked with 2 parameters, 1
required.
------ ------------------------------------------------------------------------------------------------------------

[ERROR] Found 3 errors

Resolved the above error in my patch and tested in D9.5.7 and D10 . Attached screenshot for reference. Review it and move to RTBC.

nishavaghela’s picture

Status: Needs review » Reviewed & tested by the community

I have reviewed the patch in comment #12 , it got applied successfully.
There are no compatibility errors found , thus moving the issue to RTBC.

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

luke.leber’s picture

Version: 8.x-1.x-dev » 2.0.x-dev

Hi @Chandra Gowsalya Kannan, I've taken a look at #12 and have made some observations:

1. I don't think that the interdiff between #9 and #12 matches. #9 adds this line.

+    $this->eventDispatcher->dispatch($event, 'social_media.add_more_link');

Your interdiff is seemingly removing this line:

-    $this->eventDispatcher->dispatch('social_media.add_more_link', $event);

which simply doesn't exist in #9.

2. We should be using the dependency injected dispatcher service instead of instantiating a new one.

Given the timeline and the degree of manual testing I've performed against #9, and given no evidence of manual testing against #12 and #13, I'm planning on committing #9 to the 2.0.x branch.

  • Luke.Leber committed 1c32f816 on 2.0.x
    Issue #3289788: Automated Drupal 10 compatibility fixes
    
luke.leber’s picture

Status: Reviewed & tested by the community » Fixed
luke.leber’s picture

luke.leber’s picture

kim.pepper’s picture

Luke.Leber credited neschi.

Luke.Leber credited Tritof.

luke.leber’s picture

Added additional issue credits from #3178056.

luke.leber’s picture

Copying over issue credits from #3169074 (outdated).

Status: Fixed » Closed (fixed)

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