Currently it doesn't seem to be possible to get translatable strings back into the database from exported OL configuration. It would be nice to have this done automatically (as in the 6.x version), although even a manual operation would be sufficient.
As a workaround you can currently open and resave all Controls configuration.

CommentFileSizeAuthor
#1 2535130-Allow-refreshing-translatable-string-1.patch5.26 KBparanojik
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

paranojik’s picture

paranojik CreditAttribution: paranojik at Cando commented
FileSize
2535130-Allow-refreshing-translatable-string-1.patch5.26 KB

The current patch implements hook_i18n_string_refresh() and introduces the method Object::i18nStringsRefresh().

Pol’s picture

Pol
the/that
Location Brussels
CreditAttribution: Pol as a volunteer commented
Assigned: Unassigned » das-peter

Hello,

Thanks for the patch, I will ask for help to review it, I'm not very aware about what is going on with translations.

I'll be back soon.

  • das-peter committed 8b592c2 on 7.x-3.x authored by paranojik 
    Issue #2535130 by paranojik: Allow refreshing translatable string
Pol’s picture

Pol
the/that
Location Brussels
CreditAttribution: Pol as a volunteer commented
Status: Needs review » Fixed

Thanks ! Wonderful team !

das-peter’s picture

das-peter CreditAttribution: das-peter commented

@paranojik Awesome, thanks! Looks pretty :) Pushed

Pol’s picture

Pol
the/that
Location Brussels
CreditAttribution: Pol as a volunteer commented

I just made a small change of a variable, from $map to $exportable. Makes more sense to me and the people who will read it.

  • Pol committed 687a294 on 7.x-3.x authored by paranojik 
    Issue #2535130 by paranojik: Allow refreshing translatable string

Status: Fixed » Closed (fixed)

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