Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow explicit wrapping of logging data #30

Closed
GoogleCodeExporter opened this issue Jun 24, 2015 · 17 comments
Closed

Allow explicit wrapping of logging data #30

GoogleCodeExporter opened this issue Jun 24, 2015 · 17 comments

Comments

@GoogleCodeExporter
Copy link

Log messages should support wrapping on a newline (\n) character in all
standard log styles as well as tables.

Original issue reported on code.google.com by christop...@gmail.com on 13 Sep 2008 at 8:38

@GoogleCodeExporter
Copy link
Author

Original comment by christop...@gmail.com on 20 Sep 2008 at 3:14

  • Added labels: release-0.1.3

@GoogleCodeExporter
Copy link
Author

Original comment by christop...@gmail.com on 22 Sep 2008 at 8:54

  • Added labels: release-0.2
  • Removed labels: release-0.1.3

@GoogleCodeExporter
Copy link
Author

Fixed in 0.2 BETA

Original comment by christop...@gmail.com on 1 Oct 2008 at 6:33

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

Original comment by christ...@christophdorn.com on 22 Oct 2008 at 5:12

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

This doesn't appear to be fixed.  I'm running 0.2.0 in FF and the same on the 
server.
 Trying with ->info and ->log() with \r\n, \r or \n, none of them will produce a
newline in the output on FirePHP/Firebug.

Original comment by clint.priest on 23 Oct 2008 at 3:28

1 similar comment
@GoogleCodeExporter
Copy link
Author

This doesn't appear to be fixed.  I'm running 0.2.0 in FF and the same on the 
server.
 Trying with ->info and ->log() with \r\n, \r or \n, none of them will produce a
newline in the output on FirePHP/Firebug.

Original comment by clint.priest on 23 Oct 2008 at 3:28

@GoogleCodeExporter
Copy link
Author

After more testing it appears that this is not possible at this time. Not sure 
why I
had marked it as fixed.

Original comment by christ...@christophdorn.com on 23 Oct 2008 at 8:20

  • Changed state: Accepted
  • Removed labels: release-0.2

@GoogleCodeExporter
Copy link
Author

http://n2.nabble.com/Use-%5Cr%5Cn-in-FirePHP%3A%3ATABLE-td1086966.html#a1678152

I wrote a small patch to RequestProcessor.js for supporting newline inside 
table cells.
It split cells content in line on "\n" character and display them using a "<br 
/>"
hmtl tag.

I attach a diff file so, if you want, you can patch official sources in this way

Original comment by christ...@christophdorn.com on 19 Dec 2008 at 6:46

Attachments:

@GoogleCodeExporter
Copy link
Author

Hi, 
I've tried patching the file but I got this error:

The patch seems to be outdated! The line 
TR({},
and the patchline
}
do not match. 

I'd really appreciate it if you could attach the patched file. 

Thanks

Original comment by sola.aj...@gmail.com on 14 Feb 2009 at 4:55

@GoogleCodeExporter
Copy link
Author

Original comment by christ...@christophdorn.com on 14 Apr 2009 at 5:59

  • Added labels: Milestone-Extension-1.0

@GoogleCodeExporter
Copy link
Author

Original comment by christ...@christophdorn.com on 14 Apr 2009 at 6:04

  • Added labels: Milestone-1.0

@GoogleCodeExporter
Copy link
Author

Original comment by christ...@christophdorn.com on 14 Apr 2009 at 6:04

  • Removed labels: Milestone-Extension-1.0

@GoogleCodeExporter
Copy link
Author

Is it planned to be fixed? This makes firePHP not usable as logger in our team.

Original comment by Ged...@gmail.com on 22 Jul 2010 at 9:04

@GoogleCodeExporter
Copy link
Author

This will be fixed in FireConsole: http://www.fireconsole.org/

In the meantime you could see if it works in FirePHP Companion. If not I can 
make a fix there right away.

http://companion.firephp.org/

Original comment by christ...@christophdorn.com on 22 Jul 2010 at 10:13

  • Added labels: Companion-Done, FireConsole-Planned

@GoogleCodeExporter
Copy link
Author

I would be happy to see this change in FirePHP plugin, would it be difficult?

Original comment by marcinfi...@gmail.com on 27 Jul 2010 at 1:53

@GoogleCodeExporter
Copy link
Author

Yes, it is difficult, which is why it will not make it into the FirePHP 
extension. It will be implemented in FireConsole which will replace the FirePHP 
extension later this year.

Original comment by christ...@christophdorn.com on 27 Jul 2010 at 4:29

@GoogleCodeExporter
Copy link
Author

See: https://github.com/firephp/firephp-extension/issues/4

Original comment by christ...@christophdorn.com on 6 Apr 2012 at 9:31

  • Changed state: Moved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant