is not used any more and exists only for history. Post new tickets on the Github account. n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.

Opened 13 years ago

Closed 13 years ago

#638 closed enhancement (fixed)

option to log the url associated with an error

Reported by: bibo Owned by: bibo
Priority: normal Milestone: Jelix 1.1 beta 1
Component: jelix:core Version: trunk
Severity: normal Keywords:
Cc: Blocked By:
Blocking: Documentation needed: no
Hosting Provider: Php version:


IT would be sometime usefull, and i mean really usefull to know which url caused an error.

Imagine an 'ill-formed content' lost in a myriad of similar content. It is a waste of time to search and find the ill one. Having the url would mean such a search become a breeze.

Attachments (2)

jelix-trunk-#638.patch (1.3 KB) - added by bibo 13 years ago.
support of %url% in messageLogFormat
jelix-trunk-#638.2.patch (1.5 KB) - added by bibo 13 years ago.
some nit corrections

Download all attachments as: .zip

Change History (7)

Changed 13 years ago by bibo

support of %url% in messageLogFormat

comment:1 Changed 13 years ago by bibo

  • Owner changed from laurentj to bibo
  • Status changed from new to assigned

Patch attached adds support of %url% to messageLogFormat. I've chosen to expose all request params instead of the url string. I think it is more useful to bug hunting.

Just a nit, I've used var_export but as a result message is multi-lined. Let me know if it's a problem or not.

comment:2 Changed 13 years ago by bibo

  • review set to review?

Changed 13 years ago by bibo

some nit corrections

comment:3 Changed 13 years ago by bballizlife

I'll give you a "review+", but i don't know if i'm allowed to do so ;)

comment:4 Changed 13 years ago by laurentj

  • Milestone set to Jelix 1.1 beta 1
  • review changed from review? to review+

It's ok for me.

comment:5 Changed 13 years ago by bibo

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.