[Vtigercrm-commits] [vtiger development] #4076: i18n issue with custom views

[vtiger development]

#4076: i18n issue with custom views
------------------------+---------------------------------------------------
  Reporter:  mickie     |       Owner:  developer
      Type:  defect     |      Status:  new      
  Priority:  critical   |   Milestone:  5.0.4    
 Component:  vtigercrm  |     Version:  5.0.3    
Resolution:             |    Keywords:           
------------------------+---------------------------------------------------
Comment (by mickie):

 As of now when we save the Invoice then the value saved in invoicestatus
 column in vtiger_invoice table is Approved. But when we show this in UI we
 will translate and show as Bestätigt

 we can do fix this in following ways

 1. when we save the invoicestatus in vtiger_invoice table we have to save
 the translated value as shown in the UI ie., save the value Bestätigt in
 invoicestatus column in vtiger_invoice table. If we do this, then
 whereever we used this status Approved in queries those will be affected.
 So we have to change all hardcoded strings in queries in a common way.
 This can be done by adding the line
 $pickListValue = getTranslatedString($pickListValue);
 in include/utils/EditViewUtils.php in line 156 inside the elseif($uitype
 == 15 || $uitype == 16 || $uitype == 111) condition in function
 getOutputHtml . Also add this line in 1134 in this same function for
 uitype 115

 2. When we add the condition in query we have to convert the translated
 string Bestätigt as Approved and then add this in query. But this is a
 little bit complicated one.

 The problem is, when we use the translated string in filter then the
 expected result is not coming.
 So we have to
 1. Use the translated string in all over the product including database
 ie., save the translated string in database.
 2. Use the translated string only to show in UI and handle with original
 stiring in all over the product.

 First option ie., use the translated string all over the product will be a
 better solution.

-- 
Ticket URL: <http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/4076#comment:1>
vtiger development <http://trac.vtiger.com/>
vtigerCRM