• In WooCommerce 3.3.5 and WordPress 4.9.5 I was trying to update extensions.

    I would try to click update on an extension and it would redirect me to plugin update page and then it would immediately tell me the plugin was updates to the latest version immediately. It also directed me back to the Plugins page and not WooCommerce extensions page. If I tried to update the plugin again it would send me on the same loop.

    It was only after I clicked the update button on the extensions page that it said: Authentication and Subscriptions caches refreshed successfully than I was actually able to update the plugin.

    See Screencast of this experience:

    While I was able to update all three plugins in this work around method, this is far from a great user experience for the following reasons.

    1. There is no connection, no notification in the tried and true Plugin page for WordPress Plugins. The only way you know there is an update to these plugins is the red number notification on the drop down for extensions. Hypothetically if I didn’t hover over the WooCommerce tab I would never see the notification for plugin updates on these extensions.

    2. You are redirected to the Plugin page even after you update the WooComm extension. Which has no listing and no reference to any WooComm extensions. I realize there are reasons why developers put the plugins in the Extensions page as appose to plugins but to the average user of WooCommerce this would be very confusing. Can we either have one or the other? Not a poorly handled combination of both?

    A version of this also appear in the WooCommerce github issue system. I am reporting here for more eyes on what I think is an important issue.
    https://github.com/woocommerce/woocommerce/issues/19831

Viewing 1 replies (of 1 total)
  • Laurena Rehbein

    (@lrehbein)

    Automattic Happiness Engineer

    Hi @rdall,

    Thank you for adding it GitHub – I see it’s being addressed there!

    I will mark this as resolved. Appreciate your input on this!

Viewing 1 replies (of 1 total)
  • The topic ‘Confusing UX for Update to Extensions’ is closed to new replies.