{"version":"2.1.281","anchor":"plugin-sync-consent-bound-elsewhere-and-unknown-binding","canonical_anchor":"plugin-sync-consent-bound-elsewhere-and-unknown-binding","heading":"Plugin sync consent: bound-elsewhere and unknown binding","tier":"internal","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/plugin-sync-consent-bound-elsewhere-and-unknown-binding","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Plugin sync consent: bound-elsewhere and unknown binding\n\nThe plugin memory check now tells a binding 'elsewhere' apart from an 'unknown' one, and reports 'switched_off' when the feature is disabled\n\n**Unclear.** The finding does not say what a binding is here or where a user would see these results.\n\n**What**\n\nThe check behind plugin sync consent now separates more cases:\n\n- `bound_elsewhere`: the binding is somewhere else.\n\n- unknown: it cannot tell where the binding is.\n\n- `switched_off`: the feature is disabled.\n\n**Why**\n\nBefore this change, some of these situations were reported the same way. The separate results make it clearer why plugin syncing is or is not going ahead.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}