Posted by Jody Lynn on October 10, 2008 at 7:35pm
Jump to:
| Project: | Internationalization Views |
| Version: | 6.x-3.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I added a views filter so that one can create a listing of nodes with no translation.
| Attachment | Size |
|---|---|
| i18nviews.patch | 789 bytes |
Comments
#1
patch working with 2.5.. great
#2
New features are for 6.x only.
#3
I think moving to won't fix is a mistake. This patch is very old and never was ported. Maybe someone (I'll do it if I have some time) could make a patch for 6.x. I am not using this module in any of my sites anymore but I think this could be useful.
#4
How can this NOT be a feature??
#5
Ok, reopen if the patch is ported.
Moved to new project. See #788290: Fix views compatibility issues (2.x, 3.x), spin off i18nviews module?
#6
Uff .. The patch provided is really from 5.x times.
Setting back to active as an initial ToDo.
Actually you can do pretty much with current filters.
For example
- Node translation: Language <> No language
MEANS: node must be a specific (translateable) language
- Node translation: Translation set node ID = 0
MEANS: there's no translation added
However what we clearly can't do is:
List nodes that lack translation for specific language X.
This would need a custom handler.
Patches welcome!
#7
Edit: Sorry...this comment can be deleted as it was already pointed out in the previous comment...not trying to steal thunder.
You don't need a patch for this...just add to the Filter of the View the following condition (in addition to any other conditions you have set for the view): Node translation: Translation set node ID = 0
All untranslated nodes have the value of zero (0) for the 'Translation set node ID' field in the "Node translation" group.
Hope this helps somebody.
#8
Thanks #7.
Does that mean this issue is solved? (perhaps status should change)
cheers,
Dago