Has access for Editors changed?

Hi @mikeywil,

Trust you are doing good and thank you for reaching out to us.

In previous versions of the plugin, users with the Editor role were unable to access the plugin page. We have kept the accessibility of the Broken Link Checker Dashboard widget unchanged, which means users with the Editor role can still access it. A WordPress dashboard widget is a small module or section that provides specific information or functionality directly on the WordPress admin dashboard.

Please feel free to get back to us if you need any further clarification.

Kind Regards,
Nebu John

We have kept the accessibility of the?Broken Link Checker Dashboard widget?unchanged

That is not what he’s referring to… I’m experiencing the same. Users with the capability ‘edit_others_posts’ can not see the (old) broken link checker admin menu.

I have no intentions to switching to a cloud based solution so I’m not going to switch away from the old, so plz don’t suggest it as a solution, because it’s not the solution to my problem.

It would be welcomed if you could add more filter, for example in the function admin_menu, where $this->page_prop('capability') can be overridden…

apply_filters( 'blc_user_access', $this->page_prop( 'capability' ) )

Hi @mikeywil @beee

I checked it and @beee is right (thank you for additional explanation): in pre-2.0 version of the plugin editors (or, in general, anyone with “edit_other_posts” capability) could access list of broken links.

As mentioned earlier, we did not change the “old engine” and it’s actually the same plugin as it was. However, we did move all the menus and pages “under the same roof” and since in new 2.0 version those are only available to admins (or, otherwise, anyone with “manage options” capability), it turns out we have apparently blocked that access at the same time.

There seems to be no filter to override this available currently so if you do stick to “Local (old)” engine, it would be best (for the time being) to downgrade to the most recent pre-2.0 version of the plugin.

With that being said, I have just reported this issue to our BLC team as a bug to be looked into and fixed in future releases (though at this point I’m not able to tell in which version or what would be the ETA).

Kind regards,
Adam