Request to transfer ownership of Broken Link Checker

Thank you so much @hongpong for taking this up. I had that same issue with it getting stuck. Installed your 1.11.7 version and I’m back in business.

I hope that your changes will get rolled into the “official” version or you can take it over. You’re doing some great work on it. Just want to express my deepest appreciation for your efforts.

@hongpong

Thanks for what you’ve done so far! Your forked version is running normally. Of course, as you know, the original could have used a number of improvements.

Will you tell us your longer-term intentions if you do either takeover the current plugin or continue on with your fork?

Specifically, I’d like to know whether you’d be going strictly the donations route or creating features that would be off for those who don’t pay.

I encourage the donations route. If donations prove insufficient, then a “Pro” version could be your plan B.

I think WP plugin developers should become more interactive concerning donation requests. A developer could say that such-and-such feature would take me x hours, and I’d like to get $x per hour to bring it about. There simply are people who cannot afford a dime who shouldn’t be left behind by the WP opensource community.

I’m not rich, but this plugin has lots of installs. If enough admins or site owners would donate even a small amount, it could be really great for the developer(s).

Also, if this WordPress repository system would allow it, it would be nice to have a tab separate from the “Support” tab just for “Feature Requests/Improvements” or the like.

@hongpong ,

Hi,

I see you’re addressing support issues in this forum. Some of the things you are tackling or have at least noted are things I have been saving on my list for when the dust settles as to whether you’ll be taking over this plugin or continuing with your fork.

Anyway, you may not have the original plugin installed and, therefore, might not have been made aware that it was just updated:

Changelog:

1.11.7

Fixed a PHP 7.2 compatibility issue

1.11.6

Fixed link check not saving

I think you’re doing a solid job being informative. WordPress should take that into consideration when deciding anything on their end.

This might be helpful to see what’s changed: https://plugins.trac.wordpress.org/changeset?old_path=%2Fbroken-link-checker&old=2054130&new_path=%2Fbroken-link-checker&new=2054130&sfp_email=&sfph_mail=

@kouteki Thank you for replying here and confirming your continued motivation in maintaining this very useful plugin.

The role of maintainer also means the responsibility of monitoring and responding to requests on the Support forum. Something which has not been happening for a very long time here. I hope this changes and that users with issues no longer need to be posting into an empty void.

@kouteki ,

I think all of this in a very positive development.

Let me say that on the main page for this plugin here on the WP repository and under “Contributors & Developers,” it currently lists only ManageWP. I feel that Dan ( @hongpong ) and perhaps @achmafooma (if he has or is going to contribute to this plugin) should also be listed.

Now I have a minor technical question I believe is rightly included here even though this support ticket has been marked as resolved.

For those of us who installed https://github.com/HongPong/broken-link-checker/archive/master.zip, if we update to Version 1.11.8 as updated by ManageWP, will we run into any database table content losses? I’m concerned about losing what’s been indicated as “false positives,” Dismissed, and any of the “link-checker-settings,” especially the “Exclusion list.”

What if anything will I need to back up in one form or another and manually add back in?

Thanks!

@tomusher good question. I would defer that question to @hongpong since it’s his fork, but at a glance there should not be any DB loss if @hongpong fork is using the exact same DB structure.

I recommend backing up and testing it, just in case.

On the contributions, I agree that contributors should be listed. We temporarily cleaned up the list to avoid any confusion about the ownership. We will rely on GitHub to put together the final list.