WordPress.org

Support

Support » How-To and Troubleshooting » [Resolved] Import path problem

[Resolved] Import path problem

  • I’m trying to import WordPress to WordPress using the exported .XML file. Hostcentric is my ISP. There seems to be a path problem. the backslash notation switches to frontslash notation. Thanks in advance if anyone can tell me how to fix this or what I should ask my ISP to do to fix this. I used X’s to sanitize the paths.

    Import WordPress

    Warning: gzopen(\\XXXXX\home\users\web\bXXX\XXXXXXX\blog/wp-content/uploads/\\XXXXX\home\users\web\bXXX\XXXXXXX\blog/wp-content/uploads/2009/01/wordpress2009-01-23xml11.import) [function.gzopen]: failed to open stream: No such file or directory in \\XXXXX\home\users\web\bXXX\XXXXXXX\blog\wp-admin\import\wordpress.php on line 73

    Warning: gzopen(\\XXXXX\home\users\web\bXXX\XXXXXXX\blog/wp-content/uploads/\\XXXXX\home\users\web\bXXX\XXXXXXX\blog/wp-content/uploads/2009/01/wordpress2009-01-23xml11.import) [function.gzopen]: failed to open stream: No such file or directory in \\XXXXX\home\users\web\bXXX\XXXXXXX\blog\wp-admin\import\wordpress.php on line 73

    All done. Have fun!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi myself, why don’t you contact Hostcentric and see what they say. OK, I did, we’ll see what they say. I told them:

    “I get an error importing from another WordPress installation using the import feature. The error leads me to believe there may be either a problem with the PHP realpath or a permission problem. Here is the errror message:”

    I cannot believe this. According to my webhost they did not do a thing and yet exact same imports that failed yesterday work today. OK, MAYBE another engineer fixed something on their server and the person servicing me was not aware of it. But not the error is gone away. I wish I could say what fixed it for future readers, but I can’t. Here is what Hostcentric said:

    “We did not change any code in your account. According to the error message given below it seems to be issue with the incorrect path.

    Warning: gzopen(\\frigga\home\users\web\b356\hoc.vs-cc1987\blog/wp-content/uploads/\\frigga\home\users\web\b356\hoc.vs-cc1987\blog/wp-content/uploads/2009/01/wordpress2009-01-26xml2.import) [function.gzopen]: failed to open stream: No such file or directory in \\frigga\home\users\web\b356\hoc.vs-cc1987\blog\wp-admin\import\wordpress.php on line 73

    It looks like you are changed the path which fixed the issue.”

    frizzled,

    I got a chuckle when I read your solution. Was hoping for something with a bit more substance ’cause I am currently in the same predicament you were. Maybe I’ll give my host a call and hope for a little magic. 😉

    I was able to actually resolve this problem. Basically, the script is complaining b/c it’s got the incorrect path to the file that you just uploaded (your import file). To fix this, I had to log into my web hosts control panel to get my directory, then I had to adjust the script as follows:
    1) Determine your path from your web hosting company.
    2) Open file file: wp-admin\import\wordpress.php (I used Dreamweaver, but you can d/l via FTP, then use notepad).
    3) Look for the function “get_entries”. Then find the line that starts with “$fp =…”. It was line 101ish for me.
    4) Right above that line, add this:
    $this->file = “\\\\path\\folder\\folder\\blog\\wp-content\\uploads\\2009\\10\\wordpress.2009-10-26.xml3.txt”;
    5) You will have to change the “2009” and “10”, most likely too.
    6) Save and close.
    7) Refresh your import. It should now work.

    *Note that you are hard coding the file to import, so you need to make sure that the file exists in the directory that you are pointing to.

    leet8845

    @leet8845

    Thanks bgoldstein,

    I followed your instructions. On step 4 I changed it to my file path and it all worked perfect.

    I don;t know how you figure this stuff out but well done, you saved me a load of time was about to start copying and pasting 🙂

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Resolved] Import path problem’ is closed to new replies.
Skip to toolbar