While working on distribution which uses Profiler, a co-worker (@bdone) noticed that a language column appeared at the path "/admin/content" after install. The column contained "Undefined language ()" for the default node/1 generated by Profiler using the documented syntax for node creation in the .info file. @bdone also noticed that there were translation related options when editing nodes.

While I don't think this is a major issue, I would prefer to not have any language related features/labels displaying when using a site which doesn't use the local and content translation modules.

CommentFileSizeAuthor
#1 issue-1820010-lang-col-fix.patch462 bytesshrop
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

shrop’s picture

shrop CreditAttribution: shrop commented
FileSize
issue-1820010-lang-col-fix.patch462 bytes

Update:

  • Confirmed that the local and the content translation modules were not turned on during install
  • Noticed that the "language" field in the node table was empty
  • The default for the field should be "und" if it is undefined

The fix is to add the following line to a node creation block in the .info file for the profile. I tested this with our internal distro and it works great.

nodes[hello][language] = und

I have also attached a patch to the README.txt file to help others who may encounter a similar issue.

shrop’s picture

shrop CreditAttribution: shrop commented
Status: Active » Needs review

Changing status to "needs review"

shrop’s picture

shrop CreditAttribution: shrop commented
Title: Language column appearing in » Language options and labels showing up for initial Profiler created nodes

Changed title

shrop’s picture

shrop CreditAttribution: shrop commented
Issue summary: View changes

Linked to bdone's profile