Script-level failure in SuiteCRM 8 - inbound emails admin page is blank

SuiteCRM8 has a lot of good new ideas, but the code seems still to be full of errors.
On a fresh installation the admin page to setup the incoming emails is blocked to show up by a failure.
The hosting-support told us that this is a script level issue!!
Their bug-report:
Since this is a script-level issue, we wouldn’t be able to provide much help. However, I did manage to find a discussion thread with similar issue that you may find interesting:

Users can’t fix this kind of errors for their own.
Until you fix this kind of bugs, SuiteCRM 8 is useless for everybody.
Please help and fix it ASAP.

2 Likes
  1. What is your exact SuiteCRM version?

  2. And PHP version?

  3. Does this error occur in the live demo? SuiteCRM Demo (user: will / pass: will)

  4. Anything peculiar about the method you used to install? Did you use this process?

SuiteCRM version 8.2.3
PHP version: at the moment php 7.4

We tried 8.0 but with 8.0 php the dashboard disappeared, so we went back to 7.4.

On your Demo-SuiteCRM we have no access to the admin page
So we can’t replicate the failure on the admin inbound email setup page

Or SuiteCRM was installed on a dedicated A2 managed VPS hostingserver by Softaculous

But on the User Profile for Will, we noticed that under „Email Settings“ there is also only the „General“-Tab and the „Settings“-Tab for the Email account is also missing.

How to fix this ?
Kind regards
Jog

1 Like

Yes the email config screens have been moved. The updated docs are here:

You’ll find the missing inbound accounts configuration screens by visiting your profile and checking the left-hand menu.

Where were you clicking to go that screen that shows the error you posted above?

Error occurred while fetching metadata

Hello, also if I can find the new link to the inbound email setup page,
the failure is still there:
a blank page with this error message:
Error occurred while fetching metadata
How to solve that ?

1 Like

Look for the corresponding error in the logs

nothing is added to the logs

In console:

ERROR Error: Uncaught (in promise): TypeError: Cannot read properties of undefined (reading ‘moduleMetadata’)
TypeError: Cannot read properties of undefined (reading ‘moduleMetadata’)
at o.project (dist_core___ivy_ngcc___fesm2015_core_js-_92d41-es2015.85e46b4b7cc754f175df.js:32:14075)
at o._next (node_modules_rxjs__esm2015_operators_index_js-es2015.8f2820c8ba6a75453b5e.js:1:24803)
at o.next (node_modules_rxjs__esm2015_operators_index_js-es2015.8f2820c8ba6a75453b5e.js:1:8495)
at node_modules_apollo-angular_fesm2015_ngApollo_js-_0ddc0-es2015.31fc3a06fac668918939.js:1:76264
at u.invoke (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:7152)
at Object.onInvoke (node_modules_angular_core_fesm2015_core_js-es2015.e67882692b6d3d658f6b.js:1:198185)
at u.invoke (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:7092)
at t.run (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:2551)
at polyfills-es2015.45bb605d0a332f4c1a8e.js:1:17235
at u.invokeTask (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:7770)
at w (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:16429)
at w (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:15965)
at polyfills-es2015.45bb605d0a332f4c1a8e.js:1:17272
at u.invokeTask (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:7770)
at Object.onInvokeTask (node_modules_angular_core_fesm2015_core_js-es2015.e67882692b6d3d658f6b.js:1:198001)
at u.invokeTask (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:7691)
at t.runTask (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:3166)
at b (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:9764)
at l.invokeTask [as invoke] (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:8849)
at m (polyfills-es2015.45bb605d0a332f4c1a8e.js:1:20635)

Thank for the advice:
The suitcrm.log shows a lot of “relationship”-errors:
e.g.
Fri Feb 10 10:27:25 2023 [1239197][1][ERROR] Unable to find relationship emails_email_templates
Fri Feb 10 10:27:25 2023 [1239197][1][ERROR] Unable to find relationship projects_contacts_resources
Fri Feb 10 10:27:25 2023 [1239197][1][ERROR] Unable to find relationship am_projecttemplates_contacts_resources
Fri Feb 10 10:27:25 2023 [1239197][1][ERROR] Unable to find relationship projects_contacts_resources
Fri Feb 10 10:27:25 2023 [1239197][1][ERROR] Unable to find relationship am_projecttemplates_contacts_resources

I have learned that SuiteCRM8 has a new file permission system.
I have tried the suggested permission setting comands of your manual,
but got failure messages. (I’m not used to Linux commands)

I suggest Admin / Repairs, then run a QR&R. Also a Repair Relationships.

If you have linux errors, copy them exactly and post them here, I might be able to help.

Thank you for your help.
1.) For both permission-comands from the manual I get the same failure:
find . -type d -not -perm 2775 -exec chmod 2775 {} ;
find . -type f -not -perm 0664 -exec chmod 0664 {} ;

find: missing argument to `-exec’

2.) How to find my “apache group” fpr this comand?
find . ! -user <apache_user> -exec chown <apache_user>:<apache_group>{} ;
chmod +x bin/console

You’re missing a backslash before the semicolon, sometimes these things get removed when copy-pasting into terminals, but you can add it manually. It should look like this:

find . -type d -not -perm 2775 -exec chmod 2775 {} \;

The correct user name to use in the chown is the own mentioned in the crontab instructions at the bottom of the screen in Admin / Schedulers.

Did you solve the problem with Inbound Mail Settings?

Thank you, all permissions are now set properly -
but the Inbound and Outbound Email Problem is still unsolved !
I can’t understand that SuiteCRM has not solved this ever-lasting problem better.
Emails are a key feature of CRMs.

the errors in the suitecrm.log are:
Thu Feb 16 17:12:39 2023 [3568204][1][ERROR] Unable to find relationship emails_email_templates
Thu Feb 16 17:12:39 2023 [3568204][1][ERROR] Unable to find relationship emails_email_templates
Thu Feb 16 17:12:39 2023 [3568204][1][ERROR] Unable to find relationship projects_users_resources
Thu Feb 16 17:12:39 2023 [3568204][1][ERROR] Unable to find relationship am_projecttemplates_users_resources
Thu Feb 16 17:25:34 2023 [3570896][1][ERROR] Unable to find relationship emails_email_templates
Thu Feb 16 17:25:34 2023 [3570896][1][ERROR] Unable to find relationship emails_email_templates
Thu Feb 16 17:25:34 2023 [3570896][1][FATAL] Mysqli_query failed.
Thu Feb 16 17:25:34 2023 [3570896][1][FATAL] Query Failed: SELECT favorites.*
FROM favorites
JOIN config ON ( config.id = favorites.parent_id )
WHERE favorites.assigned_user_id = ‘1’
AND favorites.parent_type = ‘Administration’
AND favorites.deleted = 0
AND config.deleted = 0
ORDER BY favorites.date_entered DESC LIMIT 0,10: MySQL error 1054: Unknown column ‘config.deleted’ in ‘where clause’ …

I get the same exact error as soon as I click on the Inbound Emails after the successful upgrade from 7.13.1 to 8.2.2. . The “moduleMetada” error is a good hint to the issue but I cannot point to the missing undefined variable. When I look at the polyfills-2015… 3b5e.js file it goes way over my head since I have not used javascript in a very very long time.
image
image

[2023-03-01 09:30:57] request.CRITICAL: Uncaught PHP Exception RuntimeException: “Failed to start the session because headers have already been sent by “/home/mysite.net/crm/public/legacy/modules/InboundEmail/metadata/editviewdefs.php” at line 1.” at /home/mysite.net/crm/vendor/symfony/http-foundation/Session/Storage/NativeSessionStorage.php line 152 {“exception”:“[object] (RuntimeException(code: 0): Failed to start the session because headers have already been sent by "/home/mysite.net/crm/public/legacy/modules/InboundEmail/metadata/editviewdefs.php" at line 1. at /home/mysite.net/crm/vendor/symfony/http-foundation/Session/Storage/NativeSessionStorage.php:152)”} []

@pgr We will really appreciate any guidance here…

Sorry, but I’m afraid I don’t know the answer and can’t think of anything intelligent to advise you…

No worries… I just got it. What worked for me was clearing the old inbound accounts directly in MySQL tables. I figured that I can recreate them since the simple authentication does not work with Microsoft anymore.