Background import process error

  • Hi again,
    Just wanted to alert you to an error – when I check the box “background import,” and do the import, an error is returned that the file is not found.

    Without the “background process” box checked, the import works flawlessly.

    I tested this on Chrome and Safari with the same results.

    Here is the log:

    Loading...
JavaScript Loaded.
File (testexport15.csv) not found!

    Since I will be importing hundreds of members, I wanted to see if you would be able to fix this before I try the large imports.

    I REALLY appreciate your help and support on this plugin and in the forum. You are a rare jewel. I don’t have much money but I am happy to donate some to your PayPal for your help.

    Thank you,
    Liat

Viewing 11 replies - 16 through 26 (of 26 total)
  • Plugin Author Thomas S

    (@eighty20results)

    I feel horrible for “punting” on this!

    Please let me know if they have any suggestions for how a plugin that relies on the wp_upload_dir() data being correct is supposed to know that they’re modifying the paths under them (if they have a workaround, I’m happy to try and implement it).

    Hi again!
    Don’t feel horrible, I really appreciate your help. I know we can make it work.
    I talked to GoDaddy and from what I understand, the solution is to not use an absolute path when telling the plugin where the file is.

    Tell it instead to “find the uploads folder” instead of “go to path ‘home/uploads…’

    See what I mean?
    And I think it does this, because it does place the file into my uploads folder, it just then can’t find it because it tries to go to an absolute path.

    Another way to find the uploads folder is to tell the plugin to go into the database and read the upload path.

    Would either of those to changes work to find the correct folder even if the user has a custom file structure?

    Thank you!
    Hugs,
    Liat

    Hi Thomas, does what I wrote make sense? Do you think you can change the plugin a little to find whatever the uploads folder is?

    I know you are busy, I just need a little hope! Thank you,

    Liat

    Plugin Author Thomas S

    (@eighty20results)

    Hi Liat,

    Apologies for the delayed response, but have been offline for a few days.

    I understand what you wrote, so thank you for investigating.

    I just arrived at my destination after 24hours of air travel, so will need to revisit this tomorrow.

    • This reply was modified 6 years, 7 months ago by Thomas S.

    Thank you so much, Thomas!
    Have good rest ??

    Liat

    Plugin Author Thomas S

    (@eighty20results)

    Hi again,

    So the plugin uses the result of the wp_upload_dir() function call for the path to the import .csv file.

    If HostGator has decided to modify the return of that, but not update the path in the call, I don’t know what more I can do.

    It’s a standard WordPress function, and HostGator apparently has decided to override how they handle the path to it in the underlying file system (without seemingly making sure nothing breaks in the WordPress platform).

    Since wp_upload_dir() also has a filter, I would have expected them (HostGator) to have taken the time to make sure any calls to wp_upload_dir() returns the (different) path they actually upload to…

    We’re kind of stuck here.

    It seems to me like HostGator has made half-tested changes to how they expect WordPress to function, but they’re not providing any documentation on how to actually deal with it in a way that allows a plugin to work on _any_ platform.

    I’m personally not a fan of HostGator for (amongst other) this reason, but I’m genuinely willing to try and figure out how you can make my plugin work with their apparent non-standard behavior.

    • This reply was modified 6 years, 7 months ago by Thomas S.

    Thank you so much Thomas!

    I am having the people at GoDaddy (it’s not HostGater, although it doesn’t really matter) look at this and specifically what you said.

    Thank you!

    Hi Thomas,

    Just wanted to update you – looks like this is not an issue with Paid Memberships Pro – Import Members from CSV at all. ??

    Still waiting to hear more, but here’s what I heard from GoDaddy:

    “This is not a plugin issue, it’s connected with w3 total cache that was installed before, we have to clean that.

    Somehow path to the uploads folder is cached, and whatever I do, it’s always trying to follow old path…”

    Yay!
    Liat

    Plugin Author Thomas S

    (@eighty20results)

    Thank you for the update!

    I’ve been trying to figure out if I could work around your specific case, but couldn’t think of a way without rewriting portions of how WordPress handles the paths to the uploads directory, so that wasn’t really an option. ??

    Thanks Thomas!

    So just to close this issue, it turns out that yes, the upload path was being cached due to an old installation of WP Cache. We cleaned up those files and the import process works perfectly now.

    Thanks!

    Plugin Author Thomas S

    (@eighty20results)

    Awesome. Thank you for updating the status!

Viewing 11 replies - 16 through 26 (of 26 total)
  • The topic ‘Background import process error’ is closed to new replies.

Tags