davedi

Hi Alex.

Sorry for the delayed reply…

1) I use Microsoft Excel to open the CSV files, but I also see a single line in notepad and notepad++. I am running these on a Windows machine.

I’d have to clean up (remove a lot of customer data) before sending you a sample… I can tell you that the CSV file that is not working does not have Carriage Returns or Line Feeds ( “\r\n” ) after each record. Let me know if you would still like the file and I will clean it up.

2) I can change the “xls” extension to “csv” when I save (the working file) and that does open up in Excel as you would expect a CSV file to open. So that is a work around, but some people may not know to do that or just click too quickly and wonder why the file is not opening properly.

If you end up adding the time out, I think it would be good if it were configurable just so people have the option and can avoid “hanging” their server. At this time, I don’t know that you need to as the time out (at least not for me) as I am able to easily export hundreds of records in just a few seconds.

Thanks again for all of your efforts.

Dave

Hi algol.plus.

Thanks for your help on this issue. I wanted to let you know how it went with version 1.2.1:

I tried version 1.2.1 and have a couple issues, but **I think (see issue #1 below)** I am getting all of my orders in the export file.

The issues:

1) The CSV file that is produced does not appear to have line breaks. When I export, I get the header and all the orders on one line.

2) Even though I choose CSV as my export format (and that is what comes out) I am always prompted by my browser to save a “.xls” file. If I forget to change the file extension (or if somebody does not know to do this) MS excel can’t open the file.

2a) I also noticed the “file extension issue” in the pro version (Advanced Order Export For WooCommerce, Version: 1.1.13) of the plugin that I purchased as well.

Thanks again for your help.
Dave

Hi alanstorm. Thanks for your suggestions. I am sure both would work to solve the export issue. In fact, I just enabled sticky sessions and that did work consistently.

We went away from sticky sessions early on when we were running just a few smaller servers that were failing during traffic spikes because (it seemed) the bulk of the traffic did not spread to the new servers in a timely fashion. Perhaps now, running larger and more servers, sticky sessions will not be an issue.

Algo.plus, I will try your new version in case sticky sessions are an issue for us. Any issues with temporarily setting the max execution time in your script higher (via a configurable plugin setting) when using the no progress bar option?

Thanks again to you both.
Dave

Hi Alex.

Sorry for the delayed response… gmail put these emails into the “social” bucket and I just saw your last response.

Thanks for working in the “single request” feature. I will try the new plug-in with multiple servers and let you know.

Understood about the 300+ orders. One workaround could be using an S3 bucket (if configured in your settings) to store the chunks of files instead of the local server.

Thanks again,
Dave

Hi. I am just starting to work on a similar use case.

I think you would not want to edit the plugin files directly as your customizations would be overwritten during an upgrade. That being said, you can find info on filters and actions (that you would use in your functions.php file) here: https://www.iptanus.com/wordpress-plugins/wordpress-file-upload/ (Scroll down to “filters/actions”).

If you have not already found how to add custom fields look here: https://www.iptanus.com/the-new-form-fields-of-wordpress-file-upload-plugin/

Those are my next/first steps.

Good luck and let us know what you find.