[WPMU DEV Dashboard] Turn off automatic upgrading to Pro when installing Dashboard

1

If you install the WPMU DEV Dashboard plugin on a website that has the Free DEV plugins installed, upon activation and logging in to a DEV account it automatically upgrades them all to Pro.

This happens without prompting you for confirmation – it just does it. What if you didn’t want to upgrade the plugins?

There’s no way to easily downgrade the plugins, either. You have to uninstall the Pro version with settings and configuration saved, then install the free plugin version. In the few moments when you’re doing this for Forminator for example, your forms are broken and the shortcodes are shown on the frontend.

And the kicker? When you remove the Dashboard plugin, there is no way to downgrade all Pro plugins to free.

Two feature requests:

1) Stop automatically upgrading free plugins to Pro without consent from the user, upon installing and logging in to the Dashboard plugin

2) In the Dashboard plugin, offer a “Downgrade all DEV plugins to Free” option. This is useful when parting ways with a client, such that you can downgrade the plugins and disconnect the Dashboard from your Hub.

  • Nithin Ramdas
    • Support Wizard

    Hi Phil ,

    I do see that providing the option to choose which plugins to switch to Pro versions would be helpful and will make sure to bring to our teams attention as a feature request.

    2) In the Dashboard plugin, offer a “Downgrade all DEV plugins to Free” option. This is useful when parting ways with a client, such that you can downgrade the plugins and disconnect the Dashboard from your Hub.

    In general, once the WPMU DEV Dashboard plugin is deactivated or removed, the Pro features won’t be accessible anymore. So the plugin would be behaving similarly to the free version. Only when the WPMU DEV Dashboard plugin is activated are the Pro features accessible.

    So, having an option to downgrade doesn’t bring much change based on the existing workflow, or do you notice it’s useful in any specific use case? If yes, is it possible to provide further info so we can bring these to our team’s attention to see what further improvements could be explored?

    Kind Regards,
    Nithin