Closed (fixed)
Project:
Commerce Kickstart
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
18 Nov 2011 at 20:51 UTC
Updated:
2 Jan 2012 at 17:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
joshmillerAttached is the proposed fix. It's possible we could also bring in all of the languages and pick the "first" enabled language, but I thought that might be overkill.
Thoughts?
Comment #2
rszrama commentedAhh, curious. Do you know if this is how Drupal handles nodes created through the interface as well?
In fact, I see that a product display created through the UI will show up as "Language neutral." Does your patch have the same effect?
Comment #3
rszrama commentedHmm, I tried the patch, but it just resulted in my nodes not having proper field data (and still showing as undefined language).
Comment #4
joshmillerGood point. @raystuart here at the Commerce Guys conference helped me
drush make --working-copyso that I could test my code snippets. Turns out that there isn't a sensible default for nodes #1336824: set node language to LANGUAGE_NONE in node_save()Attached is the real fix this time. Fully tested, solved the problem. The generated nodes have the correct language neutral database entry that every other Drupal node has by default.
Comment #5
rszrama commentedSweet, works as advertised. I still apparently don't know how to create a multilingual Drupal site, but at least turning on Locale + Content Translation showed me that our default nodes are Language neutral. I suppose I actually need a separate module to translate content?