WebberZone Link Warnings v1.4.0: Wildcard domain exclusions, multiple class support and more

When I shipped WebberZone Link Warnings version 1.3.0, the JavaScript scan started covering links across the full page. But two gaps remained. The excluded domains list was only respected by PHP content processing — the JS scan ignored it entirely. And the four CSS class settings each accepted a single class name, which was limiting when mapping to existing markup. Version 1.4.0 closes both.

Wildcard support for excluded domains

You can now add wildcard entries to the excluded domains list using *.example.com syntax. A wildcard entry matches any subdomain of that domain, but not the base domain itself.

So *.example.com would match docs.example.com, api.example.com, and support.example.com — but not example.com on its own. Plain entries continue to match only the exact domain.

To exclude a domain and all its subdomains, add both:

example.com
*.example.com

This works in both PHP content processing and the sitewide JavaScript scan.

Excluded domains now honoured by the JS scan

This was a consistency gap that’s now fixed. PHP processing respected your excluded domains list and left those links alone. The JavaScript scan did not. A link to partner.example.com in your navigation menu, you would still get flagged as external, even if partner.example.com was in your exclusions list.

From v1.4.0, the excluded domains list — including any wildcard entries — is passed to the frontend and used by the JS scan on page load. Links to excluded domains are now ignored consistently, whether they appear in post content or in menus, footers, and widgets.

Multiple class names per CSS class setting

All four CSS class settings now accept comma-separated values. Previously, each setting only accepted one class name. Now you can enter several, and any of them will trigger the relevant behaviour.

The four settings this applies to:

  • Suppress Icon Class (default: wzlw-no-icon)
  • Suppress Icon Wrapper Class (default: wzlw-no-icon-wrapper)
  • Force External Class (default: wzlw-force-external)
  • Force External Wrapper Class (default: wzlw-force-external-wrapper)

This is useful if your theme or page builder already applies its own class names to affiliate or partner links and you want those to map directly, without adding a second class to your markup.

Upgrade notes

If you’ve been relying on excluded domains to suppress warnings on links in navigation menus or widget areas, check those areas after updating. Previously, the JS scan would still process those links regardless of your exclusions. After this update, it won’t.

The wildcard syntax is new, not a change to existing behaviour. Plain domain entries still match the exact domain only. If you previously assumed example.com also covered sub.example.com, it didn’t — and still doesn’t. Add *.example.com alongside it if you need subdomain coverage.

Clear your site cache after updating to make sure the updated JavaScript loads.

Leave a Reply

Your email address will not be published. Required fields are marked *