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.

Comments

Project Update Bot created an issue. See original summary.

project update bot’s picture

Status: Active » Needs review
StatusFileSize
new406 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 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 #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

joseph.olstad’s picture

It's time ! Let's get this in. Due to this not being in, I have to perform a composer circus to get my composer build working with D10.

joseph.olstad’s picture

Issue summary: View changes

Here's the composer circus I'm using to get around the lack of a tagged release with D10 compatibility included. It's not that hard to do but it takes a bit of effort that would normally be simple.

Add this to your repo section in your composer.json file if you have a repo section you can add it in, if you don't have one, add a repo section, check with composer documentation online on how to do this if you've never done it.

{
      "type": "package",
      "package": {
        "name": "drupaloverride/private_content",
        "version": "dev-53138c26",
        "type": "drupal-module",
        "dist": {
          "type": "zip",
          "url": "https://git.drupalcode.org/api/v4/projects/project%2Fprivate_content/repository/archive.zip?sha=53138c26"
        }
      }
    }

Patch the workaround project invented in your composer.json (add this to your patches section):

    "drupaloverride/private_content": {
      "3289146 - D10 compatibility": "https://www.drupal.org/files/issues/2022-06-16/private_content.2.x-dev.rector.patch"
    },

composer require drupaloverride/private_content:'dev-53138c26'

If you are a composer guru this should be fairly quick to figure out. Otherwise, good luck, I recommend someone commit the above patch and tag/publish a release asap.

joseph.olstad’s picture

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

Thanks for the comment. So the module works on D10 for you with this patch?

joseph.olstad’s picture

Yes it does work.

adamps’s picture

StatusFileSize
new400 bytes
adamps’s picture

Status: Reviewed & tested by the community » Needs review
StatusFileSize
new814 bytes
new322 bytes
adamps’s picture

adamps’s picture

  • AdamPS committed af49841c on 8.x-2.x
    Issue #3289146 by AdamPS, joseph.olstad: Drupal 10 compatibility fixes
    
adamps’s picture

Status: Needs review » Fixed

Thanks

joseph.olstad’s picture

Thanks @AdamPS ! :)

joseph.olstad’s picture

@AdamPS , please tag a new release 8.x-2.0 and push it out :)

Thanks :)
If you want, you can assign me as co-maintainer and I can do this for you, however if you can do this for us that'd be great, makes it easier for people to upgrade to D10 if they can just go composer up -W

joseph.olstad’s picture

gisle’s picture

I now see that the dev-branch is Drupal 10 compatible. Great!

A simple content access module for Drupal 10 is much requested, and I believe this one is a good fit for this use case.

A tagged release for Drupal 10 would be most welcome.

joseph.olstad’s picture

@gisle, agreed, I seem to recall looking at the alternatives for our use case of a simple module and this one was best suited and was easy to set up.

adamps’s picture

Yes I agree, I'm working on it😃. I have checked the issue queue, and all looks good, so I propose to create a stable release.

joseph.olstad’s picture

Yes thanks

Status: Fixed » Closed (fixed)

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