Hello.

I'm using:
Drupal 7.12
i18n 7.x-1.5
Views 7.x-3.3
Views Translation 7.x-3.x-dev

This morning I updated (on my testing site):
i18n from 7.x-1.4 to 7.x-1.5,
Variable from 7.x-1.1 to 7.x-1.2,
and Calendar from 7.x-3.1 to 7.x-3.2.

Shortly after that I tried to add a translation to a View (by opening the View, clicking "Translate View" and clicking "Tranlate" from the list), but all the fields were locked and I couldn't edit anything, including strings I had already translated. Under each field is the message (see attached image):

This is a user-defined string. You are not allowed to translate these strings.

This is the case on every View I checked. I checked my production site, which hasn't been updated to the latest modules yet, and I was able to edit every View I checked. So I guess something went wrong after upgrading i18n?

Any ideas?

Thank you!

CommentFileSizeAuthor
Views-error-after-update.png88.6 KBSDC
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

SDC’s picture

SDC CreditAttribution: SDC commented

To add to my previous post, I reverted to i18n 1.4 and I can now edit my Views translations again.

Gib...’s picture

Gib... CreditAttribution: Gib... commented

Hi,

Same problem with title block. For instance, I want to translate the title of the book navigation block.
I make this block translatable, select both languages I use. Then save and translate. I see "not translated" in one language. I click "add a translation" and I get the message " This is a user-defined string. You are not allowed to translate these string." with a dimmed field containing the original string.

I get these errors when I clic Save even if I can't change anything.
Notice : Undefined index: strings dans i18n_string_translate_page_form_submit() (ligne 213 dans /home/.../public_html/sites/all/modules/i18n/i18n_string/i18n_string.pages.inc).
Warning : Invalid argument supplied for foreach() dans i18n_string_translate_page_form_submit() (ligne 213 dans /home/.../public_html/sites/all/modules/i18n/i18n_string/i18n_string.pages.inc).

Drupal core 7.12
Internationalization 7.x-1.5
Internationalization Views 7.x-3.x-dev (2012-Jan-08)
Localization client 7.x-1.1
Localization update 7.x-1.0-beta3
Variable 7.x-1.2

guillaumev’s picture

guillaumev CreditAttribution: guillaumev commented

Hi,

Same issue here...

guillaumev’s picture

guillaumev CreditAttribution: guillaumev commented
Status: Active » Fixed

To fix it, go to People > Permissions and give the administrator role (or any role you want) the permission to Translate user-defined strings and/or Translate admin strings...

I believe this issue can be closed as this is not a bug...

Status: Fixed » Closed (fixed)

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