I've also wondered about this and having a more convenient method built into
the code would be nice (unless I too have been missing it). As of now, I
simply add code to the end of index.php where all the debug code is printed
out. But something along the line of....
foreach DebugMessages as Msg
echo Msg;
would be nice to have included in the debug print out.
Regards,
Shaun.
On Tue, Aug 9, 2011 at 7:59 AM, development <[email protected]> wrote:
> Hello everybody****
>
> ** **
>
> I’m currently somewhat puzzled but is there a more convenient way to output
> debug messages than the following?****
>
> ** **
>
> // set debug message in your code****
>
> $oSmarty = oxUtilsView::getInstance()->getSmarty(); ****
>
> $oSmarty->_tpl_vars['my_debug_info'].="\My Debug info";****
>
> ** **
>
> // output debug in template****
>
> [{$my_debug_info}] ****
>
> ** **
>
> **è **http://www.oxid-esales.com/forum/showthread.php?t=2923****
>
> ** **
>
> I mean there’s a debug mode but can’t we developer’s use it to append our
> own debug messages?****
>
> ** **
>
> I’m thinking about a function like $debug->appendMsg($myDebugInfo) or
> something like that which appends my debug info to the debug data of OXID
> and is only shown when the debug is set > 0.****
>
> ** **
>
> Thanks****
>
> Marc****
>
> ** **
>
> *ORCA Services AG*
> Herrenmattstrasse 26
> CH-4132 Muttenz
> Office Basel: Aeschengraben 10, CH-4051 Basel****
>
> ****
>
> [email protected]
> T. +41 61 205 80 80****
>
> T. +41 61 205 80 73 (direkt)****
>
> F. +41 61 205 80 81****
>
>
> www.orca.ch, www.orca-services.ch****
>
> ****
>
> *"We convert your visitors into customers."*****
>
> ** **
>
> _______________________________________________
> dev-general mailing list
> [email protected]
> http://dir.gmane.org/gmane.comp.php.oxid.general
>
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
