Hola, logré actualizar mi versión de 7.8.31 a 7.10.33, pero me sale dos errores que no logro resolver, el primero dice:
Tue Apr 26 01:17:00 2022 [5652][70ad7043-1e82-ac24-53ef-564d0eec76e2][FATAL] A language key does not found: [ERR_FIELD_FROM_IS_NOT_SET]
Tue Apr 26 01:17:00 2022 [5652][70ad7043-1e82-ac24-53ef-564d0eec76e2][FATAL] A language key does not found: [ERR_FIELD_FROMNAME_IS_NOT_SET]
Tue Apr 26 01:17:00 2022 [5652][70ad7043-1e82-ac24-53ef-564d0eec76e2][FATAL] A language key does not found: [ERR_FIELD_FROM_NAME_IS_NOT_SET]
Tue Apr 26 01:17:00 2022 [5652][70ad7043-1e82-ac24-53ef-564d0eec76e2][FATAL] A language key does not found: [ERR_FIELD_FROM_ADDR_NAME_IS_EMPTY]
Yo solo trabajo en Ingles en SuiteCRM. Mi entorno es: Windows 10 Pro, PHP 7.4.27 bajo Xampp y no he cambiado nada en el idioma.
El otro error es:
Do you have a file called custom/modules/Emails/language/en_us.lang.php? If you do, that’s not the best way to customize language strings, and it’s causing that language key error.
Access your database from phpMyAdmin, go in the email_addresses table, find the row with that email, and remove that ' from the beginning. That might fix it.
Many thanks for your help!! I found in that email an apostrophe, so you are right that’s the problem. So I deleted that hopefully it works
But in the other hand how can I do about…
Wed Apr 27 22:19:29 2022 [5668][ecc48633-68d7-f08d-0ab0-5756dc91f2e7][FATAL] A language key does not found: [ERR_FIELD_FROM_IS_NOT_SET]
Wed Apr 27 22:19:29 2022 [5668][ecc48633-68d7-f08d-0ab0-5756dc91f2e7][FATAL] A language key does not found: [ERR_FIELD_FROMNAME_IS_NOT_SET]
Wed Apr 27 22:19:29 2022 [5668][ecc48633-68d7-f08d-0ab0-5756dc91f2e7][FATAL] A language key does not found: [ERR_FIELD_FROM_NAME_IS_NOT_SET]
Wed Apr 27 22:19:29 2022 [5668][ecc48633-68d7-f08d-0ab0-5756dc91f2e7][FATAL] A language key does not found: [ERR_FIELD_FROM_ADDR_NAME_IS_EMPTY]
I really appreciate your guide about it…in advanced thks.
Sorry about it, it was my mistake. I was checking and I don’t have that file in custom/modules/Emails/language/en_us.lang.php, in fact I found this file in several parts (en_us.lang.php), so in your path I found just:
But the similar one is sugarcrm/modules/Emails/language/en_us.lang.php, so I have to do any change?
Sorry, I checked the code and this is more complicated than it initially seemed. It’s not just an ordinary use of a language string, it’s a convoluted class called LangText that makes a simple thing become multi-layered and complex.
I did find one of these errors in my own logs, back in December 2020! I’ll leave it here with an extended stack trace, in case anybody wants to take a look (but I don’t advise it).
It’s possible that this will generate more errors, not less, so try this at a time when you don’t have users using the system… and change it back in case it goes wrong.
Yes it’s an earlier version. Forget about my suggestion above.
Try something simpler, change this line:
ErrorMessage::handler('A language key does not found: [' . $this->key . ']', self::LOG_LEVEL, $this->throw);
To
$text = 'MissingString';
Instead of throwing an error and blocking execution, it will just go on with a missing label. This is a hack… but it might solve your current problem. And I have a certain hope that once you’re up to date with the latest version, this issue will go away by itself.
Please I need your guide, because I did your solution and it works in the test server very well, but when I put that in the production server, something it`s not working.
So, let me explain more, when I run the same process in the test and production server, I received a different result, basicly the process, use a WorkFlow, and it have to send a email, but the production server send some wrong information, but the test server works fine.
Both server use, same configuration, systems (Windows 10 pro, xampp, PHP 7.4.27)
Start a new thread and include more details. That seems like an entirely new issue. This change only solves a FATAL error, and it’s a fatal error that shouldn’t affect much of anything, since it’s just a label failure. You must have some other issue now…