This is a first attempt to make the nodeorder module support i18n.
Basically it is synchronizing the 'weight_in_tid' values between translations of the same node for each term, so now the node listings are in the same order in every language.
This approach is useful only if you have i18n, i18nsync and i18ntaxonomy modules enabled, your vocabulary is set to 'Localize terms' and you are synchronizing 'taxonomy' in i18nsync settings.

Currently there are only 2 drawbacks I know of:

  1. If your content is a mix of nodes with language and 'language neutral', the functionality of Move up and Move down is not always working correctly.
  2. The synchronization of weights between translations during editing of a node witch any change in terms, is working correctly only if you are editing the source translation of a node.
CommentFileSizeAuthor
norder_i18nsync_weight.admin_.patch394 byteslop
norder_i18nsync_weight.patch5.31 KBlop

Comments

pvanderspek’s picture

pvanderspek commented
Status: Needs review » Needs work

I'm not familiar with the i18n modules, but the two issues you point out really need to be solved before this patch can be applied. Have you been able to solve them already?

JGO’s picture

JGO commented

Would be great if it was solved.
I'm also suffering from nodeorder problems when using i18n

Btw:

1) is not so bad, and a lot of other drupal stuff is acting somewhat strange when listing own language and language neutral.

rolfmeijer’s picture

rolfmeijer commented

subscribing

Yuri’s picture

Yuri commented

Apparently installing and applying the module nodorder to a taxonomy, breaks the language translation connection between the translated terms.

This problem appears when clicking on the titles of the taxonomy term listing (../admin/content/taxonomy/[number]), they show: "There are currently no posts in this category". Because the translated term just adds the language prefix to the path but does not switch to the translated node.
The language switcher also doesn't work with nodeorder, for the same reason.

JGO’s picture

JGO commented

I hope somebody finally can start implementing this feature, waiting for a long time for this :(

j0rd’s picture

j0rd commented

Same problem with nodeorder on D6. Ideally it would make sense for nodeorder to work across languages. If you want to use a i18n_sync option for this, it works for me as well. This needs to get reviewed & committed. I have 9 languages and tonnes of nodes which need to be ordered. Doing it 9x times, is a hefty task currently.

dieuwe’s picture

dieuwe
Location Auckland, NZ
commented
Issue summary: View changes
Status: Needs work » Closed (outdated)

Closing as the Drupal 6 branch of this module (and Drupal 6 in general) has been discontinued.