From: HL <fre...@gm...> - 2014-07-25 08:57:06
|
Hi all ! For some reason, I miss and cannot figure out the config setting that disables BACKTRACE on the webpage Thus, when one uses a direct link like http://myvf.site.foo/Record/12345 and the record 12345 does not exist in the Solr Database the page gets full of php UGLY BACKTRACE errors ! Is there a way to stop this ? Thanks, Harry |
From: Zeno T. <z.t...@ci...> - 2014-07-25 09:47:54
|
Hi, Il 25/07/2014 10:56, HL ha scritto: > For some reason, > I miss and cannot figure out the config setting that disables > BACKTRACE on the webpage > > Thus, > when one uses a direct link like > > http://myvf.site.foo/Record/12345 > and the record 12345 does not exist in the Solr Database > the page gets full of php UGLY BACKTRACE errors ! > > Is there a way to stop this ? in config.ini there is only a 'debug' option. You can insert 'true' or 'false' If you have insert 'false', start/stop VF and you still see UGLY BACKTRACE errors, it better that you check php.ini. Attention that php.ini is a system-wide configuration, it isn't part of VF code. Bye Zeno Tajoli -- Dr. Zeno Tajoli Soluzioni per la Ricerca Istituzionale - Automazione Biblioteche z.t...@ci... fax +39 02 2135520 CINECA - Sede operativa di Segrate |
From: HL <fre...@gm...> - 2014-07-25 11:57:46
|
On 25/07/2014 12:47 μμ, Zeno Tajoli wrote: > Hi, > > Il 25/07/2014 10:56, HL ha scritto: >> For some reason, >> I miss and cannot figure out the config setting that disables >> BACKTRACE on the webpage >> >> Thus, >> when one uses a direct link like >> >> http://myvf.site.foo/Record/12345 >> and the record 12345 does not exist in the Solr Database >> the page gets full of php UGLY BACKTRACE errors ! >> >> Is there a way to stop this ? > > in config.ini there is only a 'debug' option. > You can insert 'true' or 'false' > > If you have insert 'false', start/stop VF and you still see > UGLY BACKTRACE errors, it better that you check php.ini. > > Attention that php.ini is a system-wide configuration, it isn't part of > VF code. Hm ... !!! config.ini debug=off in it is set to the default production setting for Debian ! php.ini error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT display_errors = Off display_startup_errors = Off |
From: Demian K. <dem...@vi...> - 2014-07-25 12:26:13
|
The backtrace indicates that you have development mode turned on in your Apache configuration -- comment out the development line in local/httpd-vufind.conf, restart Apache, and you should see a less detailed error page. (The reason this setting is controlled by Apache rather than config.ini is that otherwise, you would be unable to specify the error reporting level for errors involving the reading of the configuration itself). - Demian ________________________________________ From: HL [fre...@gm...] Sent: Friday, July 25, 2014 4:56 AM To: vuf...@li... Subject: [VuFind-General] Ugly Error Screen ( backtrace ) Hi all ! For some reason, I miss and cannot figure out the config setting that disables BACKTRACE on the webpage Thus, when one uses a direct link like http://myvf.site.foo/Record/12345 and the record 12345 does not exist in the Solr Database the page gets full of php UGLY BACKTRACE errors ! Is there a way to stop this ? Thanks, Harry ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ VuFind-General mailing list VuF...@li... https://lists.sourceforge.net/lists/listinfo/vufind-general |
From: HL <fre...@gm...> - 2014-07-25 13:08:02
|
On 25/07/2014 03:26 μμ, Demian Katz wrote: > The backtrace indicates that you have development mode turned on in your Apache configuration -- comment out the development line in local/httpd-vufind.conf, restart Apache, and you should see a less detailed error page. > > (The reason this setting is controlled by Apache rather than config.ini is that otherwise, you would be unable to specify the error reporting level for errors involving the reading of the configuration itself). > > - Demian That really slipped off my mind !! Yes indeed you are right !! But then again You are the developer ;) Thanks Demian !! Obligado !!! |