Automated Drupal 10 compatibility fixes

Confirming that the patch provided by the @project-update-bot fixes the issue.

I've created a new MR.

Anyone that could help me get this reviewed and eventually approved/merged?

thanks for the MR, halth. looks good to me, but I'm a first-time contributor and not sure how to 'officially' submit a review - does this count or do I need to do something in gitlab?

Hi Alyssa! Thanks for reaching out.

You can contribute to this just by confirming you've tested the patch/MR above and flagging that it works for you.
That reinforces the Reviewed & tested by the community status, increasing the level of confidence on maintainers to accept it.

However, only an official project maintainer can merge the MR into the project and release a new version.
Unfortunately, they haven't paid attention to this issue yet.

I've tried reaching out to them on Drupal Slack directly, without success.

I think the best we can do for now is wait.

In case you can't wait on them, here are a few options you have to get around the D10 incompatibility issue:

- Make use of Composer Drupal Lenient to "whitelist" this module, so the version compatibility constraint won't prevent you from upgrading to Drupal 10:

"drupal-lenient": {
            "allowed-list": ["drupal/path_file"]
        }

- Apply the MR above as a patch using cweagans/composer-patches:

"patches": {
            "drupal/path_file": {
                "Issue #3289025: Automated Drupal 10 compatibility fixes": "https://www.drupal.org/files/issues/2022-06-16/path_file.1.x-dev.rector.patch"
            }
}

If this project gets abandoned moving into the future but you still need the functionality, you could also turn it into a "custom contrib" module, which pretty much consists of removing the Composer Dependency for this module, moving it to modules/custom and treating it as a custom project.

I hope this sheds some light on your way.

Thanks so much, Heitor! My site authors rely on this module so I really appreciate the extra upgrade recommendations - didn't know about Composer Drupal Lenient, which sounds like it might solve this and a couple of my other module upgrade problems :)

Confirming that I have tested the patch provided by the @project-update-bot and it fixes the issue.

Also confirming the patch in #2 📌 Automated Drupal 10 compatibility fixes RTBC works with Drupal 9.5.10. The Merge request in #5 📌 Automated Drupal 10 compatibility fixes RTBC does not work because of a syntax issue with the ^ symbol.

After adding patch #2 getting issue as " Adding non-existent permissions to a role is not allowed. The incorrect permissions are "View published Path file entity entities".

Is there any hope this module will ever have an official release for version 10? Has it been abandoned?

Is there any more information on if there will be an official d10 compatible release?

Rohit.Mns → made their first commit to this issue’s fork.