Problem/Motivation

When I run some tests in Drupal 9^, I get the following deprecation notice:
$modules property must be declared protected
See: https://www.drupal.org/node/2909426

Steps to reproduce

Run the webform/modules/webform_access/tests/src/Functional/WebformAccessSubmissionViewsTest.php and see the deprecation notice mentioned above.

Proposed resolution

Change the visibility properties of the variables to protected.

Issue fork webform-3213630

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

paulocs created an issue. See original summary.

paulocs’s picture

Assigned: paulocs » Unassigned
Status: Active » Needs review
StatusFileSize
new102.89 KB

First try.

paulocs’s picture

StatusFileSize
new1.22 KB
new100.88 KB

WebformGroupBrowserTestBase, WebformGroupUserInterfaceTest and WebformGroupSubmissionAccessTest could not be addressed because GroupBrowserTestBase of the group module still have public static $modules.

jrockowitz’s picture

Title: $modules property in tests must be declared protected » [Drupal 9.x] $modules property in tests must be declared protected
guilhermevp’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new15.22 KB

Patch address D9 standards accordingly within the possibilities. As stated, some public declarations remain.

jrockowitz’s picture

Status: Reviewed & tested by the community » Postponed

I think this patch has to be postponed until Drupal 9.x is the only supported version. BTW, this is what I prefixed the title with [Drupal 9.x]

jrockowitz’s picture

Status: Postponed » Needs review
StatusFileSize
new105.15 KB
jrockowitz’s picture

StatusFileSize
new104.51 KB
jrockowitz’s picture

StatusFileSize
new103.75 KB
jrockowitz’s picture

StatusFileSize
new103.14 KB
paulocs’s picture

Will next webform release support drupal 9 only?

jrockowitz’s picture

I think I am going to be nice to people still on Drupal 8 and not require Drupal 9.x until next year.

paulocs’s picture

so if this issue is committed, it will break the tests in Drupal 8, won't it?

jrockowitz’s picture

Status: Needs review » Postponed

Yep. We might want to create a [meta] ticket to support only Drupal 9.x and track all the issues that can be resolved when we only support D9.

paulocs’s picture

paulocs’s picture

jrockowitz’s picture

Status: Postponed » Needs work

We need to move the patch into a branch and create a merge request.

jrockowitz’s picture

Status: Needs work » Reviewed & tested by the community

jrockowitz’s picture

Version: 6.x-dev » 6.2.x-dev

  • jrockowitz committed 54463b5 on 6.2.x
    Issue #3213630 by jrockowitz, paulocs, guilhermevp: [Drupal 9.x] $...
jrockowitz’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

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