Email address save error for v7.13

rsp · 30 November 2023 15:19

I am getting ‘Email address save error’ on SuiteCRM v7.13.

Whenever a user logged in, I am getting this error in CRM log.

[FATAL] User username has logged in.
[FATAL] Email address save error

Is anyone face this issue and able to resolve it?
Thanks in advance!

pgr · 30 November 2023 17:30

Do you have any custom code or logic hook that could be causing the User bean to be saved at the time of login?

rsp · 30 November 2023 17:37

Thank you so much for your quick reply. As per my knowledge, I don’t have custom code or logic hook related to users in custom folder. Is there any particular module/code file, I should check to find out about this error?

pgr · 30 November 2023 17:51

I don’t know much about this, I just searched the code and found that that error message appears inside the User bean save function. So perhaps trying to find out why it’s being called could be a good strategy.

Or you could simply ignore it, if it’s not causing any trouble.

rsp · 1 December 2023 17:25

You’re correct. It is not causing any problem so I will leave it for now. If I found any solution, I will post here.

chris001 · 2 December 2023 01:26

Does this fix your issue?

rsp · 4 December 2023 14:23

I tried below code changes, but it did not work. Are there any other code changes?

github.com/salesagility/SuiteCRM

Fixed #5871 - Cannot save user in custom code.

salesagility:hotfix-7.10.x ← cameronblaikie:issue-5871

opened 10:49AM - 11 Oct 18 UTC

cameronblaikie

+8 -7

## Description it was allowing the user to save (via code) but was returning fa…lse, now the the user can save and give an accurate result. ## Motivation and Context https://github.com/salesagility/SuiteCRM/issues/5871 ## How To Test This 1. create a logic hook to save a user via the accounts module upon save 2. the return result from calling save() should be the id of the user as expected. ## Types of changes - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ### Final checklist - [ ] My code follows the code style of this project found [here](https://docs.suitecrm.com/community/contributing-code/coding-standards/). - [ ] My change requires a change to the documentation. - [ ] I have read the [**How to Contribute**](https://docs.suitecrm.com/community/contributing-code/) guidelines.