View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006067 | OXID eShop (all versions) | 1. ----- eShop frontend ----- | public | 2015-03-03 15:16 | 2015-03-23 17:43 |
Reporter | d.bloessl | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | unable to reproduce |
Status | closed | Resolution | open | ||
Product Version | 4.9.3 / 5.2.3 | ||||
Summary | 0006067: oxAutoload crashes, if config is not initialized | ||||
Description | When a 404 page is delivered and a class from a not yet loaded module is used, it leads to a EXCEPTION_SYSTEMCOMPONENT_CLASSNOTFOUND. This leads to problems, if you need special classes for displaying a header. | ||||
Steps To Reproduce | Try to get a module class from oxRegistry in handlePageNotFoundError(). In oxAutoload the request to $oModulelist->getActiveModuleInfo() returns an empty list and the class is not found. If the class is added to modules/functions.php with a require_once, everything is working fine. | ||||
Tags | No tags attached. | ||||
Theme | Azure | ||||
Browser | All | ||||
PHP Version | any | ||||
Database Version | any | ||||
|
Reminder sent to: d.bloessl Can you please provide us with a code example and explain in detail why you are trying to get a module class from oxRegistry in handlePageNotFoundError() ? Thank you in advance. |
|
No feedback by reporter for >2 weeks. Closed. |