Unable to view Stream on any Entities after upgarde from 8.1.5 to 8.2.x

[khopper]

Unable to view Stream on any Entities after upgrade from 8.1.5 to 8.2.x

I run my system in a virtual environment, very easy to revert back to before upgrade.
I get no error messages during upgrade but once done, unable to see any and all stream comments under all entities.
No errors in the log files. Help?

[lazovic]

Hi khopper,

Please tell me if there are any unofficial extensions installed in your EspoCRM instance?

Also, check if there are records in the Note table in your database for EspoCRM.

[yuri]

How the Stream panel looks? Is it just empty?

Does it happen for Admin users too?

[khopper]

lazovic Yes, I have 1 unofficial extension (Free) "stream-modified-at 1.1.0" from Eblasoft Bilişim Ltd.
yuri The Stream just looks empty for users and admins.

[lazovic]

khopper,

I just tried to reproduce this issue: I installed this extension on EspoCRM v8.1.5, created several posts in the stream and upgraded EspoCRM to 8.2.2 version. The records are successfully displayed in the stream.

Please tell me, have you checked the note table in the instance database? Also, try checking the browser console (by pressing on F12 key), perhaps certain errors regarding the display of notes in the stream are logged there.

[item]

Hi,
it's not hijack post but maybe related :

on demo :
strange we can create relation to "Note" Entity !?
Create relationship (many2many and many2one tested) but after when we go to record, we have a "error 500"

Maybe it's related ?

[yuri]

Will fix it.

[khopper]

item yuri Here are my relations in my instance. Still waiting to test upgrade again as backups are currently running.

[item]

Hi khopper,
i have v8.2 and no issue with stream or any other.
maybe you can uninstall you extension.. and clear cache (browser too) .. and see.
Hope someone can help.

[khopper]

Getting the following error after upgrade to 8.2.2
No Entities are showing any records after upgrade.
All Tables (Note, PBX, etc.) exist and look normal on the backend.

[2024-04-07 16:23:41] ERROR: Slim Application Error Type: Error Code: 0 Message: Class "Espo\Modules\Crm\Services\Lead" not found File: /var/www/espocrm/custom/Espo/Custom/Services/Lead.php Line: 34 Trace: #0 /var/www/espocrm/vendor/composer/ClassLoader.php(576): include() #1 /var/www/espocrm/vendor/composer/ClassLoader.php(427): Composer\Autoload\{closure}() #2 [internal function]: Composer\Autoload\ClassLoader->loadClass() #3 /var/www/espocrm/application/Espo/Core/Utils/File/ClassMap.php(170): ReflectionClass->__construct() #4 /var/www/espocrm/application/Espo/Core/Utils/File/ClassMap.php(130): Espo\Core\Utils\File\ClassMap->fillHashFromFileList() #5 /var/www/espocrm/application/Espo/Core/Utils/File/ClassMap.php(98): Espo\Core\Utils\File\ClassMap->getClassNameHash() #6 /var/www/espocrm/application/Espo/Core/Utils/ClassFinder.php(78): Espo\Core\Utils\File\ClassMap->getData() #7 /var/www/espocrm/application/Espo/Core/Utils/ClassFinder.php(68): Espo\Core\Utils\ClassFinder->load() #8 /var/www/espocrm/application/Espo/Core/Utils/ClassFinder.php(55): Espo\Core\Utils\ClassFinder->getMap() #9 /var/www/espocrm/application/Espo/Core/ServiceFactory.php(56): Espo\Core\Utils\ClassFinder->find() #10 /var/www/espocrm/application/Espo/Core/ServiceFactory.php(61): Espo\Core\ServiceFactory->getClassName() #11 /var/www/espocrm/application/Espo/Core/Record/ServiceFactory.php(134): Espo\Core\ServiceFactory->checkExists() #12 /var/www/espocrm/application/Espo/Core/Record/ServiceFactory.php(100): Espo\Core\Record\ServiceFactory->createInternal() #13 /var/www/espocrm/application/Espo/Core/Record/ServiceContainer.php(82): Espo\Core\Record\ServiceFactory->create() #14 /var/www/espocrm/application/Espo/Core/Record/ServiceContainer.php(74): Espo\Core\Record\ServiceContainer->load() #15 /var/www/espocrm/application/Espo/Core/Controllers/RecordBase.php(135): Espo\Core\Record\ServiceContainer->get() #16 /var/www/espocrm/application/Espo/Core/Controllers/RecordBase.php(247): Espo\Core\Controllers\RecordBase->getRecordService() #17 /var/www/espocrm/application/Espo/Core/Api/ControllerActionProcessor.php(87): Espo\Core\Controllers\RecordBase->getActionList() #18 /var/www/espocrm/application/Espo/Core/Api/ControllerActionHandler.php(65): Espo\Core\Api\ControllerActionProcessor->process() #19 /var/www/espocrm/vendor/slim/slim/Slim/MiddlewareDispatcher.php(65): Espo\Core\Api\ControllerActionHandler->handle() #20 /var/www/espocrm/application/Espo/Core/Api/RouteProcessor.php(222): Slim\MiddlewareDispatcher->handle() #21 /var/www/espocrm/application/Espo/Core/Api/RouteProcessor.php(149): Espo\Core\Api\RouteProcessor->processControllerAction() #22 /var/www/espocrm/application/Espo/Core/Api/RouteProcessor.php(127): Espo\Core\Api\RouteProcessor->processAfterAuth() #23 /var/www/espocrm/application/Espo/Core/Api/RouteProcessor.php(78): Espo\Core\Api\RouteProcessor->processInternal() #24 /var/www/espocrm/application/Espo/Core/Api/Starter.php(109): Espo\Core\Api\RouteProcessor->process() #25 /var/www/espocrm/vendor/slim/slim/Slim/Handlers/Strategies/RequestResponse.php(38): Espo\Core\Api\Starter->Espo\Core\Api\{closure}() #26 /var/www/espocrm/vendor/slim/slim/Slim/Routing/Route.php(358): Slim\Handlers\Strategies\RequestResponse->__invoke() #27 /var/www/espocrm/vendor/slim/slim/Slim/MiddlewareDispatcher.php(65): Slim\Routing\Route->handle() #28 /var/www/espocrm/vendor/slim/slim/Slim/MiddlewareDispatcher.php(65): Slim\MiddlewareDispatcher->handle() #29 /var/www/espocrm/vendor/slim/slim/Slim/Routing/Route.php(315): Slim\MiddlewareDispatcher->handle() #30 /var/www/espocrm/vendor/slim/slim/Slim/Routing/RouteRunner.php(68): Slim\Routing\Route->run() #31 /var/www/espocrm/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php(45): Slim\Routing\RouteRunner->handle() #32 /var/www/espocrm/vendor/slim/slim/Slim/MiddlewareDispatcher.php(121): Slim\Middleware\RoutingMiddleware->process() #33 /var/www/espocrm/vendor/slim/slim/Slim/Middleware/ErrorMiddleware.php(76): Psr\Http\Server\RequestHandlerInterface@anonymous->handle() #34 /var/www/espocrm/vendor/slim/slim/Slim/MiddlewareDispatcher.php(121): Slim\Middleware\ErrorMiddleware->process() #35 /var/www/espocrm/vendor/slim/slim/Slim/MiddlewareDispatcher.php(65): Psr\Http\Server\RequestHandlerInterface@anonymous->handle() #36 /var/www/espocrm/vendor/slim/slim/Slim/App.php(199): Slim\MiddlewareDispatcher->handle() #37 /var/www/espocrm/vendor/slim/slim/Slim/App.php(183): Slim\App->handle() #38 /var/www/espocrm/application/Espo/Core/Api/Starter.php(76): Slim\App->run() #39 /var/www/espocrm/application/Espo/Core/ApplicationRunners/Api.php(45): Espo\Core\Api\Starter->start() #40 /var/www/espocrm/application/Espo/Core/Application/RunnerRunner.php(84): Espo\Core\ApplicationRunners\Api->run() #41 /var/www/espocrm/application/Espo/Core/Application.php(78): Espo\Core\Application\RunnerRunner->run() #42 /var/www/espocrm/public/api/v1/index.php(35): Espo\Core\Application->run() #43 {main} Tips: To display error details in HTTP response set "displayErrorDetails" to true in the ErrorHandler constructor.  
​

[item]

Hi khopper,
it's seemt :
/var/www/espocrm/custom/Espo/Custom/Services/Lead.php
this file extend old ...

you need to just change in these files :

function ......... extend Espo\Services\Record

See more detail in V8.2 annoncement section in this forum.

[khopper]

I already tried removing any customization entirely from /var/www/espocrm/custom/Espo/Custom/Services/Lead.php and get the same issues.
They were old customizations that were not being used anyways.

[item]

please send the content .. not all but the first function declartion of /var/www/espocrm/custom/Espo/Custom/Services/Lead.php

[khopper]

This is what is currently in the file since I reverted to my backup

namespace Espo\Custom\Services;

use \Espo\ORM\Entity as Entity;

class Lead extends \Espo\Modules\Crm\Services\Lead
{
    protected function getDuplicateWhereClause(Entity $entity, $data)
    {
        return array(
            'AND' => array(
                array(
                    'name' => $entity->get('name'),
                ),
                'OR' => array(
                    array(
                        'phoneNumber' => $entity->get('phoneNumber'),
                    ),
                ),
            )
        );
    }
}

[item]

Hi,
you need to change just this line :

class Lead extends \Espo\Services\Record

But the function getDuplicateWhereClause must not be writed here !
see : https://docs.espocrm.com/development/duplicate-check/

I think the best solution is :

remove the function getDuplicateWhereClause
rename the declaration to class Lead extends \Espo\Services\Record
so this files have a empty class

namespace Espo\Custom\Services;

use \Espo\ORM\Entity as Entity;

class Lead extends \Espo\Services\Record​
{

}​ 

and write your duplicate function following the doc : https://docs.espocrm.com/development/duplicate-check/

[yuri]

As we stated in upgrade notes, we removed service classes. https://forum.espocrm.com/forum/anno...sed#post104208

[khopper]

The instructions are NOT super clear to non-programmers such as myself.
I apologize for not interrupting the instructions as you would have expected.
Not everyone that is in this forum is a coding engineer such as myself.
Maybe the instructions could use some touching up? layman's terms? More details?

[yuri]

This actions are needed only for those who already did programming customizations. Upgrade should run smooth otherwise. Just need to replace 

extends \Espo\Modules\Crm\Services\Lead
=>
extends \Espo\Service\Record

[khopper]

item yuri
I did as suggested and then ran the update. however now getting this error. (stream not showing) Note table exist in DB.

[yuri]

I believe you have some customization that utilizes "views/stream/row-actions/default" view that does not exist anymore.

Try to search (grep) the string "views/stream/row-actions/default" in the code to find out where exactly.

[yuri]

Once you found, replace

views/stream/row-actions/default
=>
views/stream/record/row-actions/default

[khopper]

I know for a fact 100% that I have never made any customization to the stream it self!
Which files would I search through regardless?

[yuri]

Try to search in the entire client directory.

[yuri]

Feel free to contact us via the customer portal. We will try to help with the upgrade.

[khopper]

@yuri
Okay, upgrade successful!
I did find that there was a customization to the notes as you indicated so I just simply removed it completely.
The customization was to show date and time of all post. (can't this just be an option in the admin settings or just a default?)

[khopper]

However I have noticed a few errors in the dev console of the browser - does not seem to affect the page loading and functioning.

1. Accounts = Could not set element '#main > .record .side .panel[data-name="default"] > .panel-body .field[data-name="complexModified"] [data-name="modifiedBy"]'.

2. Opportunities = Custom:Views.opportunity.Fields.ServiceAddress: module ID should use slashes instead of dots and hyphen instead of CamelCase.

3. Opportunities = Views.Fields.Address: module ID should use slashes instead of dots and hyphen instead of CamelCase.

4. Task = Could not set element '#main > .record .side .panel[data-name="default"] > .panel-body .field[data-name="complexModified"] [data-name="modifiedBy"]'.

Any ideas?

[khopper]

Disregard the "modifiedBy" errors - they went away after removing maintenance mode!?!
They come up from time to time but refreshing the page loads okay.... ?

[yuri]

> 1. Accounts = Could not set element '#main > .record .side .panel[data-name="default"] > .panel-body .field[data-name="complexModified"] [data-name="modifiedBy"]'.

This one can be neglected. In most cases it's not a problem. It's a debugging measure I added to discover issues.

> 2. Opportunities = Custom:Views.opportunity.Fields.ServiceAddress: module ID should use slashes instead of dots and hyphen instead of CamelCase.

Change:
Custom:Views.opportunity.Fields.ServiceAddress
=>
custom:views/opportunity/fields/service-address

> 3.

Views.Fields.Address
=>
views/fields/address

[khopper]

Thank you for your guidance, everything is 100% now!