Biplav

Hey, @digitaldog247
We’re looking into the issue and probably update the plugin with a fix very soon.

Thank you for your patience.
Best regards.

Hello @sunflowermom ,
The log file is for debugging purpose and you can disable it if you didn’t turn it on deliberately.
Also if you decide to leave it turned on, the latest version of BLC there’s the option to clear log-file on a select time interval. You can find this setting on Settings->Link Checker->Advanced->Log file clear schedule

Hope this helps.
Best regards,
Biplav.

Hello @a4jpcom ,

You can create an API key with the help of instructions here, https://developers.google.com/youtube/registering_an_application

Then you can add that API on the plugin settings ( Settings -> Link Checker-> General -> YouTube API Key )

Hope this helps,
Best regards.

Hello @pathduck ,
Sorry I missed to put the credit up earlier.
I have updated the changelog and added the credits there.
Thank you for taking out your time to report the issue and helping us out with it we really appreciate that.

Best regards,
Biplav.

Hello @dpartridge

Can I get the link that is responding with that particular error code?
I don’t recall any changes on the current version that could have caused the error you explained.

Can you also try and rollback to the 1.11.12 on the site that is recording this error to see if the issue still persists just so we can make sure the issue is with version 1.11.13?

Best regards,
Biplav

Hello @larsmagne23

When editing those broken links you will be able to see the archive.org suggestions if there are any.

Best reagrds,
Biplav.

Hello @gaambo ,
Thank you for taking the time to report the issue,
You’re right we are removing the SQL query and added a WP_Query to fetch posts on the plugin this update because that’s more optimized and convenient way of fetching the posts.

For the pre_get_posts that was a really nice catch, but I think the plugin you’re using can do a better job at identifying when the use that hook and when it should be just ignored.
However, we’ll check if we can fix those on the plugin as well.
If I find any quick fix after a detail review of the plugin I’ll post it as well.

Best regards,
Biplav.

Hello @dan00neuffer
I hope you’re doing good today.

To answer your first question, Not broken is the best way to mark false positives.

For the actual link fixes if you edit the link on the plugin’s link checker dashboard itself it will show on the dashboard immediately, if you directly edited it on the source it might need some time to run the check again, or you can use the force recheck on the Settings->link checker->Advanced->Re-check

Hope this helps,
Best regards.

Hello @colinsp ,
Yeah that is possible to you’ll have to add the edit_others_posts to your custom user role.
You can do that via the User Role Editor plugin or you can add the following code on your child theme or a custom plugin. Just make sure you change the role slug and replace it with your actual role slug.

function wpmudev_simple_role_caps() {
    $role = get_role( 'sample_role' );
    $role->add_cap( 'edit_others_posts', true );
}
add_action( 'init', 'wpmudev_simple_role_caps', 11 );

Hope this helps.
Best regards,
Biplav.

Hello @almendron ,
Thank you for reporting this, we’ve seen this issue with GoDaddy hosting where WordPress installations there have mixed collations of database. They don’t respect the default collations and use their own set collations while creating default tables ( in this case utf8mb4_unicode_ci ) and when creating the custom tables they use WP’s collation ( in this case utf8mb4_unicode_520_ci ) which is causing this error.
We have tried to fix this from the plugin but unfortunately we couldn’t.
Furthermore, this may also be causing errors with other plugins that rely on the post table or make changes to it.
You’ll probably have to check in with your hosting about this and see if they could use the standard charset for this?

Best regards,
Biplav.

Hello @kalynbrooke ,
If you’ve marked the link as unbroken it will still be available at the All tab and if you recheck the link again it’ll show the links status again.
Please let me know if that helps.
Best regards,
Biplav.

Hello @panhead

Thank you for your feedback and we’re sorry you’re facing this inconvenience.
We’re aware of the plugin making expensive queries and we’re trying to fix that on the upcoming updates.
Unfortunately we don’t have any ETAs and this is going to be a gradual change but the future updates will certainly look to optimize this.

Best regards,
Biplav.

Hello @archon810
Yeah it’s true we tried to run the DB queries again because of the issue that was reported here just to optimize them and make them a little better, this is just a foundation for the next future updates where are trying to stop running these expensive queries.

Thank you for your patience.
Kind regards,
Biplav.

@blogodisea Glad that’s working for you. I don’t think you’ll face those issues now since the table is already updated. But if you do please let us know.

@archon810 Yeah that’s where the whole process started, we’re trying to fix that but that’s a long process and with trying to do it safely for all our users.
I’ve replied on the tread with more details and how we’re handling these more on the future updates.

We’re really sorry for any inconvenience caused,
Best regards.
Biplav.

Hello @igramnet ,
The error you’re getting is because of the open_basedir module enabled which blocks following the redirect URL while curling a site. It’s nothing to worry if your URL is not redirecting to anything but I must warn you that if your URL is redirecting the plugin won’t be able to check properly.

The log just pops up if you have that module enabled and is just kept for debugging purposes.

We are trying to make the plugin compatible with the module in the future updates but unfortunately we don’t have any ETAs for that. I will keep updating the thread if we make any progress there but for now you can ignore that warning. ??

Best regards,
Biplav.