Aristocles
Forum Replies Created
-
Thanks so much for taking the time to submit this feature request — both ideas are really valuable!
The MCP integration is something I’ll definitely be exploring. It’s an exciting direction that could make the plugin much more powerful for AI-driven workflows, so I want to make sure I get it right.
The auto-omit feature is a bit more straightforward to implement, so that’s likely something you can look forward to in a near-future update. In the meantime, you can manually exclude domains like LinkedIn in the Omitted Links section using the wildcard option by adding an asterisk at the end (e.g. https://www.linkedin.com/*).
Thanks again — feedback like this is what helps make the plugin better!
Forum: Plugins
In reply to: [Broken Link Notifier] Broken link is not updating (Elementor issue?)Ah. It was supposed to say update successful. Sorry. If it worked, that’s the most important part. I’ll update for next version. Thanks.
Forum: Plugins
In reply to: [Broken Link Notifier] Broken link is not updating (Elementor issue?)@nazrinn , thank you for pointing that out. It was indeed an issue with Elementor. I have fixed it now so you should be able to replace them from your results page after updating to version 1.3.7.4. Sorry for the inconvenience. Let me know if you need anything else.
AriForum: Plugins
In reply to: [Developer Debug Tools] Deprecation ErrorThanks for letting me know. I got it fixed just in time for the next update. Pushing it now. Please update to version 3.0.1.4. 🙂
Forum: Reviews
In reply to: [Clear Cache Everywhere] Perfect Cache Purge Plugin@seanlance Thank you for the kind review! I’m so happy to hear that you were able to use it like you want. 🙂
Forum: Plugins
In reply to: [Broken Link Notifier] 51 broken links that are not broken?Great. Thanks for letting me know. Reach out if you have any further issues.
Forum: Plugins
In reply to: [Broken Link Notifier] 51 broken links that are not broken?@andreasson – Alright, let’s try this again. Please update to version 1.3.7.2 now.
Then go to your results and delete all of the links. Then before visiting the frontend page again, refresh the results page and tell me if the broken links show up in the results again. This would tell me if the issue is in deleting the results from the database or if there is another issue in the capture of the links.If they actually get deleted, visit the frontend page again and wait a moment for the page to get scanned. Then go back to your results and tell me if the same broken links show up again.
Now, there is also another problem that I saw on your site. When going to the link you sent me, I went to the developer console and noticed a message that says “Scan failed. Please contact plugin developer.” In the newest version, that message should now say what the actual error is so we can figure it out. This error may just be that there are too many links on the page, though, which you can increase in plugin settings.
Let me know what happens.
AriForum: Plugins
In reply to: [Broken Link Notifier] 51 broken links that are not broken?@andreasson , I’m pretty sure I figured it out. These links should not be showing up anymore for you. Please update version 1.3.7.1. Then delete all your results and visit your pages again. See if anything shows up again. If they do, let me know.
Forum: Plugins
In reply to: [Broken Link Notifier] 51 broken links that are not broken?Hi @andreasson , I am looking into why it came up to begin with. Can you select them and delete them manually at least? I see you have over 10k links. Wow! Are they all for the same thing?
Forum: Plugins
In reply to: [Broken Link Checker] 51 broken links that don’t exist@andreasson , you submitted this on the wrong plugin, buddy. This is for the Broken Link Checker plugin, not the Broken Link Notifier plugin. Head on over to https://ww.wp.xz.cn/support/plugin/broken-link-notifier/ and I’ll take care of you there. 🙂
@cantabber, the plugin has been marked as patched. 🙂
https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/broken-link-notifier
@cantabber , thank you for reaching out and for the kudos.
Yes, I am aware and working on a solution for version 1.3.7.The problem is that they are wanting a capability check on the front-end scanner, which defeats the purpose of the plugin. In case you are unfamiliar, a capability check would ensure that the user has permissions such as an admin to trigger the scans. Obviously that would mean that it wouldn’t catch broken links when non-logged in users visit a page.
Prior to version 1.3.5, I already included several protective measures to ensure that only proper links are checked, and checked safely. And in version 1.3.6, I added a rate limiter as well. The person reporting the “vulnerability” didn’t check for alternative protections, though. They just saw, “there’s no capability check, so it must be unsafe.” It isn’t.
AriHi @nazrinn, that’s an excellent suggestion! I have added it to the emails in version 1.3.5. Please update to see the change. 🙂
By the way, if you’re familiar with custom development at all, there is a hook that allows you to customize the message output completely:
https://pluginrx.com/docs/plugin/broken-link-notifier/#email_message- This reply was modified 3 months, 3 weeks ago by Aristocles. Reason: Added dev docs for hook
Forum: Plugins
In reply to: [Headers Security Advanced & HSTS WP] Breaking update@unicorn03 Thanks for your prompt fix on this issue. Your last response sounds like a solution we could easily do, but not all of your users will know to come here and learn what to do. Just a suggestion, but maybe you could run a check on that field and have it remove those slashes from previously saved values so that it will resolve itself instead. It’ll save you some time having to respond to other complaints and prevent further frustration from other users.
Forum: Plugins
In reply to: [Headers Security Advanced & HSTS WP] Breaking updateSame here.
After updating the plugin today, my site’s login form stopped working because the Google reCAPTCHA field was always empty. Checking the browser console revealed multiple Content Security Policy (CSP) violations introduced by the plugin.
The update enforced an overly strict CSP that blocked external scripts, styles, and fonts — including essential sources for Google reCAPTCHA (
https://www.google.comandhttps://www.gstatic.com), Google Fonts, and Font Awesome. As a result, the reCAPTCHA script never loaded, preventing the form from submitting.Deactivating the plugin immediately resolved the issue, confirming that the new CSP rules were the cause. I will keep it deactivated until I here that there has been a fix.