[ 
https://issues.apache.org/jira/browse/COCOON-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906733#comment-13906733
 ] 

Francesco Chicchiriccò commented on COCOON-2342:
------------------------------------------------

Ok, I see the problem: I was confused by the fact that 

http://cocoon.zones.apache.org/cocoon21/samples/blocks/forms/do-multivalueWithSuggestion.flow
http://cocoon.zones.apache.org/cocoon21/samples/blocks/forms/do-multiValueDoubleList.flow

works fine: this is evidently because this bug was introduced in 2.1.12 while 
cocoon zone runs 2.1.12-dev.

> Apache license at the beginning cocoon's dojo widgets templates causes: 
> dojo.widget.Parse: error:
> -------------------------------------------------------------------------------------------------
>
>                 Key: COCOON-2342
>                 URL: https://issues.apache.org/jira/browse/COCOON-2342
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Forms
>    Affects Versions: 2.1.12, 2.1.13
>            Reporter: Reynaldo Porras
>            Assignee: Francesco Chicchiriccò
>             Fix For: 2.1.13
>
>         Attachments: COCOON-2342.patch
>
>
> Get cocoon from http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X 
> and test cocoon form examples, specifically "Cocoon multivalue editor with 
> suggestions" or  "Cocoon double-list multivalue widget ". You should see that 
> the widgets are not being displayed and in debug console of the browser 
> should appear a message like this "dojo.widget.Parse: error: "
> This issue is present in MultiValueDoubleList widget,  
> MultiValueEditorWithsuggestion, MultiValueEditor and InfoPopup.
> Issue is caused by the apache license header added to the template files of 
> those widgets.
> I found that moving the license header inside of the first html element of 
> the widget fixes the issue.
> Test on firefox 27.0 and google chrome 32.0.1700.107.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to