Suitecrm: Cannot add accented characters to Name field via inline edit function

[blloyd78]

Issue

Cannot save accented characters (é, ł, ç etc) when using inline edit on the "Name" field for Contact/Lead records

Expected Behavior

Should be able to save non-Roman characters in the Name field when using the inline edit function - as is possible with all other text fields.

Note: This bug does not seem to affect any of the other fields when using inline editing

Actual Behavior

Any non-Roman characters are removed when the field contents are saved.

Possible Fix

No fix known.
Workaround: Toggle standard edit function. Any accented characters can then be entered and saved as normal.

Steps to Reproduce

1. Double-click the Name field on a Contact/Lead record
2. Enter an accented character (é, ł, ç, ü etc)
3. Click tick to save / press Enter

All text will be saved _except_ but the accented character will be removed completely.

Context

Discovered when trying to create a new Lead record for a contact with the surname Gracés.

Your Environment

• SuiteCRM Version used: 7.8.24
• Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Safari 12.0.2
• Environment name and version (e.g. MySQL, PHP 7): MySQL 5.7.13 / PHP 7
• Operating System and version (e.g Ubuntu 16.04): Ubuntu 16.04.2

[Mausino]

@blloyd78 I can confirm your issue aslo in 7.10.11. I tested by same characters as you é, ł, ç, ü on listview + editview of leads + Contacts

[Dillon-Brown]

From what I can see this would be unrelated to the accented characters. Inline editing Name field in Contacts/Leads doesn't work regardless of characters used. The workaround would be to edit on the edit-view.

[blloyd78]

Can confirm that this issue affects any inline edits - not just accented characters. Do you want me to update the original report @Dillon-Brown?

[ftoledo]

Maybe this issue are related #6786

[jan-waterdrop]

Few days ago I started to have this issue. Running on xampp (7.2.15) on windows server 2016. I have 2 instances there (7.11.12 and 7.11.13) - both of them are unable to do ANY inline edit in any module. Whenever I try to inline edit I recieve alert:

There was an error loading the field. Your session may have timed out. Please log in again to fix this

Yet this seems to be a generic error thrown anytime there is an inline edit error... Weird thing is - there was no change in those instances - its started happening out of the blue.

[jan-waterdrop]

Few days ago I started to have this issue. Running on xampp (7.2.15) on windows server 2016. I have 2 instances there (7.11.12 and 7.11.13) - both of them are unable to do ANY inline edit in any module. Whenever I try to inline edit I recieve alert:

There was an error loading the field. Your session may have timed out. Please log in again to fix this

Yet this seems to be a generic error thrown anytime there is an inline edit error... Weird thing is - there was no change in those instances - its started happening out of the blue.

Ehhhh scratch that it looks like an extension is causing this... Will post here when I know more.

[jan-waterdrop]

Few days ago I started to have this issue. Running on xampp (7.2.15) on windows server 2016. I have 2 instances there (7.11.12 and 7.11.13) - both of them are unable to do ANY inline edit in any module. Whenever I try to inline edit I recieve alert:
There was an error loading the field. Your session may have timed out. Please log in again to fix this
Yet this seems to be a generic error thrown anytime there is an inline edit error... Weird thing is - there was no change in those instances - its started happening out of the blue.

Ehhhh scratch that it looks like an extension is causing this... Will post here when I know more.

It was an extension. It all works great now! ;-)

[chris001]

Which extension? Why did it mess up the inline editing?

[pgorod]

Regarding the original issue, I think this is by design - the only thing that could (should) be improved is to not allow _starting_ the inline edit at all, since it won't work.

But the Name field is a concatenation of two other fields, First name and Last Name, I don't think there's any straight-forward way to determine how editing the concatenated field should be split into the two fields...

[tsmgeek]

@pgorod maybe a new SugarField is required that can handle this type of concat, saving to hidden fields for FirstLast names, or use some invisible control character.

[pgorod]

@tsmgeek maybe something could be added to the Inline edit code to be able to handle those cases.

And maybe the Inline Edit code should be integrated with the SugarFields architecture, so you could extend the available ways to edit fields.

But that's quite some work. And in particular this "Name = FirstName + LastName" field has code for it scattered all over the app, it's going to be painful. It's not well abstracted in the code base. :-(