Warning: is_dir(): open_basedir restriction in effect

  • Resolved mkdes

    (@mkdes)


    5 months, 1 week ago

    Upload on server with domain separation realized by open_basedir.

    Warning: is_dir(): open_basedir restriction in effect. File(/wp-content/uploads/2024/05/bg-terrain-position-1) is not within the allowed path(s):

    I know You tell, this is hosting problem, but this is not hosting problem.

    Script use wrong method to generate path.

    Some hosting has domain separation, and Apache path points to the domain directory.

    And then You have to use directory path without slash / at the begining.

    Example:

    If You use path: /wp-content/uploads/2024/05/bg-terrain-position-1 – this generate error

    You should use: wp-content/uploads/2024/05/bg-terrain-position-1 – that’s works fine

    If You want use slash at the begining, You should get full server path.

    Or You can use relative path to wordpress installation catalog – I think this is better solution.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Gerard Blanco

    (@sixaxis)

    Hi mkdes,

    In order to help you troubleshoot this, it would be helpful if you could provide us with some additional information, including your site information. Please?navigate to?Tools?>?Site Health?>?Info,?click on the?“Copy site info to clipboard”?button and paste the information in your reply.

    Thank you.

    Thread Starter mkdes

    (@mkdes)

    My website works fine.

    This is no my website problem, this is plugin problem and I want help You to resolve them.

    Variable $base_url in this code can not start with / if website is hosted into separated catalogs on the hosting which use open_basedir to separate domains catalogs.

    You can resolve this to use relative path.

    https://imgur.com/Yyt6VYH

    Plugin Support Gerard Blanco

    (@sixaxis)

    Hi mkdes,

    When the plugin replaces the path of the old images with the new path, several things need to be checked. For a faulty website, it’s possible that the end result of the source image path is a directory (i.e. the image metadata is empty, corrupted or something else caused by other plugins). Let’s imagine the source was /var/www/site/wp-content/uploads/2024/05, in which case all images in that directory would be replaced with the new image, and that would corrupt a lot of post content.

    To prevent this, we check if something exists that shouldn’t exist, and if that’s the case, we abort the process. On basedir-sensitive websites, however, this leads to a basedir warning, because the correct input here should be a relative and not a full path. In any case, don’t worry, it’s just a warning and not an error.

    I hope that clarifies the matter ??

    Best,

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