New to the community? Start here

[Configuration Settings] List of settings _not_ applied?

2

Is there a concise listing of what settings are Not implemented across sites when a saved Configuration is applied?

For example, the screenshots here show the features that are applied with specific named configurations. But these configs are old. We are updating the primary config sites and then will save/apply the configs to other sites.

But when we are done, how do we know what we missed? Well, the brute force method is to look at the new list of settings (for each plugin!) that wil be applied to sites, and then look through settings pages for configs that are Not detailed.

Sounds like fun, rite? :not:

The better approach is to have a single list that hundreds of people here can look at for the thousands of sites supported, so that every admin doesn’t need to figure this out all on their own – because Time = Money. ( :hourglass_flowing_sand: = :dollar: )

Actually we can do this quite quickly. The question is … does a list of not-shared settings already exist for each plugin? If I missed existing docs I will humbly apologize than thank those who have kept them up. :poop:

Thanks.

[attachments are only viewable by logged-in members]

[attachments are only viewable by logged-in members]

Thu, 24 Apr 2025 1:11:05
  • Tony G
    • Mr. LetsFixTheWorld

    I know we can also see applied settings from plugins, and that does include settings that have not been activated/enabled.

    The issue is that a specific setting might not be added into this configuration feature, so it can’t tell us what it doesn’t know.

    For example: a Smush config shows that it has Bulk Smush Email Notification Inactive. Great, that tells us that the setting will be deactivated when the config is applied to another site.
    But there is another Bulk Smush setting for “Image Sizes”, and it isn’t mentioned in the saved config list. What do we do with this information? (Go ahead, check it out, I’ll wait until you get back. :musical_score: :musical_note: )

    As you see :grinning: the setting defaults to All, and it may be set to Custom along with individual options.

    Does no mention of the feature mean the default setting is All and is therefore not listed, so it will be transparently applied to a target system that gets these configs? Hmm, probably not.

    Or do we infer that this one feature isn’t included in the settings applied to another site. So if we want another site to generate All thumbnails for images, or only selected ones, we will need to manually check each site for this setting after applying the configuration set. This seems more likely.

    “That’s a bug, thanks for reporting, we’ll fix it in a couple years, or not.”

    OK, whatever. In the meantime we just need to know what the rules are so that we can keep our sites in sync until specific issues are resolved.
    And then a new feature will be added, the configs won’t list related settings, and we’ll be wondering why sites behave differently with (what we think are) the same configs. So the policy that we’d hope for would be that all new settings mandate a new ticket to update config options. But we know that will never happen or never be followed.

    So I come back to … can someone just be assigned to create lists until the situation changes?

    This is exactly like the situation with IP addresses used by WPMU DEV to connect to our sites. A situation that was resolved with some dedicated effort by staff. ( Thank you!!! )

    That’s the challenge laid out with all of its ugly nuances. What can be done about it?

    Why the pessimism? Because I stopped using this great feature over a year ago specifically because of this, and now we’re looking at new and existing sites and still faced with the challenge of how to get them and keep them in sync. I’ve asked for an API so that we could do this ourselves – that didn’t fly. So I’m back to asking if there is something already in the works to address this, or if we can somehow collaborate to improve the situation. I don’t care what the solution is – but leaving issues permanently unresolved is not a solution.

    Thanks.

  • Nebu John
    • FLS

    Hi Tony G ,

    Currently, there isn’t a centralized or concise list that outlines which settings are not applied across sites when a saved config is used.

    Would you like to move this ticket to the features and feedback section? This would allow the relevant team to review the request, and other users would also have the opportunity to vote on it, which can help bring more visibility and potentially prioritize it.

    Best Regards,
    Nebu John