Hi,
Is it possible to put borders on the filled cells in exported excel document?
Thanks!
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | views_data_export-2027433-3.patch | 857 bytes | les lim |
| #1 | views_data_export-xls_headers.patch | 422 bytes | les lim |
Hi,
Is it possible to put borders on the filled cells in exported excel document?
Thanks!
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | views_data_export-2027433-3.patch | 857 bytes | les lim |
| #1 | views_data_export-xls_headers.patch | 422 bytes | les lim |
Comments
Comment #1
les limExcel will draw the spreadsheet with borders if we include a meta tag for ProgId that identifies the export as an Excel sheet. Patch attached.
Comment #3
les limSame patch with updated tests.
Comment #4
priti197 commented#3 patch still not applying any borders in exported excel document. Any idea ?
Comment #5
steffenr@Les Lim - thanks for supplyinga patch for this issue - i just tested this patch with office on my Mac / Office 2011 and it's working fine for me.
Comment #6
steven jones commentedAs per https://drupal.org/node/2204803
Comment #7
les lim@Steven Jones: XLS is a currently supported format, though, not a new one.
Comment #8
les limSetting back to "Needs review" for the moment.
Comment #9
les limRemoving tag.
Comment #10
steven jones commentedSorry for the lack of attention to your issue, please accept my apologies.
Drupal 7 is going to be end-of-life'd by the community in approximately 1 month.
As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on #3492246: Close down Drupal 7 issues.
If you feel like this issue has been closed by mistake, please do comment about re-opening it.
If you feel like the ticket is still relevant for the 8.x-1.x version of the module, then please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.
Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated.
The Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :)