When I create a node translation I see the original file already attached in my translated node.

For my needs, I have a translated document I want to go along with the translated node. When I attach the translated document, it takes the place of the original document attachment as if I had deleted it (I have allow multiple attachments turned on). When I submit the translated node, it shows that there are two documents with the same title (the translated title). When I roll over each one, one is the original, non-translated filename and the other is the "correct" (translated) filename. When I go to view the original node, it looks fine, listing just the one document associated with it.

I would like for it to either not include the original attachment in the translated node or allow me to replace the existing one, if provided, with a translated one instead of showing both when viewing the translated node.

Perhaps this does not belong with the filefield issues queue, so if not, please direct me to the correct module (CCK?) to address this issue.

Comments

pcorbett’s picture

Also, in the files database table, there are two entries for the translated node (two entries with the same nid). One has the correct translated document and the other lists the original document attachment. In the database, each have different filename and filepaths, which they should. However, when the translated node is displayed, both are listed with the same title (even though the underlying file when you roll-over or click on them is different).

quicksketch’s picture

agrivas’s picture

Subsrcibing.

The reuse of attachments between translations should be optional. If that is not feasible or involves a lot of code, the attachments should not be related (attachments per physical node).

P.S. Does this issue apply to the 6.x branch as well?

quicksketch’s picture

This problem has been fixed in Drupal 6. By default files are separate between translations, but using the i18n package you can choose to "synchronize" a file field (or any field) across translations.

This problem will remain in the Drupal 5 version because no developers are working on Drupal 5 any more. Patches would still be accepted that fix the problem.

quicksketch’s picture

Status: Active » Closed (won't fix)

Unless a patch can be provided in the next few months, this will remain unfixed indefinitely. Once Drupal 7 is out, FileField for Drupal 5 will drop all support.