Support

October 22, 2015 at 10:16 am

Hi Tony,

I believe the issue is server side. The rendered text is not CSV compliant without some manual processing and appears across multiple browsers.

I have tried IE 11.0.96, Chrome 46.0.2490.71 m and FireFox 41.0.2 on this Windows 7 workstation as well as Chrome on a Surface Pro 3 running Windows 8.

The text rendered looks like this:

”Transaction ID[TXN_ID]”,”Attendee ID[ATT_ID]”,”Registration ID[REG_ID]”,”Time registration occurred[REG_date]”,”Unique Code for this registration[REG_code]”,”Count of this registration in the group registration [REG_count]”,”Registration’s share of the transaction total[REG_final_price]”,Currency,”Registration Status”,”Transaction Status”,”Transaction Amount Due”,”Amount Paid”,”Payment Date(s)”,”Payment Method(s)”,”Gateway Transaction ID(s)”,Check-Ins,”Ticket Name”,”Datetimes of Ticket”,”First Name[ATT_fname]”,”Last Name[ATT_lname]”,”Email Address[ATT_email]”,”Address Part 1[ATT_address]”,”Address Part 2[ATT_address2]”,City[ATT_city],State[STA_ID],Country[CNT_ISO],”ZIP/Postal Code[ATT_zip]”,Phone[ATT_phone],positiontitle,company-name,company-type,”On-site vs WebEx” 17774,1644,495,”2015-10-06 13:39:00″,17774-38-1-054c,”1 of 1″,39.00,USD,Approved,Complete,39.00,39.00,”2015-10-06 18:42:00″,Stripe,1N963536TX417753Y,0,”I DO want CLE credit.”,”2015-10-29 16:00:00″,XXFIRSTXX,XXLASTXX,XXEMAILXX,”XXADDRESSXX”,,Nashville,Tennessee,”United States”,37219,XXPHONEXX,”XXTITLEXX”, 17775,1265,496,”2015-10-06 13:51:00″,17775-42-1-e497,”1 of 1″,0.00,USD,Approved,Complete,0.00,0.00,,,,0,”I do NOT want CLE credit.”,”2015-10-29 16:00:00″,XXFIRSTXX,XXLASTXX,XXEMAILXX,”XXADDRESSXX”,,Washington,”District of Columbia”,”United States”,20006,XXPHONEXX,”XXTITLEXX”,”XXCOMPANYXX”,”Law Firm”,…..

(Fields redacted for privacy reasons.)

October 23, 2015 at 8:07 am

Hi Lorenzo,

Thanks for your help!

The one change we have made was adding a site plugin to move some posts into a custom post type with a unique taxonomy. There was a formatting error in the plugin that appears to have broken the CSV export.

What is still odd to me is that the text rendered is not CSV compliant so it’s not just failing to export, but failing to compile correctly. Regardless, the issue appears to be fixed!

Thanks for your help.

October 23, 2015 at 11:10 am

The exported CSV file works fine, but when it simply renders in the browser the beginning of the text string starts with “”, many of the fields appear in quotation marks, and no line breaks are included.

Copying the text into a text processor allows me to strip the “” and quotes. Then I have to do a tricky find and replace to insert a carriage return before the “TXN” field which then breaks the single text string into unique records.

The sample above is the exact text output (fields data redacted) for the first two records and header.

Thankfully the pattern “17774,1644,495,” indicates the first three fields so a search for NNNNN,NNNN,NNN can replace these strings with ¶NNNNNNNNN,NNN to insert the carriage return and delineate unique records.

At that point the file is pretty close to the usual exported CSV.

Regardless, the issue appears resolved and the conflicting taxonomy creation was corrected. We’ll have a better idea of what to look for if this happens again.

Thanks again!