Only display language switch block if translation available

The patch does not apply against latest dev.

Rerolling patch against latest dev

Patch needs to be updated. At least direct using of \Drupal::routeMatch() should be replaced by DI of necessary container.

Changed \Drupal::routeMatch() with Dependency Injection.

@Prashant.c you did not run and check your code, right? ;)
At least the number of arguments received in __constract and arguments passed in create does not match.

@kala4ek

Sorry i could not test it.

Submitting again with changes please review is it good now ?

Any updates on this , any reviews?

There is an issue with the patches. Its more of an issue of ContentEntityBase::getTranslationStatus
Im not sure if this an actual bug of getTranslationStatus or just a misconception from my side.
The fact of the matter is that getTranslationStatus returns 1 if a translation exists but is unpublished.
In this case, you get to see that language in your lang switcher although the actual translation cannot be accessed.

The attached patch tries to correct this behaviour.

Fixed patch is attached

hopefully this time i will get it right

Why target just nodes? What about other translatable entity types (e.g., Group entities from Group module)?

Since i needed this and Dropdown Language module has this built in already, i just used relevant piece of code. So far its working.

Im noob when it gets to posting patches to issues and all that stuff with git (https://www.drupal.org/node/707484 - my head will explode, its to complicated). I just created patch, will attach it to this issue, hope i will help someone and hope that i wont break something badly...

The last patch seems to work well at limiting the list of languages. However, It doesn't hide the block if only one language is present.

@johnpicozzi here is a new patch that adds a configuration option to hide if only one language is available.

The previous patch doesn't apply to 2.x-dev anymore plus it had a bug that didn't correctly set the cache context. Here's a new patch that applies to dev and fixes the cache context issue.

Let's try that patch again.

Here's yet another iteration on this patch. Because the cache context was only being applied to the route, adding or changing the translations for a node didn't clear the block cache for the node so the block wouldn't show up without a full cache clear. Additionally, the code from earlier patches only considered the first entity in the current Drupal route. I rewrote that section to consider all entities.

Oh, and I added this missing schema so hopefully the tests will fire.

Tests still assumed the default was to show all languages. Hopefully this update fixes them.

Cache wasn't always clearing when adding translations, probably due to not properly using $entity->getCacheTags()

I'm still getting reports that the cache is not correctly clearing.

Here's another pass at this, hopefully with caching fixed.

In configurations with visibility management by roles, version 4.0 that includes this patch does not work correctly.

Unfortunately it hides the languages of the translations in the dropdown.

This issue is not repeated in version 2.0-beta4.