Studio modifications to fields overwrite previous changes

šŸ‘Øā€šŸ’» Development Help
1

We found that, when a core field (for example: ā€œnameā€) from a module (for example: ā€œAccountsā€) is modified from studio (for example: Adding a Help text), the second time that you modify that field (for example: Adding a Default value) the first modification will be overwritten. Meaning that in this example, the Help text modification wonā€™t appear after the second change is applied. The result of the example will be the default properties values of the ā€œnameā€ field, plus the added Default value.

We tried:
1- change the permission and the ownerships of the whole SuiteCRM folder, like this:
chmod -R 775 .
chown -R www-data:www-data .

2- Manually removing the cache folder

3- Enabling developer mode

4- Tested in SuiteCRM 7.11.15 and 7.11.18

5- Tested in a local docker server and remote administered server

6- Changing the config.php dir/file mode properties:
ā€˜dir_modeā€™ => 1533,
ā€˜file_modeā€™ => 436, (( and 509

PHP 7.3 in all cases.

The custom fields work fine.

What are we missing? Is this a global Issue?

Thanks

2

We managed to test it in a totally different sever with an installacion of SuiteCRM 7.11.18, with the same problem.

We consider this as a major issue, surprised we didnā€™t realize it before. Is anyone currently working on this?

3

Hey @sinergiacrm,

Raising this internally, get you an update soon as we can :+1:

4

Do we know for a fact that this used to work before the latest releases? Iā€™m wondering if this isnā€™t a much older limitation of Studioā€¦

I say this because we havenā€™t been touching Studio code, itā€™s unlikely something that broke recently (though always possible).

5

Weā€™ve seen eerily similar issues in the past however this one seems unique to the folks Iā€™ve shown. Either way, should definitely be looked at - Iā€™ve raised a GitHub issue here, please feel free to add any extra info we should know - https://github.com/salesagility/SuiteCRM/issues/8969