Do not access change_feature_enable() statically. Closes #43175.

[helgatheviking]

Changes proposed in this Pull Request:

Do not access change_feature_enable() statically.

Closes #43175..

How to test the changes in this Pull Request:

Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions:

1. Should be able to access site now without fatal error.

Changelog entry

• Automatically create a changelog entry from the details below.

Significance

• Patch
• Minor
• Major

Type

• Fix - Fixes an existing bug
• Add - Adds functionality
• Update - Update existing functionality
• Dev - Development related task
• Tweak - A minor adjustment to the codebase
• Performance - Address performance issues
• Enhancement - Improvement to existing functionality

Message

Fix fatal error. Do not access change_feature_enable() statically.

Comment

[github-actions]

Hi ,

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[kdevnel]

The code looks good - I see this pattern in other places. Apologies for not using the method I saw elsewhere here.

That said, I can't replicate the issue being resolved here. I rebuilt and tried with both the standard and block product editor. No fatals I could see.

[andfinally]

This PR is having problems with the automated builds – probably because it's using a forked branch. I don't know a better way to resolve it than to copy Kathy's changes to a new PR: #43428. We'll merge that one. Thanks very much for the fix @helgatheviking! 🙌

[helgatheviking]

The build tooling has gotten way to complex for me, but happy to help. Maybe y'all can update the docu on how to submit a PR that passes the build process.