Databases
StackOverflow2013
Postsdbo
POZend Framework - displayExceptions property not working
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POZend Framework - displayExceptions property not working
    primarykey
    data
    text
    <p>In my ZF project's application.ini, I've set "resources.frontController.params.displayExceptions = 1". However, if an exception is thrown, the exception isn't displayed in the browser.</p> <p>Looking at the code in the generated ErrorController.php, it looks like the line that says:</p> <p>if ($this->getInvokeArg('displayExceptions') == true)</p> <p>always fails this condition.</p> <p>I'm new to the ZF, so there's likely something obvious I'm missing - but I don't know why it's not being set. It does seem to be processing the application.ini file, as it would be failing to connect to my database if it wasn't.</p> <hr> <p><strong>EDIT</strong></p> <p>Just found a clue:</p> <p>I had changed my modules directory. I've just undone that change, and this problem no longer occurs. However, I do actually want to change the modules directory. Here's a list of the changes I had made:</p> <p>In my application.ini, I added:</p> <pre><code>resources.frontController.moduleDirectory = APPLICATION_PATH "/modules" </code></pre> <p>In my Bootstrap class, I added:</p> <pre><code>protected function _initFrontController() { $front = Zend_Controller_Front::getInstance(); $front-&gt;addModuleDirectory(dirname(__FILE__) . '/modules'); $front-&gt;setDefaultModule('frontend'); return $front; } </code></pre> <p>This seems to successfully handle the module's new location and the site works fine (except that the displayExceptions flag isn't being set properly).</p> <p>Any ideas why this would be causing this symptom?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDan
    1. USDan
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POZend Framework - displayExceptions property not working
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POZend Framework - displayExceptions property not working
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POZend Framework - displayExceptions property not working
      1. USFlexer
      1. VTFavorite
    1. COWhat does the debugger tell you? Or Zend_Debug::dump() for these variables?
      singulars
      1. POZend Framework - displayExceptions property not working
      1. USmarkus
    2. CO@markus What variables should I be looking at? Sorry, I'm new to ZF, so not really sure how to programmatically access those application.ini settings. I tried dumping out Zend_Controller_Front::getInstance()->getParams(), but that didn't have anything useful in it.
      singulars
      1. POZend Framework - displayExceptions property not working
      1. USDan
    3. COWhat is your application environment? Usually it should be set to `development` in order to display exceptions.
      singulars
      1. POZend Framework - displayExceptions property not working
      1. USVika
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload