That doesn't seem right.
It's the iframely plugin, I don't know why it's using window.open instead of just target=_blank. Maybe some kind of tracking thing?
Well I don’t use that plugin. So, not sure where to look to isolate for a bug report.
it's been a while
I've created a plugin for email domain-name filter specification (whitelists, blacklists, both):
It's possible to specify just any patterns for domain-name matching, like shown within the examples.
It utilizes a matching module (ns-matcher) written by myself because I haven't found any matching modules for order-relevant tasks.
So if you find any bugs, please report them
Comments (shown with
//) are not allowed within the actual syntax (yet).
email.example.com // Allow email.example.com email.*.example.com // Allow email.XYZ.example.com **.email.abc.example.com // Allow email.abc.example.com and all (deep) sub-domains !email.abc.example.com // Deny email.abc.example.com (sub-domains are still allowed)
Blacklists using negative patterns:
** // Allow everything !**.example.com // Deny example.com and all (deep) sub-domains email.example.com // Allow email.example.com
I hope this will be useful, at least I needed it myself
Btw I know the plugin name might be misleading due to the possibility of blacklists/mixtures as well, but I did publish after a long coding session xD sorry.
Awesome! I'm sure some of our clients would like to see this activated as well
Good to know so much active dev on node BB. We made a good decision choosing Node bb for our forum.
Welcome back @frissdiegurke