View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003026 | OXID eShop (all versions) | 1. ----- eShop frontend ----- | public | 2011-07-04 17:44 | 2012-12-10 14:37 |
| Reporter | Holger Kohnen | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 4.5.2 revision 38481 | ||||
| Summary | 0003026: Weird exception handling in oxshopcontrol->start | ||||
| Description | If the call to: $this->_process( $sClass, $sFunction ); raises an exception, then the shop redirects to start in the first two catch-blocks, it also calls: oxUtilsView::getInstance()->addErrorToDisplay( $oEx ); But in some cases you will not see the error, because it needs to be rendered in the template. All this is only a problem in development mode (disabled shop productive mode). A simple solution would be: - Allways log all exceptions to EXCEPTION.log Another nice addition would be: - No exception-redirects in development mode (Because if you got an error you normally try to fix it and then hit reload in the browser, but if you was redirected it get's more complicated) | ||||
| Steps To Reproduce | config.inc.php ============== $this->sTheme = 'wrong_folder'; | ||||
| Tags | No tags attached. | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
| related to | 0002394 | resolved | rimvydas_paskevicius | oxshopcontrol redirects without logging the error |
|
|
See also https://bugs.oxid-esales.com/view.php?id=2394 |
|
|
@developers: check from source code side if such issue still exist |
|
|
implemented: (Because if you got an error you normally try to fix it and then hit reload in the browser, but if you was redirected it get's more complicated) |
