Hi,

It looks like only admins can see the broken link checker?
But it is the editors that need to be able to see the broken links so they can fix them!

Is it possible to give them permissions to see the list of broken links?

Thanks!!

Hi Team,

I’m unsure where to post this but I would like to see a feature request where the plugin can be configured to run overnight. Sometimes the plugin takes down a site for a brief minute or two while it does it’s scanning.

If the plugin could be scheduled to do it’s thing overnight it would prevent the site from going down in the middle of the day.

Thank you.
–Pat Costa

Hello,

Since updating to WordPress 6.7.0, I have been seeing the following notice in my error logs:

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the broken-link-checker domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later.

According to the WordPress documentation, this notice indicates that the broken-link-checker text domain is being loaded too early in the WordPress loading process (likely before the init action).

It seems that the plugin is attempting to load its translation files using a function like load_plugin_textdomain() in a hook that runs prematurely, such as plugins_loaded, or even directly in a global context.

Could you please review this and consider fixing the issue in a future update?

Thank you in advance for your help and for all the great work you’ve done on this plugin.

Best regards,
Laurent

Hi, recently it became impossible to Edit, Unlink, Recheck or Fix any of the links in the Local [old] list on wp-admin/admin.php?page=blc_local

The last entry shows in the Source column: “There has been a critical error on this website. Please check your site admin email inbox for instructions,” after which the table is broken off and the page source remains unfinished with missing footer.

The debug log shows this error occurring:

[14-Nov-2024 00:01:08 UTC] PHP Fatal error: Uncaught ArgumentCountError: 3 arguments are required, 2 given in /home/xxxxx/public_html/wp-content/plugins/broken-link-checker/legacy/includes/any-post.php:579 Stack trace:
#0 /home/xxxxx/public_html/wp-content/plugins/broken-link-checker/legacy/includes/any-post.php(579): sprintf()
#1 /home/xxxxx/public_html/wp-content/plugins/broken-link-checker/legacy/includes/any-post.php(543): blcAnyPostContainer->get_edit_url()
#2 /home/xxxxx/public_html/wp-content/plugins/broken-link-checker/legacy/includes/instances.php(463): blcAnyPostContainer->ui_get_source()
#3 /home/xxxxx/public_html/wp-content/plugins/broken-link-checker/legacy/includes/admin/table-printer.php(798): blcLinkInstance->ui_get_source()
#4 /home/xxxxx/public_html/wp-content/plugins/broken-link-checker/legacy/includes/admin/table-printer.php(490): blcTablePrinter->column_used_in()
#5 /home/xxxxx/public_html/wp-content/plugins/broken-link-checker/legacy/includes/admin/table-printer.php(147): blcTablePrinter->link_row()
#6 /home/xxxxx/public_html/wp-content/plugins/broken-link-checker/legacy/core/core.php(1988): blcTablePrinter->print_table()
#7 /home/xxxxx/public_html/wp-content/plugins/broken-link-checker/app/admin-pages/local-submenu/class-view.php(52): wsBrokenLinkChecker->links_page()
#8 /home/xxxxx/public_html/wp-content/plugins/broken-link-checker/app/admin-pages/local-submenu/class-controller.php(189): WPMUDEV_BLC\App\Admin_Pages\Local_Submenu\View->render()
#9 /home/xxxxx/public_html/wp-includes/class-wp-hook.php(324): WPMUDEV_BLC\App\Admin_Pages\Local_Submenu\Controller->output()
#10 /home/xxxxx/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#11 /home/xxxxx/public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
#12 /home/xxxxx/public_html/wp-admin/admin.php(259): do_action()
#13 {main} thrown in /home/xxxxx/public_html/wp-content/plugins/broken-link-checker/legacy/includes/any-post.php on line 579

Hope this can be fixed ??

Since 6.7 notices are popping up for this plugin

Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>broken-link-checker</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later.

The page I linked is an example with several bad reports.

I have been using the plugin for years. I just tried the cloud version. In both instances I keep getting multiple reports of bad links that work just fine when I try them.

In addition, the report in the hub for the cloud version presents a truncated version of the link.

The link displayed in the hub is: https://hotpads.com/new-york-ny/apartments-for-rent/map , but the link on the webpage is https://hotpads.com/new-york-ny/apartments-for-rent/map?z=15&lat=40.8805&lon=-73.9031

Clicking on the report link works immediately, but does not take me to the customized display that the link I am actually using goes to. Both work fine. You report a 403 in this instance.

This has been an ongoing issue (perhaps without the link shortening). It is a serious issue because the plugin puts a strikethrough on the link you report as bad and a visitor is therefore presented with an improper and unwelcoming display.

The hub report is showing a variety of Statuses. All the ones I tested manually from the webpages in question worked.

Since I first activated this plugin a few days ago I’ve been getting tons of false broken link reports. What’s the reason for this?
It’s extremely time consuming to go through all these and click on “not broken,” and even then the reports don’t disappear but remain. And then if I click on them again as not broken, some of them give me the option of “suppress report,” and others don’t, but still those ones I do have suppress still linger on as reported broken.
What is the rationale for having this plugin malfunctioning so badly?

• This topic was modified 2 weeks, 2 days ago by lomenade.

Suddenly multiple sites show all links to Facebook.com as 400 Bad Request. Some of these links have been there for years, if not a decade and were OK until yesterday.

Is Facebook now blocking Broken Link Checker testing? If so, is there a way around it?

The page above is just an example of one of the many pages I need help with, but I’ll explain the issue. ??

I went through all of the bad links and used the unlink button to get rid of broken hyperlinks specifically within my own site.

However, when I go to check on any of them, they’re all still there and linking to the broken page.

The example above was this page:

https://www.chasingfoxes.com/7-good-money-secrets-from-the-great-depression/

The page itself is fine, but it’s still linking to my article titled “7 Quotes That’ll Inspire You to Get Out of Debt”

It says it’s gone, but it’s not.

Could someone help me with this?

Thanks!

The results of the scans have become very inconsistent, and are seemingly skipping over many links, most notably to pages within the website. There doesn’t seem to be a specific reason, the links can be formatted in exactly the same way, but some are picked up and others are not.

If we look at this page as an example:
https://www.lambethappp.co.uk/hospital-discharge-and-community-support/
The scan results show 25 links were found. But if I edit the chapter and search for standard links in the content I find 53 links. 33 of which are to pages on this site, whereas in the scan results there are only 7 links found to pages within the site. The rest are all to external sites.

Hi! How can I increase the number of non-working links to delete in Broken Link Checker in the local version?

• This topic was modified 1 month, 2 weeks ago by lawwer.

Hi,

I’m trying to check for broken links in an ACF (Advanced Custom Fields) link field that is being used within a Gutenberg custom block. I’ve tried configuring the Broken Link Checker settings to include both ACF fields and custom fields, but it doesn’t seem to detect the links within these blocks.

Here’s what I’ve done so far:

• Enabled “Look for links in ACF fields” in the Broken Link Checker settings.
• Tried configuring the “Custom fields configuration” to target the specific ACF fields being used in the block.
  However, the plugin is still not detecting any broken links within these Gutenberg blocks.

Is there something specific I might be missing, or a different approach I should take for ACF fields used within custom blocks? Any advice or suggestions for additional settings or debugging steps would be greatly appreciated.

Thanks in advance!

Hello,

I’ve encountered a problem with the Broken Link Checker plugin where it flags URLs containing numbers as invalid during redirection. This seems like an unnecessary restriction, as URLs with numbers are quite common.

Steps to reproduce:

1. Attempt to fix a broken link by setting a new URL that includes numbers in a subdomain (e.g., https://mydomain.subdomain123.com).
2. The plugin marks the URL as invalid, preventing the redirection.

This is quite frustrating, as there should be no reason why a URL containing numbers in the subdomain would be considered invalid. Could this be resolved in a future update? It’s an essential feature to have working, as many legitimate URLs include numbers.

Thanks in advance!

• This topic was modified 1 month, 3 weeks ago by peterpalmer.

I recently switched from using the local version of BLC to the cloud version in the expectation that it would improve the accuracy of the reports, but I am getting a similar number of errors. When I reported this on the feedback site, your colleague Kris invited me to report the problem here and ask for your advice.
My site is simoncarne.com. I have a report from wpmudev.com, but I am not sure if it is OK to reproduce the link here. Please let me know if that is what you need in order to investigate the issue.
Amongst the working links which BLC is reporting as broken are:
https://www.fnlondon.com/articles/bankers-take-lessons-british-gas-20110627 (401 Unauthorised)
https://www.makeuseof.com/tag/feedreaders-to-become-most-popular-tools/ (21 Int Request Error)
https://www.amazon.co.uk/dp/B07BN6BWRV/ref=dp-kindle-redirect (500 Internal Server Error)
https://www.libdemvoice.org/leveson-report-open-thread-31860.html (403 Forbidden)
I welcome your comments.
Kind regards

Hi there,

I have issues with running the scan. I get the following error in the hub.

Scan aborted: Too many server errors.?This is to prevent overloading your server. Please retry the scan in a while or?contact support?if the issue persists.

Can you help me debug this further and solve the issue?

Best Regards,
Peter B. Stidsen

Hello,
we’ve been using BLC (local version) for years without issues, and we’re always using latest version as it updates automatically; same thing goes for our WP version, we’re up to date on everything.

The reason why i’m posting is we’re trying to understand if BLC is spamming our server or not, because we have some indications that it could be doing that.

Recently we’ve noticed an abnormally high CPU load on our server. By looking at our server logs, we can see an IP address is constantly bombarding URLs from our blog, but mostly images, to the point almost 20% of lines in our logs are from this IP address.

We’ve added htaccess rules to block this IP address (we now see in our logs it successfully gets 403 responses from our server).

But the weird thing is, right after we did this, BLC started getting 403s on every internal URL it scans (we use the old “local” mode); which seems to mean this problematic IP is related to BLC somehow.

So my question is the following : is the IP address 54.36.142.130 related to BLC in any way ?

Thanks,
Baptiste

Hi there,

I have been using the local checker for several years for multiple sites. I am considering moving to the cloud version. However, I do have a couple of questions before:

1. Will the cloud crawler look at the front end instead of the database? I get lots of errors in the local system because another system (WPML) uses some custom slugs for some link types and then convert them to correctly URL’s in the front end on the fly.
2. Is it possible to get an overview (and export) which links that are contained on each URL?
3. What are the general compatibility with WPML?

Best Regards,
Peter B. Stidsen

I’m trying to use BLC plugin using Local on a site that uses Elementor.

When using the Unlink or Fix Redirect function, BLC marks the link as fixed, but it’s not actually replaced/removed within the content.

Does this plugin not work with Elementor?

We’re running into an issue with the Local (old) Broken Link Checker where it resolves relative links to the following format:

https://example.com/source-path/%22/dest-path/%22

So, for example, a link on the page /page-1 that links to /page-2 ends up like this:

https://example.com/page-1/%22/page-2/%22

Even mailto: links suffer from this issue:

https://example.com/page-1/%22/mailto:[email protected]/%22

The actual links on the page work fine, but, according to BLC, we have hundreds of 404 links.

I haven’t checked every single link, but it looks like BLC is having trouble with links that are added as HTML (so <a href="/dest-path/">...</a>). BLC seems to include the quotes (“) that contain the href value when it resolves the URL (that explains the %22‘s in the resolved URL)

• This topic was modified 2 months, 1 week ago by roderickgadellaabsl.

I have over 400 broken links and I want to unlink at least in batches but even 20 per batch takes forever to unlink…. What’s the solution?

• This topic was modified 2 months, 1 week ago by mendelistickmend.

Hello! We started to experience an issue with the Broken Link Checker plugin. The blog admin login page fails to load with a timeout.

WordPress version 6.6.2
Current plugin: Broken Link Checker (version 2.3.0)
PHP version 8.1.29

Error Details
=============
An error of type E_ERROR was caused in line 370 of the file D:\WEBROOT\<domain name>\www\wp-content\plugins\broken-link-checker\core\class-loader.php. Error message: Maximum execution time of 1200 seconds exceeded

First off, thanks for a great plug-in. In general, it works well. However, something seems to have gone wrong on a blog post I just wrote.

If you look at the page linked above, you’ll see the sixth paragraph (starts with “The sample repository contains”) has a link on the 2nd and 3rd words. The target of the link is https://github.com/MrYossu/TelerikGridWithDapper, which is a live link. However, the plug-in has marked it as broken.

Same goes for the link at the end of the previous paragraph. That’s to the same repository.

Any ideas what’s going wrong? Thanks again

Hi, we’re having trouble installing BLC on our Production site. It installs and runs fine on our Dev environment but not Production or Preprod.

All environments are hosted on WP VIP using PHP 8.1, WordPress 6.6.1 and a custom theme.

Upon trying to install, the following is shown in the WP dashboard:

Broken Link Checker installation failed. Try deactivating and then reactivating the plugin.
installation_complete = 0
installation_flag_cleared_on = 2023-11-10T16:41:24+00:00 (1699634484.3933)
installation_flag_set_on = 0

Installation log follows :
Plugin activated at 2023-11-10 09:40:07.
Installation/update begins.
Upgrading the database...
... SHOW TABLES (0.002 seconds)
... SHOW FULL COLUMNS FROM wp_blc_filters 0.001 seconds
... SHOW INDEX FROM wp_blc_filters 0.001 seconds
... SHOW FULL COLUMNS FROM wp_blc_instances 0.001 seconds
... SHOW INDEX FROM wp_blc_instances 0.001 seconds
... SHOW FULL COLUMNS FROM wp_blc_links 0.001 seconds
... SHOW INDEX FROM wp_blc_links 0.001 seconds
... SHOW FULL COLUMNS FROM wp_blc_synch 0.001 seconds
... SHOW INDEX FROM wp_blc_synch 0.001 seconds
[OK] ALTER TABLE wp_blc_filters MODIFY COLUMN id int(10) unsigned NOT NULL AUTO_INCREMENT (0.006 seconds)
[OK] ALTER TABLE wp_blc_instances MODIFY COLUMN instance_id int(10) unsigned NOT NULL AUTO_INCREMENT (0.004 seconds)
[OK] ALTER TABLE wp_blc_instances MODIFY COLUMN link_id int(10) unsigned NOT NULL (0.009 seconds)
[OK] ALTER TABLE wp_blc_instances MODIFY COLUMN container_id int(10) unsigned NOT NULL (0.006 seconds)
[OK] ALTER TABLE wp_blc_instances MODIFY COLUMN link_text text NOT NULL DEFAULT '' (0.011 seconds)
[OK] ALTER TABLE wp_blc_links MODIFY COLUMN link_id int(20) unsigned NOT NULL AUTO_INCREMENT (0.008 seconds)
[OK] ALTER TABLE wp_blc_links MODIFY COLUMN check_count int(4) unsigned NOT NULL DEFAULT '0' (0.011 seconds)
[OK] ALTER TABLE wp_blc_links MODIFY COLUMN redirect_count smallint(5) unsigned NOT NULL DEFAULT '0' (0.015 seconds)
[OK] ALTER TABLE wp_blc_links MODIFY COLUMN http_code smallint(6) NOT NULL DEFAULT '0' (0.021 seconds)
[OK] ALTER TABLE wp_blc_links MODIFY COLUMN timeout tinyint(1) unsigned NOT NULL DEFAULT '0' (0.016 seconds)
[OK] ALTER TABLE wp_blc_links MODIFY COLUMN broken tinyint(1) unsigned NOT NULL DEFAULT '0' (0.017 seconds)
[OK] ALTER TABLE wp_blc_links MODIFY COLUMN warning tinyint(1) unsigned NOT NULL DEFAULT '0' (0.015 seconds)
[OK] ALTER TABLE wp_blc_synch MODIFY COLUMN container_id int(20) unsigned NOT NULL (45.438 seconds)
[OK] ALTER TABLE wp_blc_synch MODIFY COLUMN synched tinyint(2) unsigned NOT NULL (20.756 seconds)
Schema update took 66.344 seconds
Database schema updated.
Database successfully upgraded.
--- Total: 66.519 seconds
Cleaning up the database...
... Deleting invalid container records
... 0 synch records deleted in 0.001 seconds
... Deleting invalid link instances
... 0 instances deleted in 0.000 seconds
... 0 more instances deleted in 0.000 seconds
... Deleting orphaned links
... 0 links deleted in 0.000 seconds
--- Total: 0.002 seconds
Notifying modules...
... Updating module cache
... Cache refresh took 0.193 seconds
... Loading modules
... 4 modules loaded in 0.002 seconds
... Notifying module "http"
... Notifying module "link"
... Notifying module "image"
... Notifying module "metadata"
... Notifying module "url_field"
... Notifying module "comment"
...... Deleting synch. records for removed comments
...... 0 rows deleted in 3.872 seconds
...... Creating synch. records for new comments
...... 0 rows inserted in 20.866 seconds
... Notifying module "acf"
... Notifying module "post"
...... Deleting synch records for removed posts & post with invalid status
DELETE synch.* FROM wp_blc_synch AS synch WHERE synch.container_id NOT IN ('11250200', '11251495', '11250700', '11250538', '11249586', '11248797', '11248567', '11248262', '11247817', '11247366', '11246816', '11246339', '11246007', '11245080', '11244276', '11243809', '11243520', '11242681', '11242112', '11241567', '11241289', '11241068', '11240971', '11240222', '11239635', '11238971', '11238251', '11237717', '11237145', '11236724',

The only related error we can find in the error logs is:

PHP message: PHP Fatal error: Uncaught Error: Class "blcUtility" not found in /var/www/wp-content/plugins/broken-link-checker/legacy/core/core.php:1723

If Site Health info helps you, here it is:

<br>### wp-core ###<br><br>version: 6.6.1<br>site_language: en_US<br>user_language: en_US<br>timezone: America/Boise<br>permalink: /%year%/%monthnum%/%day%/%postname%/<br>https_status: true<br>multisite: true<br>user_registration: false<br>blog_public: 1<br>default_comment_status: open<br>environment_type: production<br>site_id: 1<br>site_count: 4<br>network_count: 1<br>user_count: 304801<br>dotorg_communication: true<br><br>### wp-dropins (3) ###<br><br>db.php: true<br>object-cache.php: true<br>sunrise.php: true<br><br>### wp-active-theme ###<br><br>name: Redacted (redacted)<br>version: 1.0.0<br>author: Redacted<br>author_website: https://redacted.com<br>parent_theme: none<br>theme_features: core-block-patterns, widgets-block-editor, block-templates, infinite-scroll, menus, automatic-feed-links, title-tag, post-thumbnails, html5, custom-background, customize-selective-refresh-widgets, custom-logo, wp-block-styles, align-wide, editor-styles, responsive-embeds, appearance-tools, border, widgets, editor-style<br>theme_path: /var/www/wp-content/themes/redacted<br><br>### wp-mu-plugins (38) ###<br><br>Admin Notice: version: 0.1.0, author: WordPress VIP<br>Advanced Post Caching: version: 0.2, author: Automattic<br>Akismet Anti-Spam: version: 5.1, author: Automattic<br>blogpublic-notice.php: author: (undefined), version: (undefined)<br>HTTP Concat: version: 1.0, author: Automattic<br>Jetpack: version: 13.7, author: Automattic<br>Lightweight Term Count Update: version: 0.1.0, author: Automattic, Alley Interactive<br>prometheus.php: author: (undefined), version: (undefined)<br>query-monitor.php: author: (undefined), version: (undefined)<br>REST API Enhancements: version: 0.1, author: Erick Hitter, Automattic<br>Rewrite Rules Inspector: version: 1.4.0, author: Automattic, Daniel Bachhuber<br>VaultPress: version: 2.2.1, author: Automattic<br>VIP AllOptions Safeguard: author: Automattic, version: (undefined)<br>VIP Back-compat: version: 1.0, author: Automattic<br>VIP Cache Manager: version: 1.1, author: Automattic<br>VIP Client mu-plugins: author: Automattic, version: (undefined)<br>VIP Codebase Manager: version: 1.0.0, author: Automattic<br>VIP Cron Enhancements: version: 1.0, author: Automattic<br>VIP Dashboard: version: 3.0.0, author: Scott Evans, Filipe Varela, Pau Argelaguet<br>VIP Feed Cache: author: Automattic, version: (undefined)<br>VIP File Service: version: 0.2, author: Automattic<br>VIP Force Two Factor: author: Automattic, version: (undefined)<br>VIP Go Core Modifications: author: Automattic, version: (undefined)<br>VIP Go Plugin Compat: version: 1.0, author: Automattic<br>VIP Hosting Miscellaneous: version: 1.1, author: Automattic<br>VIP Init: author: Automattic, version: (undefined)<br>VIP Integrations: author: Automattic, version: (undefined)<br>VIP Mail: version: 1.0, author: Automattic<br>VIP Parse.ly Integration: version: 1.0, author: Automattic<br>VIP Performance: version: 1.0, author: Automattic<br>VIP Plugins: version: 1.0.0, author: Automattic<br>VIP Schema: author: Automattic, version: (undefined)<br>VIP Security: version: 1.2, author: Automattic<br>VIP Stats: author: Automattic, version: (undefined)<br>WooCommerce: VIP Specific Changes: version: 1.0.0, author: Automattic<br>WordPress Importer: version: 0.6.4, author: wordpressdotorg<br>WordPress VIP Support: version: 3.1.0, author: <a href="https://automattic.com">Automattic</a><br>WP-CLI for VIP Go: author: Automattic, version: (undefined)<br><br>### wp-plugins-active (16) ###<br><br>Ads.txt Manager: version: 1.4.4, author: 10up<br>Advanced Custom Fields PRO: version: 6.3.5, author: WP Engine (latest version: 6.3.6)<br>Block Admin Emails: version: 1.0.0, author: Redacted<br>Bulk Delete: version: 6.0.2, author: Sudar<br>Cache Nav Menus: version: 1.0, author: Automattic<br>Comment Reply Email Notification: version: 1.33.0, author: Arno Welzel<br>External Links in a New Window: version: 1.0, author: Javi Moya<br>Fieldmanager: version: 1.2.4, author: Alley<br>Gravity Forms: version: 2.8.16, author: Gravity Forms (latest version: 2.8.17)<br>IndexNow: version: 1.0.3, author: Microsoft Bing<br>Sticky Custom Post Types: version: 1.2.3, author: Ann Oyama<br>Term Management Tools: version: 2.0.1, author: theMikeD, scribu<br>TK Favorites: version: 1.0.0, author: Redacted<br>WP Post Publish AYS: version: 0.1.0, author: John James Jacoby<br>Yoast SEO: version: 23.2, author: Team Yoast (latest version: 23.4)<br>Yoast SEO Premium: version: 23.2, author: Team Yoast<br><br>### wp-plugins-inactive (1) ###<br><br>Yoast Test Helper: version: 1.18, author: Team Yoast<br><br>### wp-media ###<br><br>image_editor: WP_Image_Editor_GD<br>imagick_module_version: Not available<br>imagemagick_version: Not available<br>imagick_version: Not available<br>file_uploads: 1<br>post_max_size: 2047M<br>upload_max_filesize: 2047M<br>max_effective_size: 2 GB<br>max_file_uploads: 20<br>gd_version: bundled (2.1.0 compatible)<br>gd_formats: GIF, JPEG, PNG, WebP, BMP, AVIF<br>ghostscript_version: not available<br><br>### wp-server ###<br><br>server_architecture: Linux 5.10.0-26-amd64 x86_64<br>httpd_software: nginx<br>php_version: 8.2.22 64bit<br>php_sapi: fpm-fcgi<br>max_input_variables: 6144<br>time_limit: 1200<br>memory_limit: 768M<br>max_input_time: 1200<br>upload_max_filesize: 2047M<br>php_post_max_size: 2047M<br>curl_version: 8.7.1 OpenSSL/1.1.1w<br>suhosin: false<br>imagick_availability: false<br>pretty_permalinks: true<br>current: 2024-09-04T08:31:50+00:00<br>utc-time: Wednesday, 04-Sep-24 08:31:50 UTC<br>server-time: 2024-09-04T02:31:50-06:00<br><br>### wp-database ###<br><br>extension: mysqli<br>server_version: 8.0.28<br>client_version: mysqlnd 8.2.22<br>max_allowed_packet: 67108864<br>max_connections: 400<br><br>### wp-constants ###<br><br>WP_HOME: undefined<br>WP_SITEURL: undefined<br>WP_CONTENT_DIR: /var/www/wp-content<br>WP_PLUGIN_DIR: /var/www/wp-content/plugins<br>WP_MEMORY_LIMIT: 64M<br>WP_MAX_MEMORY_LIMIT: 512M<br>WP_DEBUG: false<br>WP_DEBUG_DISPLAY: false<br>WP_DEBUG_LOG: false<br>SCRIPT_DEBUG: false<br>WP_CACHE: false<br>CONCATENATE_SCRIPTS: undefined<br>COMPRESS_SCRIPTS: undefined<br>COMPRESS_CSS: undefined<br>WP_ENVIRONMENT_TYPE: production<br>WP_DEVELOPMENT_MODE: undefined<br>DB_CHARSET: utf8mb4<br>DB_COLLATE: utf8mb4_general_ci<br><br>### wp-filesystem ###<br><br>wordpress: not writable<br>wp-content: not writable<br>uploads: writable<br>plugins: not writable<br>themes: not writable<br>fonts: writable<br>mu-plugins: not writable<br><br>### jetpack ###<br><br>site_id: 147862304<br>ssl_cert: No<br>time_diff: false<br>version_option: 13.7:1724264444<br>old_version: 13.6:1724264444<br>public: Public<br>master_user: #1 redacted<br>is_offline_mode: off<br>is_offline_mode_constant: off<br>current_user: #12345678 redacted<br>tokens_set: Blog <br>blog_token: zs7&99niO&x6RDay61!s55Q#3L8hY9Sc<br>user_token: Not set.<br>version: 13.7<br>jp_plugin_dir: /var/www/wp-content/mu-plugins/jetpack-13.7/<br>plan: complete<br>protect_header: false<br>full_sync: {"started":"Wed, 03 Jul 2024 16:41:47 +0000","finished":"Wed, 03 Jul 2024 16:41:49 +0000","progress":{"options":{"finished":true},"functions":{"finished":true},"constants":{"finished":true},"users":{"total":0,"sent":0,"finished":true,"last_sent":"~0"},"network_options":{"finished":true}},"config":{"options":true,"functions":true,"constants":true,"users":[145565787],"network_options":true}}<br>sync_size: 1<br>sync_lag: 3 seconds<br>full_sync_size: undefined<br>full_sync_lag: 0 seconds<br>idc_urls: {"home":"https:\/\/redacted.com","siteurl":"https:\/\/redacted.com","WP_HOME":"","WP_SITEURL":""}<br>idc_error_option: false<br>idc_optin: false<br>cxn_tests: All Pass.<br><br>### acf ###<br><br>version: 6.3.5<br>plugin_type: PRO<br>activated: false<br>activated_url: undefined<br>license_type: undefined<br>license_status: undefined<br>subscription_expires: undefined<br>ui_field_groups: 1<br>php_field_groups: 0<br>json_field_groups: 49<br>rest_field_groups: 0<br>post_types_enabled: true<br>ui_post_types: 22<br>json_post_types: 0<br>ui_taxonomies: 12<br>json_taxonomies: 0<br>ui_options_pages_enabled: true<br>ui_options_pages: 0<br>json_options_pages: 0<br>php_options_pages: 4<br>rest_api_format: light<br>registered_acf_blocks: 0<br>blocks_per_api_version: <br>blocks_per_acf_block_version: <br>blocks_using_post_meta: 0<br>preload_blocks: true<br>admin_ui_enabled: false<br>field_type-modal_enabled: true<br>field_settings_tabs_enabled: false<br>shortcode_enabled: true<br>registered_acf_forms: 0<br>json_save_paths: 1<br>json_load_paths: 1<br><br>### parsely (18) ###<br><br>apikey: redacted.com<br>content_id_prefix: undefined<br>use_top_level_cats: false<br>custom_taxonomy_section: category<br>cats_as_tags: true<br>content_helper: <br>	ai_features_enabled: 1<br>	smart_linking: Array<br>	title_suggestions: Array<br>	excerpt_suggestions: Array<br>track_authenticated_users: true<br>lowercase_tags: true<br>force_https_canonicals: true<br>track_post_types: <br>	0: post<br>	1: recipes<br>	2: contests<br>	3: diy<br>	4: tips<br>	5: product-reviews<br>	6: deals<br>	7: headers<br>	8: news<br>track_page_types: <br>	0: page<br>full_metadata_in_non_posts: false<br>disable_javascript: false<br>disable_amp: false<br>meta_type: repeated_metas<br>logo: https://redacted.com/wp-content/uploads/2012/1/logo.jpg<br>disable_autotrack: false<br>plugin_version: 3.16.4<br><br>

Some identifying elements have been redacted but I don’t believe they will affect your analysis.

I use this plugin on many different sites and would like to get to the bottom of this issue. The only related info I can find is in this ticket, but unfortunately removing and reinstalling has not helped.

Thanks in advance!

Hi,

I have am using Advanced Custom Fields and have the Repeater extension. Within my repeater field is a text field and WYSIWYG field, I’ve added the field keys in the “look for links in” section but they’re still not appearing. I’ve tried the force recheck a few times but still no luck.

Hi there,

Every day I get a massive report of 403 Forbidden broken links on my site. If I got in an hit the recheck button on the link, it changed straight away to 301 ok. If I leave the link at 403, no matter how many times the system rechecked it it stays as 403. I need to manually recheck the link for it to change to 301 ok.

I am running the latest version of WordPress and the plugin. I use the local version as I have tried the cloud version and it doesn’t appear to work well for me. Maybe due to my large site with over 89,000 links.

How can I stop this from happening as it is wasting so much of my time.

Thanks in advance

• This topic was modified 2 months, 3 weeks ago by WakeUpWorld.

Hello

We’re no longer receiving reports on broken links.

thank you

Hello,

In testing the new cloud scanning engine introduced with BLC 2.0, I’ve run into an issue where links that contain a query parameter that cannot be omitted (such as YouTube playlists, Google calendar links, etc.)

I know that removing query parameters is the default behavior, but without some way to allowlist certain parameters or detect when parameters are a meaningful part of a URL (such as trying the URL again with the query parameters included if the stripped URL fails) this leads to a large number of false positives.

One good example is YouTube Playlists. Here’s one for the BLC team to listen to while debugging this issue ?? Below is an example of testing this URL using the curl command provided elsewhere in the support forum, both with and without the query parameter:

~: curl --header "X-Forawarded-For: 165.227.127.103" -I -A "WPMU DEV Broken Link Checker Spider" "https://www.youtube.com/playlist"
HTTP/2 404
content-type: text/html; charset=utf-8
...
~: curl --header "X-Forawarded-For: 165.227.127.103" -I -A "WPMU DEV Broken Link Checker Spider" "https://www.youtube.com/playlist?list=PLd4WuOjySbJyxmFpBOE71slcbqvK9K2jd"
HTTP/2 200
content-type: text/html; charset=utf-8
...

As you can see from the example, the only difference is the presence or absence of the “list” query parameter. Omitting that will always produce a 404 error. Please provide an update or documentation to address this issue, both for known services, and for others that may be newly created and wouldn’t be on an internal allowlist.

Thank you,
David

Hi there,

I have tried all relevant settings, I think, but for some reason BLC doesn’t see and check any of the external/affiliate links in Woo. There are hundreds of them in my site. Yes, I have checked the box: Look for links in > Products and Ninja Tables. What am I missing?

• This topic was modified 3 months ago by Sean. Reason: more info added

We’re evaluating the Broken Link Checker Plugin on our WP website.
When we make an Edit any given URL it has no impact on the actual webpage.

This is the free version, but shouldn’t this also work with that version?

BLC 2.0’s cloud scanner runs into infinite loops of links with some configurations of The Events Calendar and The Events Calendar Pro (in some cases reporting 24,000,000+ instances of calendar links) and runs out of time on the 3-hour scan limit.

Please share any information available on how to filter out infinite loops of calendar links, or whether this will be identified and automatically filtered out in future versions of BLC 2.0.

Thank you