Problem/Motivation
When editing a node, that node becomes first in the list on multilingual sites.
Steps to reproduce
Create a website with 2 or more languages. Create some translated terms. Create some translated nodes and assign each node to one of the translated terms.
Reorder the nodes.
Edit anything but the first node. Save that node. That node is now the first in the order.
Proposed resolution
Quickfix:
make sure the array used in the update hook has unique values (it contains the same term id multiple time, once for each language).
Fix in the long run:
make sure order is saved taking langcode into account. All the queries in NodeOrderManager should add langcode conditions in them since taxonomy-index table contains a langcode column.
Remaining tasks
None
User interface changes
None
API changes
None
Data model changes
None
Comment | File | Size | Author |
---|---|---|---|
#2 | nodeorder-multilingual-support-3178329-1.patch | 535 bytes | kriboogh |
Comments
Comment #2
kriboogh CreditAttribution: kriboogh at Calibrate commentedHere's a patch for the quick fix.