Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecated Notices in WCPay 5.6.0 #5776

Closed
htdat opened this issue Mar 15, 2023 · 4 comments · Fixed by #9093
Closed

Deprecated Notices in WCPay 5.6.0 #5776

htdat opened this issue Mar 15, 2023 · 4 comments · Fixed by #9093
Assignees
Labels
category: core WC Payments core related issues, where it’s obvious. focus: checkout payments good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. needs prioritisation Triage finished and issues are ready for the following processing. priority: medium The issue/PR is medium priority—non-critical functionality loss, minimal effect on usability type: bug The issue is a confirmed bug.

Comments

@htdat
Copy link
Member

htdat commented Mar 15, 2023

Describe the bug

I've just reviewed debug.log from the provided testing site by GlobalStep p1678813826134229/1678768526.480299-slack-C011ENB20Q1 (with the main purpose of checking errors from the platform project #5321) and found out these notices.

Not urgent but I think we will need to fix them eventually.

The Automattic\WooCommerce\Admin\API\Options::get_options function is deprecated since version 3.1.

woocommerce_blocks_checkout_order_processed is deprecated since version 7.2.0! Use woocommerce_store_api_checkout_order_processed instead. This action was deprecated in WooCommerce Blocks version 7.2.0. Please use woocommerce_store_api_checkout_order_processed instead.

The Automattic\WooCommerce\Admin\API\Options::update_options function is deprecated since version 3.1.

Payment gateway with handle 'WCPAY_BLOCKS_CHECKOUT' has been deactivated in Cart and Checkout blocks because its dependency 'wc-blocks-registry' is not registered. Read the docs about registering assets for payment methods: https://github.com/woocommerce/woocommerce-blocks/blob/060f63c04f0f34f645200b5d4da9212125c49177/docs/third-party-developers/extensibility/checkout-payment-methods/payment-method-integration.md#registering-assets

The Automattic\WooCommerce\Admin\API\Options::get_options function is deprecated since version 3.1.

To Reproduce

  1. Go to '…'
  2. Click on '…'
  3. Scroll down to …'
  4. See error

Actual behavior

Screenshots

Expected behavior

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context

@htdat htdat added type: bug The issue is a confirmed bug. category: core WC Payments core related issues, where it’s obvious. needs prioritisation Triage finished and issues are ready for the following processing. good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. labels Mar 15, 2023
@Onyx808
Copy link

Onyx808 commented May 12, 2023

Site running PHP 8+ get the depricated and other warnings

( ! ) Deprecated: Return type of WCPay\Core\Server\Response::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /wp-content/plugins/woocommerce-payments/includes/core/server/class-response.php on line 49
--
( ! ) Deprecated: Return type of WCPay\Core\Server\Response::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /wp-content/plugins/woocommerce-payments/includes/core/server/class-response.php on line 60
--

@haszari haszari added the focus: misc or unknown Issues that need to be added to a focus area (aka "needs focus"). label Mar 11, 2024
@nerrad
Copy link

nerrad commented Jun 24, 2024

Hey folks, this seems like an odd one to have been sitting with no fix for over a year. It's surfacing for the community. (cc @vbelolapotkov for awareness).

@vbelolapotkov
Copy link
Collaborator

Thanks for the ping @nerrad , I'll try to bump its priority and assign to the best team.

@vbelolapotkov vbelolapotkov added type: technical debt This issue/PR represents/solves the technical debt of the project. and removed focus: misc or unknown Issues that need to be added to a focus area (aka "needs focus"). type: bug The issue is a confirmed bug. labels Jul 1, 2024
@FangedParakeet FangedParakeet added type: bug The issue is a confirmed bug. priority: medium The issue/PR is medium priority—non-critical functionality loss, minimal effect on usability focus: checkout payments and removed type: technical debt This issue/PR represents/solves the technical debt of the project. labels Jul 1, 2024
@timur27 timur27 self-assigned this Jul 11, 2024
@timur27
Copy link
Contributor

timur27 commented Jul 12, 2024

Quick update after reviewing all the notices/errors, as it's been a while since they were discovered and things have changed in some areas:

Hence, all the bullet points except for the last one were fixed at this point. The last point will be fixed by #9093.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: core WC Payments core related issues, where it’s obvious. focus: checkout payments good first issue The issue is a good candidate for the first community contribution/for a newcomer to the team. needs prioritisation Triage finished and issues are ready for the following processing. priority: medium The issue/PR is medium priority—non-critical functionality loss, minimal effect on usability type: bug The issue is a confirmed bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants