Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC:

Better Error reporting 17 May 2015 15:08 #13035

  • MorganL
  • MorganL's Avatar Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
  • Posts: 438
  • Thank you received: 53
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

Please Log in or Create an account to join the conversation.

Better Error reporting 18 May 2015 07:21 #13044

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
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

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.072 seconds

The j-cook project is one of the best of its kind and it is nice that we all try to contribute in little ways to make life easy for each other.

vlemos (Forum)  

Get Started