Hi,

This is not working on a multilanguage site where is chosen for " Localize terms. Terms are common for all languages, but their name and description may be localized."
The problem is that the tagorder is only set for the current node. When using a translated node, the setting gets set to the translation and removed from the original.

----------------------------
JGO | http://www.e2s.be
----------------------------

Comments

arski’s picture

arski commented

subscribing.

Would be a great addition to have!

Thanks,
Martin

porg’s picture

porg commented
Version: 6.x-1.3 » 6.x-1.5

@JGO: I can confirm this bug. Still happening in 6.x-1.5 with Drupal 6.19.

In order that this bug is completely understood, so that it can get solved, I provide an example scenario/test.

In my node tests, I wrote the originally given tag order into the body text, so that I can later compare it with the actual tag order, and I prefixed it with the English/German string "Vokabular"/"Vocabulary" so that it is also obvious in which localization I am.

0) "Haustier" and "Mitleid" are already existing terms, already localized as "pet" and "pity".

1) Creating original: /de/ordnung-2 = /node/20
Body text: Vokabular: testbb1 testcc2 testaa3 Haustier testzz5 Mitleid testxx7
Entered tag order:    testbb1 testcc2 testaa3 Haustier testzz5 Mitleid testxx7

REMARK: The terms in the style of "testAAN" are now freshly created. The letter suffixes in the style of "AA" provoke the alphabetical order, whereas the numerical "N" indicates the order as entered, to later check if "Tag order" worked correctly. In the numerical ommision "4" I put "Haustier", into "6" "Mitleid".

2) Viewing: /de/ordnung-2
Body text: Vokabular: testbb1 testcc2 testaa3 Haustier testzz5 Mitleid testxx7
Actual tag order:     testbb1 testcc2 testaa3 Haustier testzz5 Mitleid testxx7

REMARK: Ok! As expected!

3) Viewing: /en/node/20
Body text: Vokabular: testbb1 testcc2 testaa3 Haustier testzz5 Mitleid testxx7
Actual tag order:     testbb1 testcc2 testaa3 pet      testzz5 pity    testxx7

REMARK: Ok! As expected!

4) Localising the German terms to English:
DE: testbb1    testcc2    testaa3    testzz5    testxx7
EN: testbb1-en testcc2-en testaa3-en testzz5-en testxx7-en

5) Creating node localisation: en/order-2 = en/node/24

6) Viewing: /en/order-2
Body text: Vocabulary: testbb1    testcc2    testaa3    Haustier testzz5    Mitleid testxx7
Actual tag order:      testbb1-en testcc2-en testaa3-en pet      testzz5-en pity    testxx7-en

REMARK: Ok. As expected.

7) Now again viewing: /de/ordnung-2
Body text: Vokabular: testbb1 testcc2 testaa3 Haustier testzz5 Mitleid testxx7
Actual tag order:     testzz5 testxx7 Mitleid testcc2  testaa3 testbb1 Haustier

REMARK: Not ok! Complete chaos now! The localization has destroyed the original order. I cannot even conclude the systematics of how it was scrambled.

8) Viewing German node in English display language: /en/node/20
Body text: Vokabular: testbb1    testcc2    testaa3 Haustier   testzz5    Mitleid    testxx7
Actual tag order:     testzz5-en testxx7-en pity    testcc2-en testaa3-en testbb1-en pet

REMARK: Same chaos!

9) Viewing English node in German display language: /de/node/24
Body text: Vocabulary: testbb1 testcc2 testaa3 Haustier testzz5 Mitleid testxx7
Actual tag order:      testbb1 testcc2 testaa3 Haustier testzz5 Mitleid testxx7

REMARK: Interesting! Here it is re-scrambled into its original order!
porg’s picture

porg commented

I have now researched what happens in the database.
Hopefully this can help for debugging.

0) Fresh installation with 0 nodes yet using Tagorder.
Now I enable Tagorder for a certain content type.

1) Creating the node in English (nid 93).
The complete database table "tagorder" now looks like this:

nid	vid	vocabid	tid	weight
93	93	18	249	1
93	93	18	253	5
93	93	18	252	4
93	93	18	251	3
93	93	18	250	2

2) Translating the node to German (nid 94).
Neither changing the used terms nor their order.
The content type uses the international settings "Synchronize Taxonomy".
The complete database table "tagorder" now looks like this:

nid	vid	vocabid	tid	weight
94	94	18	249	1
94	94	18	250	2
94	94	18	251	3
94	94	18	252	4
94	94	18	253	5

Observations:
A) All nid 93 terms got completely lost from the table! Thus Drupal will use the default alphabetical tag sorting for the English node.
B) The weights for nid 94 got reordered (compared to nid 94), the order as entered by the user was lost, the tagorder makes for the German node makes no sense either!

porg’s picture

porg commented

One year later. Plans for a fix meanwhile?
Or can this meanwhile be achieved by core functionality or other modules?