New to the community? Start here

[Defender Pro] Centralized management of plugin configuration

0

Would love centralized management of the plugin configuration for Defender Pro, but also for Hummingbird Pro and Smush Pro via the hub :slight_smile:. That would make WPMU Dev’s awesome new hosting much more scalable for clients like me who support a growing number of small businesses through WPMU Dev’s hosting and plugin solutions.

Thu, 13 Feb 2020 19:51:20
More Defender Pro discussions
Defender Pro
  • Predrag Dubajic
    • Support

    Hi Jollity Web ,

    Something like that would certainly be a time saver for multiple sites connected in Hub, and I have good news as we have something like that on our to-do list already :slight_smile:

    I’m not sure on the specifics yet and if it would be a centralized option or an option to have predefined settings that you could “push” on selected site(s), it’s still something discussed internally but it’ll definitely help with speeding things up :slight_smile:

    Best regards,
    Predrag

  • Lauren with jollity.io
    • The Incredible Code Injector

    That is wonderful news!! I’m moving over to Defender from a security plugin/platform that did have centralized management including push/pull configuration options. Here are some things I liked and miss:
    1. A pre-set “template” of configuration options could be saved. After setting it up on one site, I’d be prompted (or could go to a specific menu area) right in the plugin within the site and say “save these settings as a template”, give the template a unique name, and I was done! Then, next time I’d install the plugin on a new site, it would give me the option of pulling in settings from a template.

    2. I could save multiple templates. This was huge as I have clients at different hosting plan levels. Years ago before SSL was commonplace, for example, I had a template for SSL clients and one for non-SSL clients with different configurations. Today I’d probably have a template for different themes since sometimes they will have a conflict. For example, I could have a template for “clients with Divi sites”.

    3. I could change to a template configuration later, which was AWESOME and appreciated. So, for example, I could go to my oldest “legacy” clients who had a bunch of random settings applied as they were created before I’d standardized my security configurations, and I could click “apply X template security settings” and it would update everything automatically.

    4. I could use this same setup to automatically apply white labeled profiles. I miss this perk a TON from my old setup. I logged in one time, uploaded my logo, desired label and footer text one time, and then chose to apply the white-labeled profile to any sites I wanted within the system. Now, with WPMU Dev, I’m logging into every single client’s sites, adding my own logo to their media library (a bit weird), and re-copying and pasting the text into every single site.

    I don’t mean to complain – I switched to WPMU Dev for very good reasons and I’m happy with the change overall. The centralized management is probably the biggest thing I miss about my old system, so I figured since I had experience I’d share since it sounds like it’s being discussed internally. I hope this helps!