Automated Drupal 10 compatibility fixes

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.

Here's the composer circus I'm using:

{
      "type": "package",
      "package": {
        "name": "drupaloverride/private_content",
        "version": "dev-51138c26",
        "type": "drupal-module",
        "dist": {
          "type": "zip",
          "url": "https://git.drupalcode.org/api/v4/projects/project%2Fbutton_link/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.

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

Yes it does work.

Thanks

Thanks @AdamPS ! :)

@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

✨ Make form group optional Needs work

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.

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

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.

Yes thanks

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