v3.0 feedback

  • Resolved Gal Baras

    (@galbaras)


    2 years, 10 months ago

    The recent update, v3.0, is brilliant. It includes many very useful new features and allows far greater control over what the plugin does.

    Just a few comments, though:

    1. This is no longer a WooCommerce-specific plugin, so its settings page should appear under Settings. Alternatively, the more generic settings should be under Settings, and plugin-specific settings can be added into each respective plugin’s admin page
    2. On sites that run the Classic Editor and/or Classic Widgets plugin, block bloat should be disabled by default (both Gutenberg’s and WooCommerce’s)
    3. The plugin should only include settings for active plugins. For example, there’s no point cluttering the admin pages with Jetpack settings, if that plugin isn’t installed on the site. It just creates, well, bloat ??
    4. Similarly, there’s no point offering settings for things that are already handled on the site, e.g. disabling XML-RPC via a security plugin or custom code
    5. The s.w.org prefetch is used by the emoji script. Therefore, removing the prefetch can be part of the “Remove emoji styles and scripts” option

    All the best and thanks again!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Disable Bloat

    (@disablebloat)

    Hello @galbaras

    Thank you for your extensive feedback. We will take it into account while working on the new version of the plugin!

    1. We spent a lot of time thinking about the location of the plugin settings menu. We didn’t want to add another top-level menu in your WordPress admin, as it would be another additional element in your WordPress dashboard. We tried to keep it simple. So, do you think it would be better to add a new top-level menu element or add it under WordPress Settings? Or maybe in the Tools section? What do you think?

    2-5: these are great ideas for plugin improvements, thank you. Stay tuned for updates.

    Thread Starter Gal Baras

    (@galbaras)

    1. A top-level admin menu has the benefit of quicker navigation into each admin sub-page, which is now a tab, but since most of the plugins whose bloat you disable already have admin interfaces, you can split those sub-pages and integrate them into each of those plugins in its “native” way, i.e. almost seamlessly.

    This is especially easy with single settings, like those for ACT or WPML.

    2-5. Thank you for being so open to feedback ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘v3.0 feedback’ is closed to new replies.