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

Periodically patches will be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches from being posted simply close this issue (any status besides Active, Needs review or Needs work) or remove the "ProjectUpdateBotD10" tag from the issue.

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 or Needs work) 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.

  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 don't want new automated patches simply leave this issue open but remove the "ProjectUpdateBotD10" tag from the issue.

    You can use Drupal Rector yourself to make these patches.

    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 or Needs work) 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 may be useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

  1. Apply the patch in the comment by Project Update Bot.
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.

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 Infrastructure project issue queue using the component “Bot: Drupal Rector”.

CommentFileSizeAuthor
#2 disqus.1.x-dev.rector.patch620 bytesproject update bot

Issue fork disqus-3296968

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

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

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

heddn’s picture

Title: Automated Drupal 10 compatibility fixes » Drupal 10 && 11 compatibility fixes
Issue summary: View changes

This is far from automated fixes at this point. And we're now testing D10 and D11. As a bonus, all the tests return green and there's not much surfacing from phpstan. This _should_ be good to land.

rossb89’s picture

8.1.x isn't a supported version any more, The MR should be changed to be based against 2.0.x.

At the moment there are far too many changes reported because of being based on the 8.1.x branch.

For a view of the fork against 2.0.x where you can see the actual changes, https://git.drupalcode.org/issue/disqus-3296968/-/compare/2.0.x...329696...

aluzzardi’s picture

Status: Needs review » Needs work
jerech’s picture

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

jeremy1606 changed the visibility of the branch 3296968-automated-drupal-10 to hidden.

jerech’s picture

Version: 2.x-dev » 2.0.x-dev

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

chike’s picture

MR !17 worked for me.

Thanks.

mlncn’s picture

Status: Needs work » Needs review

So people searching on this JavaScript error find it, this issue will fix the critical error: Uncaught TypeError: $(...).once is not a function

Merge request 17 is off of 2.0.x now so it is ready for review!

bjcooper’s picture

Can confirm that MR 17 does also seem to address this jQuery once error referenced here: https://www.drupal.org/project/disqus/issues/3359581

it-cru’s picture

Could we mark this as RTBC and get a merge into 2.0.x-dev to make it easier for everyone to update to D11 and apply other maybe needed patches?

  • robloach committed ec349dd4 on disqus-3296968-3296968-d11
    Issue #3296968: Fix JavaScript variable name
    

  • robloach committed ec349dd4 on 2.0.x
    Issue #3296968: Fix JavaScript variable name
    
robloach’s picture

Status: Needs review » Reviewed & tested by the community
robloach’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

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