Make node module inject language summary in language table

Assigning to myself. I'll work on this tomorrow at the code sprint.

Here's a patch and a screenshot of the result.

Note that the node count only includes nodes of types that can have a language.

Injecting node translation data should probably be done in a separate issue.

Updated patch:

- "Item" replaced with "post"
- "language" parameter added to the link to the content overview page. Making that form accept $_GET parameters opens a whole bunch of issues due to it's twisted use of session variables though, so this should be done in a separate issue.

Didn't mean to include the part regarding node.admin.inc. Thanks to attiks for pointing this out.

Having a look at the test failures. Adding an additional check if no content types are translatable.

Thanks Artusamak. Here's an updated patch that only inserts the additional column if at least one content type can be translated.

Working great for me!

On it!

Here is a test to check that the language overview table is displaying the posts count per language when available.

Looks good. Only a few minors.

+++ b/core/modules/language/lib/Drupal/language/Tests/LanguageNodeStatsTest.phpundefined
@@ -0,0 +1,76 @@
+    // Setup users.

Its only one user.

+++ b/core/modules/node/node.moduleundefined
@@ -3949,3 +3949,49 @@ function node_language_delete($language) {
+/**
+ * Implements hook_form_FORM_ID_alter() for language_admin_overview_form().
+ */

We dont do 'for ...'. Use @see language_admin_overview_form().

+++ b/core/modules/node/node.moduleundefined
@@ -3949,3 +3949,49 @@ function node_language_delete($language) {
+  $info = entity_get_info('node');
+  foreach ($info['bundles'] as $machine_name => $bundle) {

node_type_get_types() is easier.

Removed 'Needs tests' tag.

Added sprint.

I've applyed the patch from #16 but I cannot find the test "Node language statistics" at admin/config/development/testing.

Listed issues fixed.
@jepSter the group for the test was wrong, it's normally fixed.

After I get a fresh copy of drupal 8 files, patch drupal 8 with your file from #21 and choose your test "Node language statistics" at admin/config/development/testing/ and start the testing, I get 32 passes, 7 fails, 0 exceptions, and 10 debug messages.

the following is failing:

• For example the following fails:
• Failed to set field node_type_language to 1
• Found the requested form fields at admin/structure/types/manage/page
• Total of posts per language is displayed.
• Failed to set field langcode to en
• Found the requested form fields at node/add/page
• Basic page created.
• English displays one post.

Here is an update of the test and the form alter.
Since the content type language changed, i'm listing the posts for every language (even special ones).
I removed the link if there is no post and removed the t() calls from the messages to be compliant with http://drupal.org/simpletest-tutorial-drupal7#t

Needs reroll

Rerolling the patch #26

rerolled the patch.

The langcode field have moved from the node table to the node_revision table.

Also moved the test file to PSR-4 location, and fixed the test to pass.

Unassigning.

The test is inadequate in my opinion. It basically just tests that the text changes when adding a new node, not that the code actually counts the number of nodes in each language.

Extending the test by adding another language and checking that each language count is correct should do it.

Patch no longer applies.

Rerolled Patch.

Applying Patch.

Patch rerolled for 8.2.x

Please find the updated patch #46 with code indentation and with appropriate comments.

Thanks,

Updated patch against 8.3.x

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!