You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by "Anthony Carlucci (JIRA)" <ji...@apache.org> on 2012/08/22 16:27:42 UTC

[jira] [Resolved] (RAVE-768) OpenSocial Container Config has a hard-coded debug flag set to on

     [ https://issues.apache.org/jira/browse/RAVE-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anthony Carlucci resolved RAVE-768.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.15
    
> OpenSocial Container Config has a hard-coded debug flag set to on
> -----------------------------------------------------------------
>
>                 Key: RAVE-768
>                 URL: https://issues.apache.org/jira/browse/RAVE-768
>             Project: Rave
>          Issue Type: Improvement
>    Affects Versions: 0.14
>            Reporter: Anthony Carlucci
>            Assignee: Anthony Carlucci
>            Priority: Minor
>             Fix For: 0.15
>
>
> The OpenSocial container configuration has a hard-coded debug flag set to on:
> -------------------------------------
> rave_opensocial.js line 55
> -------------------------------------
> containerConfig[osapi.container.ContainerConfig.RENDER_DEBUG] = "1";
> This is forcing all JavaScript downloaded through Shindig (like features, etc) to always come back in debug mode.  We should tie this value in with the javaScriptDebugMode portal preference that we are using to control other JS within Rave so that admins can flip it dynamically.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira