• Resolved Mark Oppenneer

    (@moppenneer)


    Hi there.

    I have used Broken Link Checker for a long time until our server admin changed a server setting which broke the plugin functionality. He did this on purpose – and gave an explanation for his decision (see the summary of his statement below). He changed a few lines of the plugin code and BLC is now working. He sent me some wording for a message to you in case you wanted to make the change part of the official BLC code. Here’s what he wrote:

    Summary: We have a restricted set of URLs that our WordPress environment is allowed to connect to. This is accomplished by routing outbound WordPress traffic through an HTTP forward proxy server. However, the link checker needs to be able to reach pretty much anything on the internet, so I made some small changes to do the following: 1) Add an option in the BLC admin screen to set a proxy user and password, 2) if these configuration items exist, BLC will use those credentials for proxy authentication instead of those set in the wp_config.php.

    Here is the code snippet he sent me to share with you:

    diff -r broken-link-checker-orig/legacy/core/core.php broken-link-checker-fork-2.2.2/legacy/core/core.php
    680a681,684

    //http_proxy
    $this->conf->options[‘proxy_un’] = ! empty( $_POST[‘proxy_un’] ) ? $_POST[‘proxy_un’] : ”;
    $this->conf->options[‘proxy_pw’] = ! empty( $_POST[‘proxy_pw’] ) ? $_POST[‘proxy_pw’] : ”;

    1222a1227,1264

    type=”text”
    name=”proxy_un”
    id=”proxy_un”
    value=””
    class=”regular-text ltr”>

    type=”password”
    name=”proxy_pw”
    id=”proxy_pw”
    value=””
    class=”regular-text ltr”>

    diff -r broken-link-checker-orig/legacy/core/init.php broken-link-checker-fork-2.2.2/legacy/core/init.php
    106a107,108
    ‘proxy_un’ => ”,
    ‘proxy_pw’ => ”,
    diff -r broken-link-checker-orig/legacy/init.php broken-link-checker-fork-2.2.2/legacy/init.php
    123a124,125
    ‘proxy_un’ => ”,
    ‘proxy_pw’ => ”,
    diff -r broken-link-checker-orig/legacy/modules/checkers/http.php broken-link-checker-fork-2.2.2/legacy/modules/checkers/http.php
    211c211,217< if ( defined( ‘WP_PROXY_USERNAME’ ) ) {

    if (! empty( $conf->options[‘proxy_un’] )) {
    $auth = $conf->options[‘proxy_un’];
    if (! empty( $conf->options[‘proxy_pw’])) {
    $auth .= ‘:’ . $conf->options[‘proxy_pw’];
    }
    curl_setopt( $ch, CURLOPT_PROXYUSERPWD, $auth );
    } elseif ( defined( ‘WP_PROXY_USERNAME’ ) ) {

    Please let me know if you have any questions – I’ll be glad to pass them along to the person who made these recommendations.

    Cheers,
    Mark

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Kris – WPMU DEV Support

    (@wpmudevsupport13)

    Hi @moppenneer

    I hope you are doing well today.

    Thank you for all the data. I will pass them to our developers for a full review. Thank you for your patience while we look into this further and we will post an update here as soon as more information is available.

    Kind Regards,
    Kris

    Plugin Support Kris – WPMU DEV Support

    (@wpmudevsupport13)

    Hi again @moppenneer

    Our developers made a review of your request and we are considering adding this as an update in future updates. Please note we have multiple request and lower and higher priority and at the moment we do not have ETA when this will be implemented.

    Kind Regards,
    Kris

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @moppenneer,

    Please do note that we have raised this as a feature request to our BLC team so that we could check the possibility of implementing such a feature down the roadmap.

    While we cannot provide a specific timeline yet, you can get updates on our upcoming feature by subscribing to our roadmap at:

     https://wpmudev.com/roadmap/

    Since this feature request has been acknowledged, we’re marking this as resolved for now. However, if you have any queries, please don’t hesitate to ask. Thank you for your understanding.

    Best Regards,

    Nithin

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Setting a proxy user and password’ is closed to new replies.