Hi.
We're using Views data export to export our datas in *.txt files

It works fine, except ' caracters which are exported in &#039 inside the final *.txt file, which give us "it&#039s cat" where we'd like to have "it's cat"

Any way to fix that ?
Help welcome
Best regards
D

CommentFileSizeAuthor
#3 views_data_export-1865688-3-decode_entities.patch1.25 KBsimon georges
#1 views_data_export-1865688-2-decode_entities.patch708 bytessimon georges

Comments

simon georges’s picture

simon georges commented
Version: 7.x-3.0-beta6 » 7.x-3.x-dev
Status: Active » Needs review
StatusFileSize
new views_data_export-1865688-2-decode_entities.patch708 bytes

Is it better with this patch?

This patch is part of the #1day1patch initiative.

Status: Needs review » Needs work

The last submitted patch, views_data_export-1865688-2-decode_entities.patch, failed testing.

simon georges’s picture

simon georges commented
Status: Needs work » Needs review
StatusFileSize
new views_data_export-1865688-3-decode_entities.patch1.25 KB

Is it because of the empty line?

Status: Needs review » Needs work

The last submitted patch, views_data_export-1865688-3-decode_entities.patch, failed testing.

dbourrion’s picture

dbourrion commented
Status: Needs work » Needs review

#3: views_data_export-1865688-3-decode_entities.patch queued for re-testing.

Status: Needs review » Needs work

The last submitted patch, views_data_export-1865688-3-decode_entities.patch, failed testing.

dbourrion’s picture

dbourrion commented

Hi
Thanks but... as I'm a newbie and as the test of the patch looks failing, sould I try it anyway ?

simon georges’s picture

simon georges commented

@dbourrion, yes, you should, I need to fix the tests, I don't know how yet... but if it works for you, it's a first indication (try the first patch, no need to take the modification of the tests that are within the second patch).
Thanks for your feedback.

dbourrion’s picture

dbourrion commented

Hi
Patch applyed
On my views preview, got a popup with

"Une erreur HTTP AJAX s'est produite.
Code de statut HTTP : 500
Informations de débogage ci-dessous.
Chemin : /dune/?q=admin/structure/views/view/export/preview/views_data_export_1/ajax
StatusText: Internal Server Error
ResponseText : []"

If i go to the real display of that export, got only that on screen :

[]

Before the patch, that real display export was

[]

000000384 FMT L EB
000000384 LDR L -----nlm0-2200000---450-
000000384 035 L $$adune384
000000384 091 L $$adune384
000000384 100 L $$a20121228d2012----k--y0frey50------ba
000000384 102 L $$aFR
000000384 2001 L $$atest2812création$$bRessource électronique$$fJ. Doe$$gsous la direction de D. B

Yes,

[]

was already there but it wasn't a prob before :)

simon georges’s picture

simon georges commented

Wow... Ok. I need to dig deeper... I'm wondering what kind of data you're trying to display.

dbourrion’s picture

dbourrion commented

;)
We're a french academic library http://bu.univ-angers.fr (D6 website)

We're using drupal with the biblio module for a university website (see the production website here http://dune.univ-angers.fr/) where we're collecting our student's academic works.

We have to export some bibliographic data to push them into our ILS (Aleph, from ExLibris) : that's where Views data export comes.
The export takes some field from biblio, and rewrites them so that the result is a TXT files looking like that

000000384 FMT L EB
000000384 LDR L -----nlm0-2200000---450-
000000384 035 L $$adune384
000000384 091 L $$adune384
000000384 100 L $$a20121228d2012----k--y0frey50------ba
000000384 102 L $$aFR
000000384 2001 L $$atest2812création$$bRessource électronique$$fJ. Doe$$gsous la direction de D. B

(it's compliant to ISO2709, a bibliographic numeric way of formatting data that our ILS can manage)

Then, we take the resulting *.txt files to push them into our ILS. It works fine (for the moment, the &#039 things are cleaned AFTER the export with Linux scripts but it should be better to have a clean export ;) )

Don't know if I explain clearly :(

simon georges’s picture

simon georges commented

You did, I just wasn't expecting that kind of data... I'll take another look at trying to patch it as soon as I have the time.

dbourrion’s picture

dbourrion commented

:)

Rebekaloz’s picture

Rebekaloz commented

I need to add custom xml .

lalbright’s picture

lalbright commented
Issue summary: View changes

What is the status here ... the last comment was three years ago. Is this module actively supported still? I too use this module for something unique. We import code snippets into a "Code" content type, and use the Data Export module to export specifically tagged collections of code snippets as fully functional user-extension files for Selenium RC automation testing (also acting as a form of version control and central distribution, as well as being able to provide edits and comments on each block of source).

Would be nice to get this fixed. :) The ability to export code this like is awesome, if we didn't have to do any cleanup after the export.

steven jones’s picture

steven jones commented
Status: Needs work » Closed (won't fix)

Sorry 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 :)