Welcome, Guest
Username: Password: Remember me

TOPIC: [FIXED] Better Error reporting

Better Error reporting 17 May 2015 15:08 #13035

  • MorganL
  • MorganL's Avatar
  • Offline
  • Platinum Member
  • Posts: 438
  • Thank you received: 53
  • Karma: 15
At present when the builder throws up an error, its quite tricky without version control / change history to know exactly what could be causing the issue without working backwards in memory which is tough when you have had a busy day.

Is it possible to expand the error at build time to say exactly which layout or part of the project has caused the error beyond the example below
Call to a member function isFk() on a non-object
Morgan Leecy MCSE

Novell / Linux
PHP. MYSQL, Apache, node.js
Coldfusion, JQuery, HTML5
Joomla
The administrator has disabled public write access.

Better Error reporting 18 May 2015 07:21 #13044

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 987
  • Karma: 140
Don't worry, because as an admin, I have the details.

All errors you have, such as this one is logged and I can check it properly.
You even do not need anymore to tell to me because I recieve by mail all notifications of such errors.

For instance, this is now fixed already
Coding is now a piece of cake
The administrator has disabled public write access.
Time to create page: 0.058 seconds

Get Started