davidginzberg

Thanks Adam,

Can you tell me whether changes to the behavior of the cloud engine go into the changelog as well? As they’re two different pieces of software I would assume not, so if there’s somewhere else I should be looking for that changelog that would be helpful information.

Thanks,
David

Thanks for the update Nebu. I’ll keep an eye on this thread for further updates on this issue.

Cheers,
David

Hi there,

The issue is still present and the roadmap only hints at “groundbreaking new features”, not fixing existing issues. It seems to provide quite a bit less information than the entries for other WPMU DEV products.

I’ve switched this thread back to “not resolved” to reflect the actual state of the issue. Is there a public-facing bug/issue tracker available? That would be more helpful than the roadmap in its current state.

Thank you,
David

Hi Amin,

Thank you for the update. I realize it can take some time to work a patch into the deployment schedule and get the bot approved. I’m happy to wait for that update. I’ll keep an eye on this thread until then.

Thanks,
David

Hi Kris,

Thank you for the update. It’s good to know that the BLC team is planning to address the issue.

I am reverting the “resolved” flag until the feature you described is released to production and/or the issue is listed in the troubleshooting section of the docs. Looking forward to seeing that release.

Cheers,

David

Hello Nebu,

Thanks for your message. If there’s any other information I can provide that would be helpful, please let me know. I’ll keep an eye on this thread for a follow-up once the BLC team has had time to assess.

Thanks,
David

Hello Nebu,

Thank you for your response. I will keep an eye on this topic for a follow-up once the BLC team has had time to assess.

Thanks,
David

Thanks Imran,

While I wait for that update, can you tell me how BLC’s cloud scanner handles noindex and nofollow directives and robots.txt settings? I’d like to understand if those might be useful to control which URLs are scanned and I’m not seeing anything in the documentation.

Thanks,
David

Hi @lgladdy,

Thanks for the update. I’ve verified that this no longer produces the fatal error on our sites.

Thanks for the update @wpmudevsupport12,

I’m running into the same issue on multiple sites now, so if a future release adds an identifiable UA, or a way to set one in the WP Admin settings, that would be very helpful. For now, the best workaround we’ve found is manually checking links that get a 503, but that’s not a sustainable solution long-term. If there’s a better solution you can offer for unblocking these links, I’d welcome the advice.

Thank You,
David

Thanks for your reply @wpmudevsupport12.

Please note the following from my original post:

Please note: This issue is specific to third-party sites blocking Broken Link Checker traffic, so any solution that requires changing CloudFlare settings likely isn’t workable.

Because this issue involves being blocked by sites controlled by a third party, your suggestion is unfortunately not going to work here.

I’d like to request that someone at the WPMU Dev team submit the user agent details you’ve listed above to CloudFlare using The CloudFlare Bot Verification Form so that all users of Broken Link Checker can benefit from whitelisting.

And I’m happy to hear that there are updates coming. If you have a link to a blog post or press release detailing them I’d be happy to take a look to see if any of them will help.

Thank you,
David