Support multilingual sites

Actually, that check may not be needed anymore. It was a check which was in for D6 and is still there in the D7 version. I'll look at the code in a bit and see if I can recommend a line to comment out to test your import.

Cheers,

Kevin

If you comment out

includes/profiles/nodes.inc
lines 63 to 67

includes/profiles/taxonomy_terms.inc
lines 67 to 71

it will remove this check which was put in for the D6 version - D7 may be more multi-lingual by default.

This is untested by myself so make sure you only do this on a test system. Any feedback about how it worked would be gratefully received.

Same problem

Could you let me know the result from carrying out the suggestion in #2 ?

I confirm that suggestion in # 2 is working fine. Can you please let me know where the dataset file will be stored once the export is done? I am doing it right now and my data is huge, so it will take a while. Thanks for the great module.

OK, I got it. The file will be stored in sites/default/files/data_export_import/

One last question: can I open the exported dataset in Excel or Notepad? I would like to create a CSV file from my exported nodes. Is this possible?

You won't be able to open the dataset file in Excel.

The dataset file contains the serialised node objects and any attached files will also have been serialised and base64 encoded. This is so it is almost a 'native' format when we recreate the nodes.

There may be other modules which may export to CSV which you may be able to use.

The thing is that node objects contain data and meta-data - and some fields can hold more than one value. To get all that into a CSV file is going to be very difficult. It would probably need to use XML at least.

Maybe the 'data' module will be of help - this links to tables in the database which are not part of Drupal.

Cheers,

Kevin B

OK - so it may be that the D7 version can be easily changed to be multi-lingual.

To add this it would need proper testing and adding to the docs.

I'm going to mark this as a postponed feature request until either a patch or sponsorship is supplied.

As multi-lingual sites are not default I'm going to leave this as a feature request. It may take quite a bit of work to get this module to be fully classed as multi-lingual - or it may take commenting out a couple of lines of code. Either was would require proper testing.

Currently I have no need to create a multi-lingual version of this module - but would be happy to accept patches or a proven coder as a co-maintainer to implement the multi-lingual functions.

The D7 version of this module has now been tested with multilingual content. Further testing may need to be carried out - but content language is exported and imported.

So, the D7 version looks like it works with module i18n.

This may be a feature required by someone for D6 - but as that has not been asked for yet I'm going to close this bug (for D7).

No, Still i have this issue, Am struggling on this. please help on this.
Error - "The data export functionality is not currently compatible with internationalization (i18n)."
While create dataset file am facing this issue.

This would be the almost perfect module for moving stuff from production site to a dev site, which would be the new production site, but I also run into this problem.

The problem still exists.

Workaround #2 fixes it.

bailey86, please could you make a new release including #2?

Thank you!

Yes - an updated dev version would be great.

Hi, greetings to @all.

I was trying to create an export from a D6 site, but I received this message -> "The data export functionality is not currently compatible with internationalization (i18n)"... and I can't get the dataset.

Well, ok. I'm looking for the #2 solution but I don't have any nodes.inc or taxonomy_terms.inc in /includes within this D6. LOL

So, what can I do?

Hi, we have lots of content (with lots of images in it) and export is really slow. Can I somehow exclude images from the exported data?