I added a views filter so that one can create a listing of nodes with no translation.

CommentFileSizeAuthor
i18nviews.patch789 bytesJody Lynn
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

lelizondo’s picture

Status: Needs review » Reviewed & tested by the community

patch working with 2.5.. great

Jose Reyero’s picture

Status: Reviewed & tested by the community » Closed (won't fix)

New features are for 6.x only.

lelizondo’s picture

Version: 5.x-2.4 » 6.x-1.x-dev
Status: Closed (won't fix) » Active

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.

dagomar’s picture

How can this NOT be a feature??

Jose Reyero’s picture

Project: Internationalization » Internationalization Views
Version: 6.x-1.x-dev » 6.x-3.x-dev
Status: Active » Postponed

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?

miro_dietiker’s picture

Status: Postponed » Active

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!

WWB’s picture

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.

dagomar’s picture

Thanks #7.

Does that mean this issue is solved? (perhaps status should change)

cheers,
Dago

ANDiTKO’s picture

@ #6

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

Thanks. That worked for me in Drupal 7

OneTwoTait’s picture

I think the terminology of Views was changed a bit. It's now:

Content translation: language
- Settings: "is not one of" "no language"

Content translation: Translation set node ID
- Settings: "is equal to" "0"