Closed (outdated)
Project:
TableField
Version:
7.x-2.1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Dec 2012 at 14:49 UTC
Updated:
12 Aug 2016 at 06:23 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
kevin hankens commentedHey, thanks for the report, if you can give me some more info I can help debug it. Is there any way you can describe your table field settings and give me some example data? Also, feel free to direct message me a link where I can see it in action.
Thx!
Comment #2
benevides commentedHello Kevin, thanks for your reply. I am sending the link to my table so that you can download.
http://www.proppi.uff.br/sistema-financeiro/node/5
Comment #3
kevin hankens commentedWe should probably explicitly set it to enclose values in quotes. Can you try the attached patch?
Comment #4
kevin hankens commentedActually, on closer inspection, the CSV file that I got from your server looks ok. The first three rows look like:
Also, what are you using to view the CSV? Are you seeing something different when you open the file in a text editor?
Comment #5
benevides commentedstill not working.
Results in a single column table.
Comment #6
benevides commentedI'm using excel to open the resultant tables. In a text editor this table looks like this:
Comment #7
kevin hankens commentedOk, thanks, now we're getting somewhere! Now to start deducing :)
We know that the columns are intact, comma separated and enclosed in quotes. The one inconsistency that I immediately see is that when the last column is empty, there isn't an empty quote "". I wonder if that could be it.
Can you copy and paste the first two lines into a new .csv file using a text editor, then open that in excel?
If that doesn't work, can you try enclosing the 12 in quotes?
Let me know if either of those generate the proper columns.
Comment #8
benevides commentedNone of my tries did work. First two lines still giving me a table with one single column, and wrapping 12 in quotes didn't help either.
I'm wondering if this could have some thing about special characters in the table.
Sorry I'm a noob "front end" user, can't help much and my english is a crap. But I will do what I can to help.
This is a great module! We could have a way to download a .xls file. That would be great!
Comment #9
kevin hankens commentedBummer. I was hoping it would be something easy :)
No worries, I'll do some googling to see if there are any obvious solutions. I'm using libre office here and it seems to interpret the columns correctly. That said, there are way more people using excel, so it will be good to solve this properly.
There are some libraries for saving xls files, but it's a difficult business. Hopefully we can figure this out and just use CSV files as they are so much simpler.
Keep in touch if you figure anything out!
Comment #10
benevides commentedOk, using www.libreoffice.org, and setting the document to UTF-8 the table works like a charm.
Comment #11
jenlamptonThis is a very old issue, and I cannot reproduce it today. If the problem persists please reopen.