Skip to content

eCommerce plan: "No access" on Plugins area on websites that upgraded to eCommerce  #51263

Open

Description

I've been seeing two incidents about this since last week so I decided to open GH issue here. Feel free to point me to the right direction/right repo! Thank youuu!

Reports:

First report:
p9F6qB-6DQ-p2

Second report:
p9F6qB-6Eu-p2

However, I can't replicate this issue (I upgraded my test site to eCommerce plan and I able to access the Plugins area after the website is upgraded to eCommerce plan) so it might be happening on some sites.

What happened on the user's website is:

  • User upgraded the website to eCommerce plan
  • They found themselves unable to finish WooCommerce Store set-up and/or access Plugins area (WEBSITE.COM/wp-admin/plugins.php)

What the user expected to happen

WooCommerce Store set up finished properly and they should be able to access Plugins and Themes area.

What actually happened

  • WooCommerce Store gave out error:
    Could not install code, message, data plugin, woocommerce_rest_cannot_update, Sorry, you cannot manage plugins., [object Object]

  • "Oops, you are not authorized to see this page" when they are trying to access Plugins area

  • User is not authorized to activate plugins message on Blog RC

What HEs have tried and didn't work

HEs have checked:

  • The user in question is set as Administrator ✅
  • at_options on the website, when checked on CLI, displayed the proper plan (ecommerce) ✅
  • Jetpack is connected ✅ (some HEs even reconnected Jetpack several times and removed + readded the user)
  • Role reset ✅
  • Run Jetpack sync ✅
  • Cache flush ✅

And all the above didn't work.

What worked?

Plan switcheroo from SA. We found that this method works:

  • Add non-regular/1 year eCommerce plan (most preferably: eCommerce BIYEARLY plan, this to ensure eCommerce plan features are intact on the website)
  • Remove the regular (1 -year) eCommerce plan
  • At this point, the website should be eCommerce Biyearly plan
  • Re-add regular (1-year) eCommerce plan to the website
  • Remove the eCommerce Biyearly plan

Then, everything works properly.

Does this happen on simple or atomic sites or both?

Atomic

Level of impact (Does it block purchases? Does it affect more than just one site?)

Medium to High, I guess? This is the second issue I noticed since March 19 (the first incident). Problem is, I can't replicate it. I wonder if this is related with user, the fact I'm a Super Admin (HE,) or websites that created before date XXYYZZ.

Reproducibility (Consistent, Intermittent) Leave empty for consistent.

Intermittent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Plans: eCommerceTriagedTo be used when issues have been triaged.User ReportThis issue was created following a WordPress customer report[Feature] Plans & UpgradesAll of the plans on WordPress.com and flow for upgrading plans.[Pri] Normal[Type] Bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions