I was wondering if there is planned support for CCK fields being pulled in from the xml. I have a pach that I had to add to get this to work but its depending on xml structure. Also I had to change$html->head; to $html->elements; to get this module to pull in the data correctly , it may be a version change for XSLT.

CommentFileSizeAuthor
#6 xliff.zip49.05 KBnanobyt3
#5 XLIFF.zip42.39 KBnanobyt3
#3 xliff.zip32.44 KBnanobyt3

Comments

bryanschnabel’s picture

bryanschnabel commented

I've been supplying the XSLT for this module. I would be happy to make the kind of update you refer to. Could you send me a sample of the XML input and I can figure out what the XSLT needs to do.

- Bryan

nanobyt3’s picture

nanobyt3 commented
Title: Support for CCK feilds » Memory limit
Category: feature » bug
Issue tags: +XLIFF Tools

I am trying to extend this module to include CCK fields of some selected type.
During XLIFF import, I am using node_save() to create/update translated content. This works fine for about a hundred node imports.
But, when the import reaches around 160+ nodes, I get a PHP error saying 'memory size exhausted'. I have allocated sufficient amount(about 1024MB) of memory to PHP.

Please suggest?

nanobyt3’s picture

nanobyt3 commented
Title: Memory limit » Support for CCK fields
StatusFileSize
new xliff.zip32.44 KB

I am attaching my under-development module which provides facility to import textual(textfield, textarea) CCK fields. The issue of "memory limit exceeding" seems to be concentrated in the function xliff_import().

bwinett’s picture

bwinett commented

Note that the version in #3 is a huge jump in functionality, enabling export of sets of nodes (including CCK fields) via a view and VBO, and import of translated nodes in XLIFF files.

Although not perfect (because of the memory issue), this enhancement provides working functionality, so I hope that we can move forward with this version and get eyes on it to resolve the memory issue.

nanobyt3’s picture

nanobyt3 commented
Category: bug » task
StatusFileSize
new XLIFF.zip42.39 KB

The attached archive includes latest development of XLIFF module. A new multilingual export functionality to export content in user selected language has been added. This is mostly useful in keeping a backup of translated content. Note that, import of content exported using multilingual functionality is not supported. Also there are some minor enhancements and bug-fixes to the existing XLIFF export/import functionality.

nanobyt3’s picture

nanobyt3 commented
StatusFileSize
new xliff.zip49.05 KB

The latest development version of XLIFF module is attached. Below is a list of major changes/enhancements:

  1. XLIFF Export: Support for taxonomy module. This adds ability to filter using terms/tags.
  2. XLIFF Export: 'Translate this' flag added to node forms of multilingual content-types. Filter can be done using translate this flag.
  3. XLIFF Export: Ability to export all content (Earlier, export only consisted of nodes having no translations at all).
  4. XLIFF Export: Content type selection relocated from 'Settings' tab to 'Export' section under 'Export/Import' tab.
  5. XLIFF Export: Rearrangement of export filters.
  6. XLIFF Import: Added a sub option under 'Skip node version ID check' to mark translations of nodes with mismatched version ID's as outdated.
  7. XLIFF Import: Ability to skip re-pointing of node-references where a node reference belongs to selected content type(s).

Do test and report back any issues found.