How to log to vui log / where to find vui log results?

Hi,

In the documentation for the sample v8 custom widget, it has this customization:

if ( vui.log.isDebug() ) { vui.log.debug("Getting widget value for: " + this.id); }

Can someone tell me how to enable debugging for the vui widget? And, where should I expect to see the output?

If this is documented somewhere and I just missed it, can you point me to it?

Thanks,

Eric

Find more posts tagged with

Comments

Hi Eric !

To set the log level, you have to execute the following stement form the firebug console

vui.log.level=1;

Once you have done it if you execute vui.log.isDebug() you should get true as a result.

Debug statements will be seen in the firebug console output.

ciao

Mario

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Friday, March 28, 2014 3:32 PM
To: eLink Recipient
Subject: How to log to vui log / where to find vui log results?

How to log to vui log / where to find vui log results?

Posted byeborisow@us.imshealth.com (Borisow, Eric) On 03/28/2014 10:25 AM

Hi,

In the documentation for the sample v8 custom widget, it has this customization:

if ( vui.log.isDebug() ) { vui.log.debug("Getting widget value for: " + this.id); }

Can someone tell me how to enable debugging for the vui widget? And, where should I expect to see the output?

If this is documented somewhere and I just missed it, can you point me to it?

Thanks,

Eric

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Content Server

Thanks for that Mario. Sorry, I'm just getting back to this. When I use those functions, it returns true and all that good stuff. However, if I try to send a message to debug, I get:

TypeError: vui.log.debug is not a function

vui.log.debug("Getting relator widget dirty value for: "+this.id);

Thanks,

Eric

why don't you just use console.debug ?

Mario

Yeah, thanks Mario. I guess that's what we'll do. I guess we were just thinking that it would provide some type of common logging mechanism. And console.log causes errors on old IE browsers, in case we wanted to leave the log messages in there. It's odd that it didn't work. And, also that there isn't any documentation on it.

Regards,

Eric