Ticket #531 (reopened defect)

Opened 21 months ago

Last modified 6 months ago

MessageSource_MySQL does not save untranslated strings

Reported by: rabol Owned by: wei
Priority: urgent Milestone: 3.2
Component: Prado Framework v3 Version: 3.2
Severity: major Keywords:
Cc:

Description

MessageSource?_MySQL does not save 'new' strings unless you have a valid record in the catalouge table for the specific language.

In other words, you need to make sure that you have a messages.XX (where XX is the culture) for each culture that you would like to use - before, the messages.XX record is not automatticly created as with XLIFF

Change History

Changed 21 months ago by xue

  • milestone set to 3.0.7

Changed 20 months ago by xue

  • owner changed from xue to wei

Changed 20 months ago by wei

  • status changed from new to closed
  • resolution set to wontfix

Provide your own custom db message source to handle this. The DB versions of message source are trickier to support.

Changed 20 months ago by rabol

  • status changed from closed to reopened
  • resolution wontfix deleted

hmm... It is not possible to add a custom messages

Changed 19 months ago by wei

  • version changed from 3.0 to 3.1
  • milestone changed from 3.0.7 to 3.1 Beta

MessageSource?_Db will be added later for 3.1 branch such that MessageSource?_MySQL and MessageSource?_Sqlite will be deprecated.

Changed 19 months ago by wei

  • milestone changed from 3.1 Beta to 3.1 RC

Changed 17 months ago by wei

  • milestone changed from 3.1 RC to 3.1.0

Changed 16 months ago by xue

  • milestone changed from 3.1.0 to 3.1.1

Changed 12 months ago by xue

  • milestone changed from 3.1.1 to 3.1.2

Changed 6 months ago by xue

  • version changed from 3.1 to 3.2
  • milestone changed from 3.1.2 to 3.2
Note: See TracTickets for help on using tickets.