[FEATURE REQUEST] – Comma Separated CSS Exclusion Classes

The exclusion classes work great, with wzlw-no-icon-wrapper being used for container exclusions and the wzlw-no-icon-class works great on individually anchors beautifully. The problem I’m running into is edge cases, where a certain block was re-used throughout the site. The process of finding them, wrapping them and adding the exclusion class is an undertaking, particularly if there are a lot of instances. Since these site-wide elements share a common CSS class, it would be so much easier if I could just add it via the admin, and have that CSS class part of the exclusions. The request is to expose the exclusion fields in the UI and to make them comma separated so there is a possibility of custom CSS exclusions. I can foresee all the code behind this, so I understand this is a large ask. It would make integrating this into the site much easier, and allow for some real fine-tuning via classes. At the moment I’m relying on domain exclusions to catch some of the edge cases, but that is a catch-all, and I’d prefer to be more surgical about it. Thanks for the great plugin Ajay! This topic was modified 3 weeks, 6 days ago by Ronald Huereca . Reason: Clarifying feature request title The page I need help with: [ log in to see the link] Currently you can customise the class name for inclusion/exclusion in the settings page – new feature I added in v1.2.0. Am I correct to understand that this field should be a comma-separated set vs a single name? I think that should be doable. Yes, having the fields be comma separated would be epic. I had this filed here: https://github.com/WebberZone/webberzone-link-warnings/issues/4 Will implement this in v1.4 @ronalfy This feature has been implemented in v1.4 which I released over the weekend.