starred/SuiteCRM-SuiteCRM

Fork 0

mirror of https://github.com/SuiteCRM/SuiteCRM.git synced 2026-03-02 19:16:58 -05:00

[DEPRECATED] Array #3935

New issue

Open

opened 2026-02-20 16:11:37 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-20 16:11:37 -05:00

Owner

Originally created by @greenlanegreb on GitHub (Aug 27, 2019).

Originally assigned to: @Dillon-Brown on GitHub.

Mon Aug 26 21:28:23 2019 [919][1][DEPRECATED] Array

Issue

This should not be appearing within the error log and I am concerned that it may cause further issues across the Suite CRM system and create additional workload. By ironing out errors generated, it provides a cast iron base to move forward with (to add to recommendations already provided to Ashley regarding end user involvement being at the core of the development work that Suite CRM undertakes.

Expected Behavior

This should not be happening.

Actual Behavior

Possible Fix

Steps to Reproduce

1.By checking the error.log in depreciated status.
2.
3.
4.

Context

SuiteCRM Version used: 7.11.8

Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Version 76.0.3809.100 (Official Build) Built on Ubuntu , running on LinuxMint 18.3 (64-bit)

Environment name and version (e.g. MySQL, PHP 7): PHP 7.0.33 - 10.3.15-MariaDB-1 - Debian 10 Apache 2.4.28 (Debian)

Operating System and version (e.g Ubuntu 16.04): As Above.

This issue has not been resolved with a quick rebuild.

Many thanks.

Originally created by @greenlanegreb on GitHub (Aug 27, 2019). Originally assigned to: @Dillon-Brown on GitHub.  Mon Aug 26 21:28:23 2019 [919][1][DEPRECATED] Array   #### Issue  This should not be appearing within the error log and I am concerned that it may cause further issues across the Suite CRM system and create additional workload. By ironing out errors generated, it provides a cast iron base to move forward with (to add to recommendations already provided to Ashley regarding end user involvement being at the core of the development work that Suite CRM undertakes. #### Expected Behavior  This should not be happening. #### Actual Behavior   #### Possible Fix  #### Steps to Reproduce   1.By checking the error.log in depreciated status. 2. 3. 4. #### Context   SuiteCRM Version used: 7.11.8 Browser name and version (e.g. Chrome Version 51.0.2704.63 (64-bit)): Version 76.0.3809.100 (Official Build) Built on Ubuntu , running on LinuxMint 18.3 (64-bit) Environment name and version (e.g. MySQL, PHP 7): PHP 7.0.33 - 10.3.15-MariaDB-1 - Debian 10 Apache 2.4.28 (Debian) Operating System and version (e.g Ubuntu 16.04): As Above. This issue has not been resolved with a quick rebuild. Many thanks.

deekerman added the

labels

2026-02-20 16:11:37 -05:00

deekerman commented

2026-02-20 16:11:39 -05:00

Author

Owner

@greenlanegreb commented on GitHub (Aug 28, 2019):

Good afternoon Cameron, what is this bug regarding please and is there any temporary fix? Many thanks.

@greenlanegreb commented on GitHub (Aug 28, 2019): Good afternoon Cameron, what is this bug regarding please and is there any temporary fix? Many thanks.

deekerman commented

2026-02-20 16:11:39 -05:00

Author

Owner

@pgorod commented on GitHub (Aug 29, 2019):

@greenlanegreb SuiteCRM logs are very verbose, I don't like it either, but that's something we inherited and have been slowly improving. We're talking about literally thousands of logging messages throughout the code, and thousands of admins and add-on developers that rely on some of these messages, they can't just be taken away indiscriminately.

Anyway, all this should be triaged in the Forums, before coming on Github. Nothing should be here that is specific to someone's system, it comes here when it is ascertained that it is a generic problem in SuiteCRM for everyone.

The approach I advise to the SuiteCRM logs is not to worry about each message. Some of your Issues here are just problems with your configuration. Others are messages that are there on purpose and should be there (DEPRECATEDs), your just don't need to raise your log level so high.

If everybody opened a new issue with each message they worry about in their logs, we'd just be flooded with unactionable stuff.

You can confidently ignore every log message that is WARN or below, that you cannot find a matching UI or functionality problem to go with it. So if you have an IMAP error, and a problem sending mail, do worry. But it it's just the message, ignore it.

@pgorod commented on GitHub (Aug 29, 2019): @greenlanegreb SuiteCRM logs are very verbose, I don't like it either, but that's something we inherited and have been slowly improving. We're talking about literally thousands of logging messages throughout the code, and thousands of admins and add-on developers that rely on some of these messages, they can't just be taken away indiscriminately. Anyway, all this should be triaged in the Forums, before coming on Github. Nothing should be here that is specific to someone's system, it comes here when it is ascertained that it is a generic problem in SuiteCRM for everyone. The approach I advise to the SuiteCRM logs is not to worry about each message. Some of your Issues here are just problems with your configuration. Others are messages that are there on purpose and should be there (DEPRECATEDs), your just don't need to raise your log level so high. If everybody opened a new issue with each message they worry about in their logs, we'd just be flooded with unactionable stuff. You can confidently ignore every log message that is WARN or below, that you cannot find a matching UI or functionality problem to go with it. So if you have an IMAP error, and a problem sending mail, do worry. But it it's just the message, ignore it.

deekerman commented

2026-02-20 16:11:39 -05:00

Author

Owner

@greenlanegreb commented on GitHub (Oct 13, 2019):

Thanks for this. Are there any updates in the direction of a fix please? Many thanks.

@greenlanegreb commented on GitHub (Oct 13, 2019): Thanks for this. Are there any updates in the direction of a fix please? Many thanks.

deekerman commented

2026-02-20 16:11:39 -05:00

Author

Owner

@Dillon-Brown commented on GitHub (Oct 16, 2019):

@greenlanegreb I can take a look at this, although so far haven't been able to replicate it (Probably comes from a specific module). As noted by @pgorod this is just a deprecation warning so it shouldn't actually impact your system, still worth us cleaning these up though.

@Dillon-Brown commented on GitHub (Oct 16, 2019): @greenlanegreb I can take a look at this, although so far haven't been able to replicate it (Probably comes from a specific module). As noted by @pgorod this is just a deprecation warning so it shouldn't actually impact your system, still worth us cleaning these up though.

deekerman commented

2026-02-20 16:11:39 -05:00

Author

Owner

@greenlanegreb commented on GitHub (Oct 17, 2019):

Hi, thanks for this. Yes, again, it’s coming from a fresh version of 7.11.8.

Thanks and Kind Regards.

@greenlanegreb commented on GitHub (Oct 17, 2019): Hi, thanks for this. Yes, again, it’s coming from a fresh version of 7.11.8. Thanks and Kind Regards.

deekerman commented

2026-02-20 16:11:39 -05:00

Author

Owner

@re8260 commented on GitHub (Dec 5, 2019):

HI @Dillon-Brown this MR add missing message: https://github.com/salesagility/SuiteCRM/pull/8360

@re8260 commented on GitHub (Dec 5, 2019): HI @Dillon-Brown this MR add missing message: https://github.com/salesagility/SuiteCRM/pull/8360