Some cases when replace is not optimal

  • Resolved codernize

    (@codernize)


    4 years, 2 months ago

    Hi there,
    have been debugging some problems, and I come to the conclusion that on autoload function for wp-all-export-pro.php file the $pathAlt ( I see it done in two different ways) is eventually replaced with str_replace (or lreplace method first), but that may throw erros if the abspath has _ in it. So if the hostname is like /home/someuser_33/public_html/wp-content… then the path is replacding _ with DIRECTORY_SEPARATOR . So I just did
    $pathAlt = self::ROOT_DIR . '/' . $subdir . '/' . str_replace('_',DIRECTORY_SEPARATOR, $filePathAlt);

    This might solve some is not within the allowed path(s) errors

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author WP All Import

    (@wpallimport)

    4 years, 1 month ago

    Hey @codernize,

    I come to the conclusion that on autoload function for wp-all-export-pro.php file the $pathAlt ( I see it done in two different ways) is eventually replaced with str_replace (or lreplace method first), but that may throw erros if the abspath has _ in it.

    Thanks for the heads up. I’ll ask our developer to review this.

    Plugin Author WP All Import

    (@wpallimport)

    4 years, 1 month ago

    Hey @codernize,

    Our developer confirmed that this could cause issues. We will implement a fix in a future release.

    I’m marking this as resolved for now but let me know if you have any questions.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Some cases when replace is not optimal’ is closed to new replies.