Posts: 2,456
Threads: 39
Joined: Dec 2008
Reputation:
6
Huh...! You're quite right, I can see the problem now. Neat...
I'll look into this tomorrow - I think it'll take a little digging & I have a few other support posts to respond to. Keep you posted -
Ben
Posts: 33
Threads: 6
Joined: Sep 2009
Reputation:
0
Glad you were able to replicate the problem, Ben.
Thanks for your persistence,
Jim
Posts: 2,456
Threads: 39
Joined: Dec 2008
Reputation:
6
Feb 13th, 2010, 12:12 PM
(This post was last modified: Feb 13th, 2010, 12:16 PM by Ben.)
Ah, I found the problem. It looks like I introduced it a few versions ago of the Export Manager when solving another problem.
What happened was that newlines weren't being converted properly to <br />'s in the Print Preview export type, so all text in a single cell was being smushed into a single block. So, I remedied that by adding in a nl2br clause for textarea fields in both the Print Preview and Excel export types. But I guess I didn't QA the Excel type well enough: as you noticed, it's causing it to be broken into multiple cells. On my own installation I wasn't seeing this because upgrading the Export Manager module does NOT upgrade the export content (it can't, because it would overwrite any customizations that people would make). So even though I'd kept my module up to date, the actual export type content was slightly different - actually VERY different. I'd made some significant changes when playing around with it and had unwittingly fixed the newline problem.
Alright, now to fix it...! I'll release an update to the Export Manager module today and then post instructions on the additional manual fix you'll need to do to get it working properly.
Keep you posted!
- Ben
Posts: 33
Threads: 6
Joined: Sep 2009
Reputation:
0
Thanks for keeping me up to date on your progress, Ben.
Jim
Posts: 33
Threads: 6
Joined: Sep 2009
Reputation:
0
Ben,
If you could extend this fix to the CSV export, it would be both a healthy piece of housekeeping AND it would provide me a useful work-around for the problem described in Thread #503.
Jim