View Issue Details

IDProjectCategoryView StatusLast Update
0007294OXID ERP InterfaceOXID ERP Interface - subpublic2021-12-03 15:09
Reportermichael_keiluweit 
PrioritynormalSeverityminorReproducibilityalways
Status acknowledgedResolutionopen 
Product Version3.2.0 
Target VersionFixed in Version 
Summary0007294: EE: Heavily reseting of the tmp directory can lead to ERROR: Class "ProjectServiceContainer" not found
DescriptionWhen importing products with the ERP SOAP interface, the cache gets continuously reseted, when the ContentCache is activated ("blUseContenCaching") and the method \OxidEsales\EshopEnterprise\Application\Model\Article::onChange is executed:

if ($config->getConfigParam('blUseContentCaching')) {
    $genericCache = oxNew(ContentCache::class);
    $genericCache->reset();
}

The file container_cache.php itself is administered by the class \OxidEsales\EshopCommunity\Internal\Framework\DIContainer\Service\FilesystemContainerCache which is called by \OxidEsales\EshopCommunity\Internal\Container\ContainerFactory.

This leads to the assumption that the file container_cache.php must not be removed by the general cache reset. The property \OxidEsales\EshopCommunity\Core\Utils::$_sPermanentCachePattern could be extended by the named file, since the ContainerFactory will take care about it.


Since the code is placed in the oxideshop-ee package it, the report could also be made for the eshop project, but since it only occurs when importing is made, I selected the project OXID ERP Interface.
Additional Information[2021-11-10 12:48:19] OXID Logger.ERROR: Class "ProjectServiceContainer" not found ["[object] (Error(code: 0): Class \"ProjectServiceContainer\" not found
TagsNo tags attached.

Activities

michael_keiluweit

2021-12-03 15:09

developer   ~0013514

-MK