Latest nightly build issues

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

garpinc

When going to company home I get the following error

javax.faces.FacesException: Client-id : col10-lang is duplicated in the faces tree. Component : browse:col10-lang, path: {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /jsp/browse/browse.jsp][Class: javax.faces.component.html.HtmlForm,Id: browse][Class: org.alfresco.web.ui.common.component.UIPanel,Id: content-panel][Class: org.alfresco.web.ui.common.component.data.UIRichList,Id: contentRichList][Class: org.alfresco.web.ui.common.component.data.UIColumn,Id: col10][Class: javax.faces.component.html.HtmlOutputLabel,Id: col10-lang]}
caused by:
org.apache.jasper.JasperException: Client-id : col10-lang is duplicated in the faces tree. Component : browse:col10-lang, path: {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /jsp/browse/browse.jsp][Class: javax.faces.component.html.HtmlForm,Id: browse][Class: org.alfresco.web.ui.common.component.UIPanel,Id: content-panel][Class: org.alfresco.web.ui.common.component.data.UIRichList,Id: contentRichList][Class: org.alfresco.web.ui.common.component.data.UIColumn,Id: col10][Class: javax.faces.component.html.HtmlOutputLabel,Id: col10-lang]}
caused by:
java.lang.IllegalStateException: Client-id : col10-lang is duplicated in the faces tree. Component : browse:col10-lang, path: {Component-Path : [Class: javax.faces.component.UIViewRoot,ViewId: /jsp/browse/browse.jsp][Class: javax.faces.component.html.HtmlForm,Id: browse][Class: org.alfresco.web.ui.common.component.UIPanel,Id: content-panel][Class: org.alfresco.web.ui.common.component.data.UIRichList,Id: contentRichList][Class: org.alfresco.web.ui.common.component.data.UIColumn,Id: col10][Class: javax.faces.component.html.HtmlOutputLabel,Id: col10-lang]}‍‍‍‍‍

kevinr

Is that the latest? There was an issue with some contributed UI code that we integrated, it was fixed early last week.

Thanks,

Kevin