Thomas S

It’s going to depend on the size of the install (# of plugins, etc), but for sites with payment gateways for instance, I tend to want 1-2 minutes as the max_execution_time setting.

That said, since my plugin tries to be smart about how many records it can import per attempt – it’s supposed to cycle through until the file is done – it seems like I’ll need to get a little more flexible in my timeout calculations…

I’m explicitly looking for the JavaScript console status/messages though. If there’s a timeout error, it would most likely get logged there.

That could simply mean that the server is running a little slower than I expected when I guesstimated the amount of time it would take to import ~60 records, and as a result, I haven’t configured enough of a buffer for the JS timeout vs the PHP max execution time.

Thanks for that screen capture.

Are there any Javascript errors in the JS console of the browser you’re using?

Hi,

I’m going to close this topic as I’m presuming you’ve resolved your issue. If not, please open a new thread.

It would also be great if you could include the link for the headers of the .CSV file you’re using to import if you do reopen this topic.

Hi,

It is possible it’s due to a PHP timeout or a JS timeout, what settings do you have configured for the plugin (on the Import Members page) when importing?

Hi,

Thank you for the thorough problem report. I’ll be investigating this over the next day or so and will push out a release as quickly as my schedule permits.

Do you have a deadline you need to meet?

Hi,

You’re getting that error because you’ve added the fields to a portion of the checkout page where they won’t be included if the user is logged in during the checkout (after_email). As a result, the field data isn’t being included in the checkout REQUEST.

You could move them to a different section (below the user/login info).

Thank you for your review!

Your input made me realize I needed to add a bit of information about what the plugin expects (in the FAQ section), as well as a few tests to verify the data for some of the more common errors I’ve seen in the files being used in the import.

Hi,

Have you reported this to the PMPro Support forums? It _sounds_ more like a PMPro issue, but I’d be happy to take a look at your import file to try and understand what may be happening.

I’d need you to include a link to a file containing the .CSV file headers and an example of an entry with the billing information included (from the .CSV file).

Thanks for letting me know.

I’ll update the FAQ to make sure it’s clear what the separator for the .csv must be (comma, as you pointed out).

I’ve updated the plugin with a couple of data file checks during the import (for some of the more common problems I’ve seen within .csv files being imported).

Should be available in version 2.5

Hi,

Would you be willing to share the headers and the 1st line of your import .csv file? (wrap it in the “[code]" button of the edit reply portion on this page).

Figured it out: Had a shopping wizard plugin for WooCommerce that was “misbehaving” (it cleared the cart and re-added everything the product count was incremented).