Impossible to enter phone number in (Czech) locale format in Organizational Unit settings

[Eva Cerninakova]

In Server admin --> Organizational Unit in tab Main library information (attached to particular organizational units) in Evergreen 2.6.2 Staff Client when entering the library phone number to the field "Main phone number" I always get the error message attached the field "The value entered is not valid" and the phone number is impossible to save. The behavior of the system is the same no matter whether en-US or cs-CZ locale interface is of Evergreen staff client is used.
I tried following formats of library phone number with no succes:

211222410
[phone]
00420211222410

211 222 410
[phone]
00420 211 222 410
00 420 211 222 410

211-222-410
[phone]
00420-211-222-410
00-420-211-222-410

(Note: The similar problem used to happen in Evergreen 2.2. in JSPAC when entering the patron hold notification phone number - now no problem occurs with hold notification nubmers, so I supposed it was solved).

[Kathy Lussier (klussier)]

I tested this in master and found something a little different.

I also see the message "the value entered is not valid" when entering the number of any of the formats you listed above. Therefore, I'm marking the bug confirmed because we should not be seeing that message. Ideally, it would be nice if we could set a regex for this field. I didn't see a current setting that does this.

However, even with that message, I was able to save the phone number in the record.

I did come across another problem, though, that was unrelated to the phone number format. If, after saving the record, I tried entering a new phone number and saving the record again, the system often choked up on me, until I eventually received an error message that says:

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: oils://remote/js/dojo/dojo/openils_dojo.js:16

This message came up even when I was entering a phone number in a standard U.S. format, which is why I think the problem is unrelated to the phone number format. If I existed out of the interface, retrieved it again, and then entered the phone number in any of the above formats, I had no trouble saving the record.

Do you think this may have been what happened when you were trying to save the number?

[Eva Cerninakova (ece)]

I tried to test it ones more.
I discovered, that I was partially right. I really was not able to save the settings with phone number in "invalid" format. It happened first time I entered the phone number consisting of nine digits (i.e. 2112212410 - I was still not able to save it during new testing), but phone numbers in some of the following "longer"formats I might have not tried to save and gave up immediately after the error message "not valid" appeared.
I can confirm the same behavior in all other cases i.e., after saving the record (with phone numbers [phone] and 00420211222 for another OU) , if I tried entering a new phone number and saving the record again, the system stopped working. I was probably not patient enough and after some time I tried open the same setting interface ones more again (in the same tab) and I got the error message:

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.
Script: chrome://global/content/bindings/general.xml:0

[Eva Cerninakova (ece)]

I tried to replicate the issue in EG 21.12 (version 0master.53150bb):
No script error message appeared even if trying to enter a new number. However the message "the value netered is not valid" still persists.

[Eva Cerninakova (ece)]

This problem has been confirmed in our libraries recently (confirmed also in 3.3.0). It is possible to save the phone number in any format, however, the field is marked as invalid, see the attachment

[Eva Cerninakova (ece)]

The bug is no more relevant in the Angular client.