View Issue Details

IDProjectCategoryView StatusLast Update
0007279OXID eShop (all versions)2.2. Shop settingspublic2024-08-07 09:37
Reporterd3 Assigned To 
PriorityhighSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Product Version6.3.1 
Fixed in Version7.0.0 
Summary0007279: Shop deactivated modules
DescriptionIn some situations the shop cannot find all files of a module. (server busy etc.)
Result: The shop deactivates the affected module.

The bad thing is: No one is informed about it. (no mail to shopowner etc)

We just have the case that an article export module to Google Shopping has not made a new export for several months. No one has noticed this, as everything happens automatically via cronjob. If it works...

Solution 1)
If a module is automatically deactivated, a mail is sent to the shop owner at the same time.

Solution 2)
There is a config.inc parameter to disabled this function -> "blDoNotDisableModuleOnError"
This Parameter should be activated by default.
TagsNo tags attached.
ThemeNot defined
BrowserNot defined
PHP VersionNot defined
Database VersionNot defined

Activities

QA

2021-09-22 09:21

administrator   ~0013485

Hey @d3,

I acknowledged the issue as 1) would be a handy feature request and one could think about the 2) proposal.

Could you provide further information about how the shop doesn't find some files sometimes? Is this about a too busy webserver and PHP has to wait too long for an answer? Could you provide us an error log so we can investigate more closely?
Of course you can write to [email protected] if it is about sensitive information.

Greetings,
Michael

SvenBrunk

2024-08-07 09:37

administrator   ~0017355

In version 7, if the shop encounters an issue where certain module files are not findable, it will display a notice in the module area. In some cases, this may cause the shop to stop functioning, potentially throwing an exception and redirecting to the homepage. However, this is intended behavior, and the module will remain activated anyhow.