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

Fatal error on the Reports page after 5.0.0 update #29096

Closed
5 tasks done
ospiotr opened this issue Feb 10, 2021 · 5 comments
Closed
5 tasks done

Fatal error on the Reports page after 5.0.0 update #29096

ospiotr opened this issue Feb 10, 2021 · 5 comments

Comments

@ospiotr
Copy link

ospiotr commented Feb 10, 2021

Prerequisites (mark completed items with an [x]):

  • I have have carried out troubleshooting steps and I believe I have found a bug.
  • I have searched for similar bugs in both open and closed issues and cannot find a duplicate.

Describe the bug

Caused by #28799

I am using an official WooCommerce filter to disable WooCommerce Admin in my site:
add_filter( 'woocommerce_admin_disabled', '__return_true' );

After updating to WooCommerce 5.0, there is a fatal error on Reports page (the classic old reports):

Uncaught Error: Call to undefined function wc_admin_url() in /wp-content/plugins/woocommerce/includes/admin/views/html-admin-page-reports.php:17

Steps to reproduce the bug

  1. Use fresh WooCommerce 5.0 installation
  2. Disable WC Admin using an official WooCommerce filter
  3. Go to old Reports page
  4. Fatal error happens

Screenshots
image

Isolating the problem (mark completed items with an [x]):

  • I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
  • This bug happens with a default WordPress theme active, or Storefront.
  • I can reproduce this bug consistently using the steps above.

WordPress Environment

WC Version: 5.0.0
WP Version: 5.6.1
PHP Version: 7.4.12

@roykho
Copy link
Member

roykho commented Feb 10, 2021

Thanks for reporting. Fixed here 315c4de

@roykho roykho closed this as completed Feb 10, 2021
@kanlukasz
Copy link

When will you release this patch?

@dcx15
Copy link

dcx15 commented Feb 28, 2021

Fixed 17 days ago, but still not available. Any news on when 5.0.1 might be pushed live?

@superbmario
Copy link

I'm guessing this won't make it into a 5.0.1 and we should expect a fix in 5.1.0 on 8th March?

@roykho
Copy link
Member

roykho commented Mar 1, 2021

Yes so the fix will be apart of the 5.1 version release slated to go out on March 9th. Sorry for the inconvenience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants