We forgive you ;-)
Have a nice one!
On Mon, Jul 25, 2011 at 6:58 PM, krazykev wrote:
>
> Don't pin that on me ;-) I should have spotted that first - how many times do
> I tell people to read there code carefully! Oh well - sure it won't be
> last blunder :)
>
>
> Christian grobmeier wrote:
>>
Don't pin that on me ;-) I should have spotted that first - how many times do
I tell people to read there code carefully! Oh well - sure it won't be
last blunder :)
Christian grobmeier wrote:
>
> Kev found a bug and Ivan gets out of his holidays ;-)
>
>
> On Mon, Jul 25, 2011 at 6:48 PM,
glad it worked out for you know!
We'll fix the documentation
Cheers!
On Mon, Jul 25, 2011 at 6:37 PM, krazykev wrote:
>
> YOU WON'T BELIEVE THIS!!
>
> The XML is posted isn't complete. There was in fact an error. I was
> using:-
>
>
>
>
>
>
>
> Seen the mistake
>
> There
Kev found a bug and Ivan gets out of his holidays ;-)
On Mon, Jul 25, 2011 at 6:48 PM, Ivan Habunek wrote:
> Our documentation has a bug. :)
>
> Thanks for reporting this, Kev. We'll fix the docs.
>
> Also, we're working on a new and improved configuration parser which will
> report any errors p
Our documentation has a bug. :)
Thanks for reporting this, Kev. We'll fix the docs.
Also, we're working on a new and improved configuration parser which will
report any errors properly instead of failing silently like what happened to
you.
Regards,
Ivan
On 25 July 2011 18:41, krazykev wrote:
It seems this site parses messages it seems to hide my param tags. For
completeness, the XML I was using was:-
krazykev wrote:
>
> YOU WON'T BELIEVE THIS!!
>
> The XML is posted isn't complete. There was in fact an error. I was
> using:-
>
>
YOU WON'T BELIEVE THIS!!
The XML is posted isn't complete. There was in fact an error. I was
using:-
Seen the mistake
There is no closing slash after logger.txt - it shoud be:-
In my defence this error also exists in the documentation
http://lo
Yes - the xml I posted is complete.
Not sure about your link - I am only changing the order of the appenders.
All apenders still appear before the logger. I should have made that clear.
I am still working on this - so far it appears that when parsing the
FileAppender xml, for some reason the c
> Your print_r trick stops the php loading.
wtf - the xml you posted was complete?
> What I have noticed though is that the log4php parser stops parsing after
> the file appender section! So if this appender is last there could be the 2
> stdout out appenders. If its first there won't be any.
Your print_r trick stops the php loading.
What I have noticed though is that the log4php parser stops parsing after
the file appender section! So if this appender is last there could be the 2
stdout out appenders. If its first there won't be any. Still going through
the log4php code.
Christ
> You are right, the echo statement isn't code good. BUt it works. I have
> changed it though and it doesn't make a difference.
OK :-)
Yes, you can try:
print_r( Logger::getAllAppenders() );
This should print all configurated appenders. If there is nothing
returned, we need to look on your xm
You are right, the echo statement isn't code good. BUt it works. I have
changed it though and it doesn't make a difference. I am currently going
through the log4php code to see if I can spot the problem.
Any other ideas?
Christian grobmeier wrote:
>
> Hi
>
> did you realize you pasted:
> e
Hi
did you realize you pasted:
echo Hello World;
while it should be
echo "Hello World";
Can you check if this is truth?
Cheers
On Mon, Jul 25, 2011 at 5:49 PM, krazykev wrote:
>
> Thanks Christian,
>
> nice ideas but no luck. The changes to the config file made no difference.
> And the erro
Thanks Christian,
nice ideas but no luck. The changes to the config file made no difference.
And the error reporting line doesn't add any errors to stdout (or should I
be looking elsewhere)?
Kev
Christian grobmeier wrote:
>
> Hey Kev,
>
> did you try this:
>
>
>
>
>
>
>
>
Hey Kev,
did you try this:
Replace file value with your log location. Maybe its some configuration missing.
And you can try to call this in the first line of your script:
error_reporting(E_ALL);
This should bring up any errors, if any.
Let me know what the outcome is
Cheers
15 matches
Mail list logo
