hongpong

You are probably reaching the job timeout. Give a try as the community fork that I put together with some other people has better batch job management (resumes past the timeouts better). I have requested already to take over managing this plugin – my fork does not have a separate internal designation in the WP universe. The DB schema is about the same in terms of recording whether links are checked.

https://github.com/HongPong/broken-link-checker

Otherwise you can try changing the PHP timeout values in your environment.

best regards!

This particular issue should be OK on my repo.

There has been a bit of activity on our fork repo which does cover some of the issues people are still having such as the misnamed database table issue. Give a try and download here (use green button): https://github.com/hongpong/broken-link-checker

Note this is not fully packaged as a forked plugin but I did update the readme a bit to clarify.

I don’t have the capacity for full blown maintenance but I can at least evaluate pull requests on a week-or-two basis. Also there have been other patches around on github see the ‘network’ feature. If there are worthy ones to add post a PR and I will get to it in a reasonable time frame.

Hi folks,

There has been a bit of activity on our fork repo which does cover some of the issues people are still having such as the misnamed database table issue. Give a try and download here (use green button): https://github.com/hongpong/broken-link-checker

Note this is not fully packaged as a forked plugin but I did update the readme a bit to clarify.

I don’t have the capacity for full blown maintenance but I can at least evaluate pull requests on a week-or-two basis. Also there have been other patches around on github see the ‘network’ feature. If there are worthy ones to add post a PR and I will get to it in a reasonable time frame.

Hi folks,

There has been a bit of activity on our fork repo which does cover some of the issues people are still having such as the misnamed database table issue. Give a try and download here (use green button): https://github.com/hongpong/broken-link-checker

Note this is not fully packaged as a forked plugin but I did update the readme a bit to clarify.

I don’t have the capacity for full blown maintenance but I can at least evaluate pull requests on a week-or-two basis. Also there have been other patches around on github see the ‘network’ feature. If there are worthy ones to add post a PR and I will get to it in a reasonable time frame.

i would suggest that a patch be applied on this one so that the clients don’t need to be on a fork. thanks ??

Thanks so much for the quick and informative answer. This is really helpful!

@jodzeee take a look at the cron jobs to get a sense of it (this hasn’t been surfaced very well in WP by default)

https://www.wpbeginner.com/plugins/how-to-view-and-control-wordpress-cron-jobs/

@gooma2 I don’t have access to this repo and as I’ve said I don’t have the latitude to put my time into a software package that is branded for a company. If there are good pull requests that people can test I will put them on the community fork and revisit in say, 10 months or so if it’s worth submitting a new official plugin.

this issue has been logged on the community fork and PR is welcome for the issue

https://github.com/HongPong/broken-link-checker/issues/36

some of this has been because the jobs were not quite set up to batch correctly. this has been improved a bit. you can try the community fork that i set up which might give better performance than the main one. available for download here.

https://github.com/HongPong/broken-link-checker

In the community fork we are following these issues. I think this was already resolved due to community commits that did not get included in the main plugin

https://github.com/HongPong/broken-link-checker/issues/23

this has been filed on the community fork and any PR is welcome

https://github.com/HongPong/broken-link-checker/issues/36

This issue is filed on the community fork and any pull request fix is welcome here
https://github.com/HongPong/broken-link-checker/issues/27

@finalwebsites thank you for finding this. A community member has opened an issue about this here on the community fork of the plugin and a pull request is welcome.

https://github.com/HongPong/broken-link-checker/issues/36

Hi all,

I am really glad to hear that the team is committed to working on the regular maintenance of the plugin and supporting the community. This seems to fulfill the main goal of forking which is to get positive improvements going for everyone. Thus I withdraw my request to take over management of this community plugin.

(sorry for delay in response, I got rather sick when I was planning to revisit everything, then had to launch a new site, you know how it goes…)

To @tomusher I would say that I have not earned any real contributor credits on this plugin yet and should not be credited that way.

I have not changed any DB structure on the fork compared to the main line, simply included other folks improved DB commit structure which seems to improve the stability.

Re the future of the fork here is what I am thinking:
– On the readme the fork will get dubbed “Broken Link Checker Unlimited” to distinguish it from the mainline plugin. However I will leave the URL as it is now. (hopefully if the readme is updated, this will not cause needless confusion but if its a serious problem let me know.)
– post PRs to the fork if you like!!
– I am not going to delete the fork, and I will leave the issues that I wrote up available, in case people want to tackle them or use them as ideas.
– I would be down to keep taking on patches from the community over there, and if they get rolled into the main line that is good as well. I would still backport changes from the main line to it (or if anyone else wants to submit PRs there that’s great)
– I will avoid changing the DB structure, so that, in theory, the fork can be swapped as one would expect with the mainline plugin, without surprises. (however there was someone who observed that the null values should be stored a little differently to match the latest mysql defaults, this could be explored but would mean that the fork data would not easily interoperate with the mainline plugin data, so I am not inclined to mess with it).
– If the fork really gets rolling, let’s say at the beginning of 2020, I would consider submitting it as a full alternative plugin to the WordPress community. It should be clear by that time if that makes sense or if it just sensible to leave it as a modest community fork.
– I am still particularly interested in scrubbing AMP urls to replace with proper ones, as well as scrubbing ugly ?FBCLID query string pollution. Down with badly behaved mega-vendor URL pollution, am I right folks?!
– This also gives me, and anyone else interested, a bit of a free hand to reshuffle and reoptimize the plugin as “I would like it to be” rather than the priorities of maximizing backwards compatibility, conservatively minimizing changes and so on.

I would hope that the github version maintained by ManageWP is kept up to date so that no confusing SVN/git divergences occur.

Personally I learned quite a bit in this process and I appreciate the positive community discussion around here. I feel like all of this is worth the effort because we really need free software and high quality hyperlinks to be available on the interwebs.

Thank you all for sharing your thoughts!!
..Dan