PHP Warning is_readable

  • Resolved Jos Klever

    (@josklever)


    2 years, 9 months ago

    I’m seeing these warnings in the error log of a client’s website. Version 2.6.1 is installed and everything else is up to date as well. It looks like the path should be prefixed but it isn’t. Can you check this?

    AH01071: Got error 'PHP message: PHP Warning: is_readable(): open_basedir restriction in effect. File(/includes/fbwpml.php) is not within the allowed path(s): (/home/**/:/tmp/:/var/tmp/:/opt/alt/php74/usr/share/pear/:/dev/urandom:/usr/local/php74/lib/:/usr/local/php74/lib/:/usr/local/php73/lib/:/usr/local/lib/php/) in /home/**/domains/**/public_html/wp-content/plugins/facebook-for-woocommerce/includes/Integrations/Integrations.php on line 61'

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support laceyrod a11n

    (@laceyrod)

    Automattic Happiness Engineer

    2 years, 9 months ago

    Hi there,

    Thanks for reaching out.

    We do have an open bug report for this if you’d like to take a look: https://github.com/woocommerce/facebook-for-woocommerce/issues/1642

    It has been fixed for Windows+IIS+PHP+open_basedir configuration but could be existing on other configurations still.

    Would you be able to confirm if this is what you’re running into?

    Thread Starter Jos Klever

    (@josklever)

    2 years, 9 months ago

    This site is running on CentOS + Apache/Nginx and it started today. I’ve asked the client if they changed anything on or around the site. But I can’t find any lead in the access log.
    The only thing I know that has changed is the PHP version. That was just before updated from 7.4.20 to 7.4.21. The changelog can be found at https://www.php.net/ChangeLog-7.php#7.4.21
    and I think it’s related to this bugfix: https://bugs.php.net/bug.php?id=76359

    The solution in the bug report sounds good, but I don’t have time to test it right now. Hopefully soon.

    Plugin Support Ena P (a11n)

    (@drwpcom)

    2 years, 9 months ago

    Hi @josklever,

    I’m going to go ahead and close this thread as there is a relevant Github issue. Please feel free to comment there if needed, or to comment here once more if your issue is a separate one.

    Thread Starter Jos Klever

    (@josklever)

    2 years, 9 months ago

    I’m not familiar with the whole Github thing, and the ticket is quite old without much progression, so I would like to have an update first about the status. When will this be fixed in an update of the plugin? Why isn’t there any update in the investigation for the last 7 months?
    Just closing a support ticket as solved and doing nothing is not how this should work.

    Thread Starter Jos Klever

    (@josklever)

    2 years, 9 months ago

    I’ve manually applied the on Github proposed fix yesterday and I haven’t seen any error since. So please implement the solution in the next update.

    Plugin Support Shohan Hossain Nabil – a11n

    (@sohanhossain)

    2 years, 9 months ago

    Hello @josklever,

    The issue has been marked as low priority by our developers on 16th April as you can see on the GH page:


    Link to image: https://d.pr/i/AyDoIj

    This means this is already under their radar and it will be fixed soon. However, we do not have any ETA at this moment. For now, you can use the solution provided on the bug report page.

    Thanks!

    Plugin Support Shohan Hossain Nabil – a11n

    (@sohanhossain)

    2 years, 9 months ago

    Hey there!

    I’m going to mark this as resolved – please continue following the issue in Github for further updates.

    Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘PHP Warning is_readable’ is closed to new replies.