[jira] [Commented] (TAP5-2541) Error when saving upload

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade commented on TAP5-2541:
--------------------------------------

First of all, which version are you using? In the description, you say "5.4.0", but the "Affects version" field is set to "5.4.1".
Second, does this also occur in development mode? Debugging is usually easier in development mode as it disables JavaScript aggregation and compression.
As for the error, it looks as if you're using Prototype as the JavaScript infrastructure provider and something tries to fire an event but with an {{undefined}} event name.
I suggest running in development mode and setting a breakpoint in {{requirejs.onError}}. Then you can access the thrown error and analyze its stack.

> Error when saving upload
> ------------------------
>
>                 Key: TAP5-2541
>                 URL: https://issues.apache.org/jira/browse/TAP5-2541
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-upload
>    Affects Versions: 5.4.1
>            Reporter: Xavier Rasschaert
>
> Version: 5.4.0
> When I click the submit button to store the file the user selected in the upload component, I get the error below in the console:
> chrome: "core.js:21633 RequireJS error: require: Cannot read property 'include' of undefined"
> ie: RequireJS error: require: Unable to get property 'include' of undefined or null reference
> firefox:RequireJS error: require: eventName is undefined
> level/<() core.js:22308
> requirejs.onError() core.js:22337
> onError() core.js:547
> newContext/Module.prototype.check() core.js:896
> newContext/Module.prototype.enable() core.js:1160
> newContext/Module.prototype.init() core.js:784
> localRequire/<() core.js:1433
> The component functions correctly, but throws this error in the console. I find these types of errors in general not clear. If this is a mistake on my part, I don't find the error easy to debug.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)