I believe that this issue here http://drupal.org/node/1265152 is actually being caused by Kickstart and not Drupal Commerce.

CommentFileSizeAuthor
#2 translate_image-1267386-2.patch491 bytesFranciscoLuz
#1 translate_image-1267386-1.patch1.53 KBFranciscoLuz

Comments

FranciscoLuz’s picture

FranciscoLuz commented
Status: Active » Needs review
StatusFileSize
new translate_image-1267386-1.patch1.53 KB

UPDATE: Please apply the patch in #2 instead of this one.

So, in my case the culprit was a couple of typos on the t() function name in commerce_kickstart.profile and commerce_kickstart.install files. Once they were corrected the errors went away.

In field.views.inc the if check on $label != $label_name was failing for image field because $label was coming untranslated "Image" and $label_name was coming translated so the if statement was being executed when it shouldn't.

Please check out the patch attached.

FranciscoLuz’s picture

FranciscoLuz commented
StatusFileSize
new translate_image-1267386-2.patch491 bytes

Ok,

Let me correct a couple of things:

  1. I was wrong, there were no typos, the calls to st() function are meant to be there http://api.drupal.org/api/drupal/includes--install.inc/function/st/7.
  2. The actual issue was being caused by a missing st() call in commerce_kickstart.install

So, please ignore the patch in #1 and apply this one instead.

UPDATE: This patch will only fix the issue if applied b4 a fresh install is made. The only way I could think of fixing it on an already corrupted installation is to delete the field_image field at admin/structure/types/manage/article/fields

chi’s picture

chi commented
Title: Notice: Undefined index: commerce_product in field_views_field_default_views_data() for languages other then english » Label of field_image instance created during install cannot be localized.
Version: 7.x-1.0-rc1 » 7.x-1.x-dev
Status: Needs review » Reviewed & tested by the community

@ FranciscoLuz
Read this comment. It is not commerce_kickstart issue.

But I think that label of the field must be localized and the patch should be committed.
There is related issue with standard profile: #1048006: Name of vocabulary (Tags) created during install cannot be localized

rszrama’s picture

rszrama commented
Status: Reviewed & tested by the community » Fixed

Committed, thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.