Renaming Relationship Label

OK, I understand… but I’m at a crossroads.

FYI… I’m on a bitnami stack of SuiteCRM. I have no idea what the ownership of the files/folders were before I changed them.

I did as you suggested and changed all the files/folders to be owned by the apache user/group (daemon:daemon)… and I set the file permissions as you suggested.

Problem is, now the files are not writeable through FTP when I’m logged in as ‘bitnami’ user (which is the only user that is allowed SFTP access).

I’m not a linux/ubuntu expert by any means… I’m pretty handy with PHP, however… so forgive my noviceness.

Thanks,
sieberta

OK, so I’m now in a workable place, but I’m not sure if security is a concern… I added the bitnami user to the daemon group as a secondary group… I then had to upgrade permissions to 775 so that bitnami can write to the files in addition to daemon being able to write the the files. Since daemon is the apache user, and has full control over files and folders, I don’t necessarily see why giving all group users that level of permission would be an issue. But again, I’m a novice, so I’m not sure.

sieberta

Here’s the problem with pictures…

I created a 1:Many relationship between Projects & Projects to allow for a parent-child relationship.

I then try to edit the name in Projects->Labels, but as soon as I click Save & Deploy it reverts to the old name “Projects”.

Quick Repair doens’t change anything, when viewing in detailview or editview it still just says “Projects”.

So then following the instructions here, I open the \suitecrm\custom\modules\Project\language\en_us.lang.php file, but it already has the desired value (see the last line in the code below)!

<?php
// created: 2014-10-30 14:18:37
$mod_strings = array (
  'LBL_AA_FILE' => 'AA File',
  'LBL_CITY' => 'City',
  'LBL_STATE' => 'State',
  'LBL_COUNTRY' => 'Country',
  'LBL_CATEGORY' => 'Category',
  'LBL_FACILITY_TYPE' => 'Facility Type',
  'LBL_DRAWINGS' => 'Avant Drawings',
  'LBL_ASSIGNED' => 'Assigned',
  'LBL_PROPOSAL_SENT' => 'Proposal Sent',
  'LBL_ACTUAL_PROJECT' => 'Project?',
  'LBL_PROPOSAL_RECEIVED' => 'Proposal Received',
  'LBL_DESIGN_DEVELOPMENT_SUBMITTAL' => 'Design Development Submittal',
  'LBL_SCHEMATIC_DRAWINGS_SUBMITTAL' => 'Schematic Drawings Submittal',
  'LBL_CONSTRUCTION_DOCUMENTS_SUB_1' => 'Construction Docs Submittal 1',
  'LBL_CONSTRUCTION_DOCUMENTS_SUB_2' => 'Construction Docs Submittal 2',
  'LBL_FULL_SUBMMITTAL' => '100% Submmittal',
  'LBL_BID_SUBMITTAL' => 'Bid Submittal',
  'LBL_EQUALIZATION' => 'Commissioning',
  'LBL_FIRST_USE' => 'First Use',
  'LBL_RECORD_DRAWINGS' => 'Record Drawings',
  'LBL_SCOPE' => 'Scope',
  'LBL_FEE' => 'Fee',
  'LBL_EXPENSES' => 'Expenses',
  'LBL_HOURS' => 'Hours',
  'LBL_USERS_PROJECT_1_FROM_USERS_TITLE' => 'Assigned By',
  'LBL_PANEL_ASSIGNMENT' => 'Schedule',
  'LBL_EDITVIEW_PANEL1' => 'Project Notes',
  'LBL_DESCRIPTION' => 'Description/Notes',
  'LBL_EDITVIEW_PANEL2' => 'Statistics',
  'LBL_DATE_START' => 'Start Date:',
  'LBL_DATE_END' => 'End Date:',
  'LBL_DETAILVIEW_PANEL3' => 'Other',
  'LBL_FEE_BILLED' => 'Billed',
  'LBL_FEE_PER_HOUR' => 'Per Hour',
  'LBL_STATUS' => 'Status',
  'LBL_EDITVIEW_PANEL3' => 'New Panel 3',
  'LBL_FEE_BALANCE' => 'Balance',
  'LBL_ASSIGNED_BY_USER_ID' => 'Assigned By (related User ID)',
  'LBL_ASSIGNED_BY' => 'Assigned By',
  'LBL_NAME' => 'Name:',
  'LBL_DELETED' => 'Deleted:',
  'LBL_CONTRACTOR_ACCOUNT_ID' => 'Contractor (related Account ID)',
  'LBL_CONTRACTOR' => 'Contractor',
  'LBL_FEE_INCLUDED' => 'Fee Included In Parent',
  'LBL_PROJECT_PROJECT_1_FROM_PROJECT_L_TITLE' => 'Parent Project',
);

OK.
I would try the following:

  1. delete the contents of the cache folder (not the folder itself) and then navigate to a page where the label appears to see if it is correct.

  2. Search through all of the SuiteCRM files for the label names you want to change so that you can locate all files in which these labels appear and then modify them by hand

Hotfix from Sugar fixed it. For some reason they don’t make them available, you have to request it and then you get a .zip which can be installed through module builder followed by a quick repair.

https://community.sugarcrm.com/sugarcrm/topics/custom_related_fields_labels_reset_to_default?utm_source=notification&utm_medium=email&utm_campaign=new_comment&utm_content=topic_link

It is important, supposedly, that you only use the attached hotfix with this version:

SuiteCRM Version 7.1.2
Sugar Version 6.5.17 (Build 1220)

1 Like

Good to hear you solved it!

Hey. If anyone’s interested, here’s the hotfix for Sugar Version 6.5.18 (Build 1110). Works with my local instance of Suite 7.1.4

Thanks to sieberta for putting me on the right track.

I know that this is an old thread, but I’ve just run into the same problem on SuiteCRM 7.3.1 (based on CE 6.5.20). Does anyone have the hotfix that works with this version?

I have the same problem. Version 7.2.

Is there any official patch or workaround to solve this issue?

Looking at the patch uploaded in other posts i can see the only difference between the patch and the SuiteCRM “LanguageManager.php” file is this line:

Function: “refreshLanguage”

Original Array:

$lang_paths = array(
‘modules/’.$module.’/language/’.$lang.’.lang.php’,
‘modules/’.$module.’/language/’.$lang.’.lang.override.php’,
‘custom/modules/’.$module.’/language/’.$lang.’.lang.php’,
‘custom/modules/’.$module.’/Ext/Language/’.$lang.’.lang.ext.php’,

			 );

It should be like this:

$lang_paths = array(
‘modules/’.$module.’/language/’.$lang.’.lang.php’,
‘modules/’.$module.’/language/’.$lang.’.lang.override.php’,
‘custom/modules/’.$module.’/Ext/Language/’.$lang.’.lang.ext.php’,
‘custom/modules/’.$module.’/language/’.$lang.’.lang.php’,

			 );

The order of the last two lines is reversed. Unfortunately this change is not upgrade safe.

This fixed the issue of the topic for me (Using the latest 7.9 verision of SuiteCRM)

5 Likes

Made this change, cleared the cache folder and it worked perfectly.

Thanks @positiveit for the fix.

I’ve got the latest version of suitCRM and its not fixed yet …
Version 7.10.9
Sugar Version 6.5.25 (version de construction 344)

If I understand correctly, on every update I will have to re-change the code in LanguageManager.php cause the update will override it ? …

Still looking for an update safe methode, I’ve got to do this little change on every update.

Wow… new version Suite 7.11.20 still has the problem!

I still use the fix proposed by @positiveit after every update of the CRM lol

Is there a PR proposing this fix?

What is a “PR” … and how does one go about creating one?

It is a Pull Request on GitHub, It’s the way developers use to contribute fixes like this one to the source code.

I don’t believe positiveit’s solution still works.
Tested on Version 7.11.20

The values for the labels are being pulled from here:
/var/www/html/SuiteCRM/custom/modules/{module}/language

Then get overwritten with values from here:
SuiteCRM/custom/Extension/modules/{module}/Ext/Language

The simple solution that worked for me was to delete all the files in:
SuiteCRM/custom/Extension/modules/{module}/Ext/Language

Note:
SuiteCRM\modules\ModuleBuilder\parsers\parser.label.php
contains the function addLabels that originally creates the files in
SuiteCRM/custom/Extension/modules/{module}/Ext/Language
(It has comments about fixing this issue (as bug #51))
The problem is even though this function is called each time the labels are edited, the section of code that is supposed to update the labels in the SuiteCRM/custom/Extension/modules/{module}/Ext/Language folder doesn’t run because $forRelationshipLabel is always false.

1 Like

Im on 7.11.22 and the fix is still working for me ?