Plugin installation via 'set up marketing tools' fails

[janmckell]

Quick summary

Going through the WooCommerce setup asks if we want to install plugins, via 'Set up marketing tools', like MailPoet, but then says we’re not allowed to manage plugins, once we click into it.

Steps to reproduce

1. Started at WooCommerce option (in WP dashboard)
2. Began quick WooCommerce install flow
3. When clicking on 'set up marketing tools', I'm taken to a screen that recommends marketing extensions, but then I cannot install, re: MailPoet, for example.

What you expected to happen

I'd be able to install a marketing extension.

What actually happened

I was unable to make the purchase, since an error message popped up at the bottom of the screen, indicating that I could not install the plugin.

Context

No response

Browser

Mozilla Firefox

Simple/Atomic

No response

Other notes

No response

Reproducibility

Once

Severity

No response

Available workarounds?

No response

Workaround details

No response

[cpapazoglou]

@ianstewart it seems that WooCommerce is very dependant on other plugins. I can think of 2 different solutions:

• Hide sections that lead to installing non-marketplace plugins
• Change the messaging, including "Installing free plugins is available only in X, Y plans. Click here to upgrade."

[cpapazoglou]

Same happens with the onboarding flow and when trying to buy - install through WC.com

I believe the best course of action here is to update the code making sure that user has permissions to install plugins before suggesting so. @bgrgicak can you point us to the teams that could handle this in woocommerce and WC.com?

[bgrgicak]

@bgrgicak can you point us to the teams that could handle this in woocommerce and WC.com?

Team Alpha is responsible for the auto-install flow in Woo and on WCCOM.

[cpapazoglou]

Created a P2 p6JqRr-6Zk-p2 to discuss further.

[cuemarie]

Adding to Dotcom Bug Prioritization Board > ON HOLD, as the work around WooCommerce on lower tier plans is paused for now.

Installing plugins from the Woo setup flow on an AT site still works as expected