CMS MADE SIMPLE FORGE

CMS Made Simple Core

 
Back Back to List

[#8526] Customization of the errorConsole smarty exception page >= CMSMS 1.11.x

avatar
Created By: Deleted User (deleteduser_11200)
Date Submitted: 2012-10-16 07:23

Assigned To:
Resolution: Won't Fix
State: Closed
Summary:
Customization of the errorConsole smarty exception page >= CMSMS 1.11.x
Detailed Description:
When you break a CMSMS page because of a Smarty error you get the "OMG! You
broke this page." error page. For developers it gives enhough hints to fix the
problem for endusers it's not that friendly.

Please consider:

- Away to customize the OMG! error page, best will if it can be a template +
stylsheet already setup in the CMS
- Away to turn on logging in the Site Admin -> Admin log
- Also it will be very helpful if there is a switch to notify an 'admin'-user by
e-mail.

 
==

./lib/classes/class.Smarty_CMS.php:		
public function errorConsole(Exception $e)
$output = $this->fetch('error-console.tpl');
0 => '/lib/smarty/error-console.tpl'

==

History

Comments
avatar 
Date: 2012-10-16 07:33
Posted By: Deleted User (deleteduser_11200)

Customization is enhough. 

- Via a UDT added to {error-console.tpl): it's possible to make a notification
in the Admin Log and sent out a email.
avatar 
Date: 2012-10-16 07:39
Posted By: Goran Ilic (uniqu3)

And same way you can customize look of it by editing error-console.tpl if you
don't like it.
avatar 
Date: 2012-10-16 07:58
Posted By: Deleted User (deleteduser_11200)

I already did but since it's part of the core, I made this request to consider
an official solution.
avatar 
Date: 2014-04-05 22:22
Posted By: Robert Campbell (calguy1000)

An Exception at that level indicates a fatal error (or probably something that
should be fixed).  It could indicate all kinds of errors including stuff that is
irrecoverable.  And unhandled exceptions could leave things in a bad state. 
Allowing developers to execute a UDT, module or whatever else at that time is
probably not a good idea.  Could overcomplicate an already serious issue.
avatar 
Date: 2014-04-06 13:18
Posted By: Deleted User (deleteduser_11200)

While in development mode a tracelog, exception page can be very handy for the
webmaster, it gives indeed directions that something should be fixed.

I am afraid that an enduser on a live website facing such an exception page will
only become confused.  This is why I requested to consider customization of the
error-console template.


Most ideal will be if an enduser will report to the webmaster. In the real world
the enduser will never do. Some proactive webmasters will watch webserver error
logs or test intensively so they can find out more about broken pages.

Lazy webmasters on a hosting provider surpressing error logs can only find out
when the error console page is indexed in search engines. Who to blame the
webmaster or cmsms :)

Google -> "title:CMS Made Simple - Error consol" is telling me that there is
something wrong with the current reporting mechanism.
avatar 
Date: 2014-04-06 13:27
Posted By: Rolf (rolf1)

A few releases ago I added robots noindex nofollow to the error template
The technical stuff is hidden for non-admins using the admin cookie
And a mention is added to the admin log (is improved in 2.0)
avatar 
Date: 2014-04-06 13:40
Posted By: Deleted User (deleteduser_11200)

Nice work.
Updates

Updated: 2014-08-16 21:37
state: Open => Closed

Updated: 2014-04-05 22:22
resolution_id: 5 => 8

Updated: 2012-10-16 07:33
resolution_id: => 5