Expected behavior:
Filter on 'outdated translation' shows me all the nodes that are marked as outdated
Currently it shows... nothing. Maybe my expectations are wrong and this is working as designed though :)
I've added a patch that changes a WHERE clause to a group by (couldn't figure out why there was a WHERE there, maybe this is the functionality I'm not grasping).
Also added sorting and paging in the process.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | translation_overview-filter_and_sorting-1424504.patch | 802 bytes | thijsvdanker |
| translation_overview-filter-and-sorting-fix.patch | 603 bytes | thijsvdanker |
Comments
Comment #1
miro_dietikerI cannot see anything about "sorting and paging" you've added.
Outdated functionality is known to be broken. That's bad, but no one found time to fix it till now.
Patch appreciated.
Comment #2
thijsvdanker commentedwoops, here's the patch with sorting and paging
Comment #3
thijsvdanker commentedComment #4
devad commentedI tried the patch...
where("(n.nid = n.tnid OR n.tnid = 0) ... ... works nice.
groupBy('n.tnid') do not work nice.
Grouping by n.tnid puts all untranslated nodes (n.tnid = 0) into one group which displays the first node with n.tnid = 0 only and all others are removed from the list.
Other parts of the patch... sorting and paging... work nice for me. Thnx thijsvdanker!
Comment #5
stefan.r commentedSetting to NW based on #4