• Resolved dee987

    (@dee987)


    Hi,

    I am receiving an error:

    My whole site when down for a minute when I tried to schedule a post. I didn’t capture the error unfortunately – it was related to Accessibility Checker. However, now I am seeing this message on the back end:

    Whoops! It looks like your website is currently password protected. The free version of Accessibility Checker can only scan live websites. To scan this website for accessibility problems either remove the password protection or upgrade to pro. Scan results may be stored from a previous scan.

    The site is not password protected at all.

    I have the plugin disabled as we get to the bottom of the message. Any suggestions on how to fix this issue. Thanks!

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Chris Hinds

    (@christophermhinds)

    Hi there,

    Our team would like to investigate this. Could you please send us your system information file? You can do that by going to Accessibility Checker > Settings > System Info.

    You can email that information to dev (at) equalize digital (dot) com. Please also link directly to this support topic thread in the body of the email so that we don’t miss it, and post a comment on this thread when you’ve sent the email.

    Thank you!

    Thread Starter dee987

    (@dee987)

    Hi Chris,

    The information has been sent by email.

    Thank you for helping me, Diana

    Plugin Support Chris Hinds

    (@christophermhinds)

    Diana,

    Thank you for sharing that information. Based on what I can see, it looks like this site is running on PHP 7.4 which is ~4 versions behind the current PHP release (8.3). PHP 7.4 reached end of life 2 years ago, and stopped receiving security releases 1 year ago.

    Generally speaking, we strive to maintain backward compatibility for the most recent three releases of WordPress and PHP.

    • Try running a scan again with your browser’s console open, and see if you can capture the specific error code(s) in the console.
    • If feasible, on a staging environment (i.e. not your live site) try upgrading to PHP version 8.1 + and running a scan. You may also need to check other areas of your site when upgrading PHP to ensure nothing else is amiss.

    I hope this information is helpful and gives us some things to try next as we work together to resolve this issue.

    I have the same issue issue too.

    Currently the website is:

        WordPress Version:        6.4.3
        PHP Version:              8.1.12

    I started getting this error after I upgraded the PHP version a few weeks back. In addition, I am getting this error too:

    
    Warning/home/XXXXX/public_html/wp-content/plugins/accessibility-checker/includes/simplehtmldom/simple_html_dom.php84
    
    Warning/home/XXXXX/public_html/wp-content/plugins/accessibility-checker/includes/simplehtmldom/simple_html_dom.php84
    
    : file_get_contents(): https:// wrapper is disabled in the server configuration by allow_url_fopen=0 in on line : file_get_contents(https://WEBSITE/creative/gallery/?edac_cache=1709181813): Failed to open stream: no suitable wrapper could be found in on line

    I only see this issue when I am on admin mode. It is not visible to the public.

    Plugin Support Chris Hinds

    (@christophermhinds)

    Narada,

    Thank you for adding to this thread and for sharing the error information from your site. I’m hopeful that it’ll help us track down the source of the issue.

    I’m asking our CTO Steve to take a look at this. He will review the error information you shared and may follow up with additional questions.

    Plugin Author Steve Jones

    (@stevejonesdev)

    Hi @binku,

    1. allow_url_fopen Disabled: The first part of the warning indicates that the PHP directive allow_url_fopen is disabled in your server’s configuration. This directive allows PHP’s file_get_contents() function (and others) to access files over a network using URLs. When allow_url_fopen is set to 0 (disabled), these functions cannot use URL-based file paths, leading to the warning you’re seeing.
    2. Failed to Open Stream: The second warning is a consequence of the first. Because allow_url_fopen is disabled, the file_get_contents() function cannot open the URL you’ve provided, leading to a “Failed to open stream” error.

    How to Fix:
    Enable allow_url_fopen: To resolve these warnings, you need to enable the allow_url_fopen directive in your PHP configuration. You may need to contact your hosting company to help with this.

    Plugin Author Steve Jones

    (@stevejonesdev)

    We’re closing this ticket due to inactivity, but we’re here if you need us in the future. Please open a new ticket for further assistance.

    Thanks for reaching out to us!

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.