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:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Project Update Bot created an issue. See original summary.

Project Update Bot’s picture

Status: Active » Needs review
FileSize
3.92 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 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

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 #143

This patch was created using these packages:

  1. mglaman/phpstan-drupal: 1.1.25
  2. palantirnet/drupal-rector: 0.13.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, even with this patch, this module is not yet compatible with Drupal 10.

Currently Drupal Rector, version 0.13.1, 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 #145

This patch was created using these packages:

  1. mglaman/phpstan-drupal: 1.1.25
  2. palantirnet/drupal-rector: 0.13.1
Project Update Bot’s picture

fathima.asmat’s picture

Assigned: Unassigned » fathima.asmat
Issue summary: View changes
Issue tags: +Drupal 10 porting day

I'm going to test this and review as part of D10 porting day Nov.

fathima.asmat’s picture

  • Applied rector patch from #4 but had some issues in D10 beta.
  • Amended the patch to include the version compatibility in info yml and added the access check to entity query. Patch attached below.
  • Upgrade status doesn't flag any more issues
 [notice] Processing /var/www/html/web/modules/contrib/view_unpublished.

================================================================================
View Unpublished, --
Scanned on Sat, 11/19/2022 - 12:03

No known issues found.
  • Manually tested the module on both D10 beta and D9.5. On D10.
  • I was successfully able to rebuild the permissions on both D9 and D10.
  • I could successfully tick the permissions for content editor user role to view unpublished content on both D9 and D10.
  • I was successfully able to see the unpublished content when logging in as content editor on both D9 and D10.
  • I have attached screenshots of my test results.
fathima.asmat’s picture

Assigned: fathima.asmat » Unassigned
vinaymahale’s picture

Status: Needs review » Reviewed & tested by the community

Reviewed the code from patch provided in #7
Code looks good!
Module works as expected on D10.
Setting to RTBC

james.williams’s picture

Fixes for the access check in the entity query were also provided over in #3281519: Install helper entity query without access check specified results in deprecation warning. I recommend that user (richard.thomas) be given issue credit here too, as & when this is committed.

james.williams’s picture

Status: Reviewed & tested by the community » Needs review
FileSize
613 bytes
5.34 KB

In fact... the fix from #3281519: Install helper entity query without access check specified results in deprecation warning looks much better - it explicitly skips the access check, which makes far more sense, given that this code is quite deliberately there to find unpublished content!

Here's an updated patch.

yashingole’s picture

I have reviewed and checked Patch #11 this works for drupal 9.4 and drupal 10.0. and 10.0.1
Screenshots of the compatibility on 9.4 and the Permission page on 10 have been attached for reference:

vinaymahale’s picture

Please change the status to RTBC if the patch works properly and there are no more errors

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

AaronBauman’s picture

Status: Needs review » Reviewed & tested by the community

Created an issue fork so that i can test the install / require and it works.

j-vee’s picture

+1 works.

Can this be published now that D10 has been out for a while?

xeM8VfDh’s picture

thanks so much for the work here, would love a release :)

stijnhau’s picture

A New release of this module would be so nice

xeM8VfDh’s picture

I messaged the maintainers, hopefully someone will have time in the near future. Thanks again to everyone involved :)

KlemenDEV’s picture

RTBC (tested, seems to work fine) from my side too, hoping for the release

xeM8VfDh’s picture

I just wanted to check in on this, would love to see it merged and released! Thanks everyone for the help!

Victonator’s picture

+1
Merge request #21 works!

ressa’s picture

Adding related issue #3345720: Offering to co-maintain view_unpublished, hopefully the module can soon be Drupal 10 ready :)

ressa’s picture

Title: Automated Drupal 10 compatibility fixes » Automated Drupal 10 compatibility fixes for view_unpublished

Adding project name in title.

xeM8VfDh’s picture

I've just tested upgrading my site to drupal 10 with this module installed running the latest patch (using these instructions) and everything seems to be working fine

Chandra Gowsalya Kannan’s picture

FileSize
1008 bytes

Tested patch #12 and it is works fine. That patch makes the module D10 compatible and Drupal check errors are ignorable which I attached here.

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

tobiasb’s picture

Status: Reviewed & tested by the community » Fixed

<3

xeM8VfDh’s picture

🥳

Status: Fixed » Closed (fixed)

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