Internal Server Error with custom record action, no further info

[cdon]

Hi!

I’m trying to add a custom record action following this tutorial:

SuiteCRM Developer Insights - Module Record Actions - SuiteCRM

I’m using the bitnami suitecrm image with suitecrm 8.5.1.

I’ve modified the files according to my needs, but in principle I’ve just changed the module and action name. Everything seems to work up until the moment when I select a Quote in the modal, then I get
UI: Unexpected error when calling action
Response:

{
“errors”: [
{
“message”: “Internal server error”,
“extensions”: {
“category”: “internal”
},
“locations”: [
{
“line”: 2,
“column”: 3
}
],
“path”: [
“createProcess”
]
}
],
“data”: {
“createProcess”: null
}
}
Blockquote

Unfortunately, despite logging on debug level (I get all the other debug and info messages in public/legacy/suitecrm.log), there is no further info to be found in suitecrm.log or the apache error log.

Iv’e created the following files (please find them via the dropbox link):
/opt/bitnami/suitecrm/extensions/defaultExt/config/modules/Accounts/recordview/actions/create-pdf.php
/opt/bitnami/suitecrm/extensions/defaultExt/modules/Accounts/Process/Service/RecordActions/CreatePdfAction.php
/opt/bitnami/suitecrm/public/legacy/custom/Extension/modules/Accounts/Ext/Language/en_us.create_pdf.php

I’ve also uploaded the full request payload.
https://www.dropbox.com/scl/fo/e36hpsxd41xg52ko6yuli/ACi7WeIQ7EJt1RWArkXG8fM?rlkey=3u5ze04utmsj4oo61fjvzuh0n&st=aqnmlo0g&dl=0

Thanks in advance to anyone who can point out any mistakes or help me get better error messages!

BR,
Chris

[rsp]

New button triggering workflow

I tried to implement the functionality on my machine. I could get it successfully working. The following are the code changes: public\legacy\custom\Extension\application\Ext\Language\en_us.lang.php <?php $app_strings['LBL_ASSIGN_STATUS_CONFIRMATION']='Are you sure to change the status of this lead?'; extensions\defaultExt\config\modules\Leads\recordview\actions\assign_lead.php <?php namespace Symfony\Component\DependencyInjection\Loader\Configurator; use Symfony\Component\DependencyInjec…

Insert Link into Top Navigation

I have added an external link under ‘Marketing’ menu with the following steps. Copy ‘themes\SuiteP\tpls\header.tpl’ & ‘themes\SuiteP\tpls_headerModuleList.tpl’ at ‘custom\themes\SuiteP\tpls\header.tpl’ & ‘custom\themes\SuiteP\tpls_headerModuleList.tpl’ Open custom\themes\SuiteP\tpls\header.tpl and change the following line to include _headerModuleList.tpl from custom folder. {if $AUTHENTICATED} <div id="ajaxHeader"> {include file="custom/themes/SuiteP/tpls/_headerModuleList.tpl"…

[cdon]

Thanks for the example, but I fail to find the difference - it seems they did everything just like in my code…?

[rsp]

You have to run a symfony cache clear from your instance root folder.

.bin/console cache:clear

[pgr]

If you still have problems after the cache:clear, the way to get better messages is to go in .env file and change APP_ENV to dev.

Then, if everything starts crashing (usually it’s a Doctrine fatal error), you need to run a composer install to get the dev packages.

After that it should all work again; and you can reproduce your error, and in the browser developer tools, network tab, you will find helpful stack traces in one of the grapql calls (you have to look around to find each one).

[cdon]

Thanks! setting the dev value in the .env file got me the error messages!
It seems that

LoggerManager::getLogger()

doesn’t work:
Class \u0022App\Extension\defaultExt\modules\Accounts\Process\Service\RecordActions\LoggerManager\u0022 not found

I tried importing the one from Consolidation\Log, but that doesn’t seem to be the correct one.

Without the logger calls, the script works fine - I’d still like to log things though

BR,
Chris

[pgr]

I think you just need to fix your logging code. If you’re not in legacy mode, you shouldn’t be looking for the LoggerManager, and much less if you’re looking for it under defaultExt… it’s a core file.

If you’re not in legacy mode, just use the “modern” side of logging, as a randomly-selected example, copy what you find in this file.