As in the subject, this patch allows to see the node language on table results.

CommentFileSizeAuthor
#4 nodequeue-langresults-1649206-1.patch3.49 KBpaolomainardi
#3 nodequeue-langresults-1649206-1.patch2.72 KBpaolomainardi
#1 nodequeue-langresults-1649206-1.patch4.46 KBpaolomainardi

Comments

paolomainardi’s picture

paolomainardi commented
StatusFileSize
new nodequeue-langresults-1649206-1.patch4.46 KB

Attached patch.

Status: Needs review » Needs work

The last submitted patch, nodequeue-langresults-1649206-1.patch, failed testing.

paolomainardi’s picture

paolomainardi commented
Status: Needs work » Needs review
StatusFileSize
new nodequeue-langresults-1649206-2.patch2.72 KB

The corrected one.

paolomainardi’s picture

paolomainardi commented
StatusFileSize
new nodequeue-langresults-1649206-4.patch3.49 KB

I've just noticed a problem, it was missing the language header column, please find attached the corrected one.

paolomainardi’s picture

paolomainardi commented

Up

nils.destoop’s picture

nils.destoop commented

up

nils.destoop’s picture

nils.destoop commented
Status: Needs review » Reviewed & tested by the community
fizk’s picture

fizk commented
Issue summary: View changes
Status: Reviewed & tested by the community » Closed (won't fix)

There are many node attributes we could potentially include in the table. How do we decide which ones to include and which not to include? I'm guessing by the lack of activity here over the past 3 years, most people don't need this feature. It's a good resource for anyone wanting to add this feature, though.