View Issue Details

IDProjectCategoryView StatusLast Update
0003026OXID eShop (all versions)1. ----- eShop frontend -----public2012-12-10 14:37
ReporterHolger Kohnen 
PriorityhighSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version 
Target VersionFixed in Version4.5.2 revision 38481 
Summary0003026: Weird exception handling in oxshopcontrol->start
DescriptionIf 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 Reproduceconfig.inc.php
==============
$this->sTheme = 'wrong_folder';
TagsNo tags attached.
ThemeBoth
BrowserAll
PHP Versionany
Database Versionany

Relationships

related to 0002394 resolvedrimvydas_paskevicius oxshopcontrol redirects without logging the error 

Activities

leofonic

2011-07-04 20:27

reporter   ~0004818

See also https://bugs.oxid-esales.com/view.php?id=2394

birute_meilutyte

2011-07-06 13:15

reporter   ~0004830

@developers: check from source code side if such issue still exist

arvydas_vapsva

2011-08-02 16:52

reporter   ~0004915

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)