Feb 13th, 2010, 12:41 PM
(Feb 12th, 2010, 9:46 PM)Ben Wrote: Excel, once it's decided the column is a date column, there's no way to convince it otherwise.
Yes, Excel is sometimes too smart for its own good!
(Feb 12th, 2010, 9:46 PM)Ben Wrote: Instead, you can tackle it via the Export Manager export type - you'll need to edit that Smarty markup to either reformat the field value right there, or maybe add a space at the end (or start) of the <td> cell. The latter is easier to do, so maybe give that a go first.
Can you offer me a little more explicit instruction on this point, please, Ben? I'm a web designer/builder in HTML/CSS, but Smarty is new to me.
First, please help me make sure I'm in the right place...
The Smarty markup you're looking at is reached through the FT admin interface for the Export Module, right? Attached to {$LANG.export_manager.phrase_table_format}? There I see markup that clearly builds the HTML tables, though it's less obvious that the same template is used for the Excel export.
If that's the right place, then I see that the template already includes a bunch of spaces at both the start and end of the cell, inserted for readability of the Smarty code. But those spaces don't actually factor into the export, do they? I probably need to ask Smarty to include a space in some explicit way, perhaps at this point in the code:
{elseif $field_type == "textarea"}
{$value}
Sorry to need this hand-holding,
Jim