Good day
Im using Suitecrm version 8.2.3. When I create a new Tasks I get the attached Error showing. The record does get created though, its just that the users sees the error and tries to create the record again and it creates duplicates. I do not get this error when logging in and creating a task as an admin user.
Could you please share some light on this.
Hi
if you can find a more detailed error message in your logs , that would be quite helpful.
Also, please state your exact PHP version.
Thanks
Hi
Im using PHP version 8.0.28
This is the error I see on the logs
It’s a known issue, you can track it here
opened 10:10AM - 24 Sep 22 UTC
Type:Bug
Priority:Important
Type:Suite7
#### Issue
I've grown accustomed to seeing this kind of errors a lot in the For… ums, it's definitely a bug that should be looked at...
#### Expected Behavior
No MySql errors.
#### Actual Behavior
Have a look at this list of issues:
https://community.suitecrm.com/search?q=config.deleted
#### Possible Fix
Just guessing: although `config` is a special table, with a special structure, some database class somewhere is treating it like a regular SuiteCRM table, and adding clauses like `AND config.deleted = 0` which won't work.
#### Your Environment
* SuiteCRM Version used: SuiteCRM 8, several versions.
Some of those Forums issues are very old, like 2014! This error seems to have resurfaced after being fixed ([here](https://github.com/salesagility/SuiteCRM/commit/27bd7606f539e7bed55873b4343770c10a5ec05a))
I’m afraid there’s no fix yet…
Thanks for that update, is there no way to not show this error , whilst we wait for a solution?
Sorry, I don’t know where to change this.
If you can get a PHP stack trace of that error, it would be quite helpful and I could take a quick look. But I just don’t have the time to go into full debugging mode on this myself.
@nzi200779 This might be an issue related to roles and permissions of users
Do you have any roles set for normal users ?
Good day
Most of the users are normal users, I will look at permissions but I doubt its the cause as this was working after the initial install.
Regards