[
https://issues.apache.org/jira/browse/TAPESTRY-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAPESTRY-2453:
-------------------------------------------
Priority: Minor (was: Major)
The workaround is to ensure that the Form is always using the multipart
encoding type (even if it does not contain a file upload). This could be
accomplished with a simple mixin to the form. Dynamically managing the enctype
on the client-side is possible in theory, but would be a bit on the unwieldy
side.
> Form enctype is not updated when an Upload component is injected via
> FormInjector / AjaxFormLoop
> ------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2453
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2453
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.13
> Reporter: Ognen Ivanovski
> Priority: Minor
>
> The following snipped describes the situation:
> <t:form>
> <ul>
> <li t:id="loop" t:type="AjaxFormLoop" source="uploads"
> value="currentValue" encoder="encoder">
> <t:submitnotifier>
> <t:upload value="currentValue.uploadedFile" />
> <t:removerowlink>remove</t:removerowlink>
> </t:submitnotifier>
> <t:parameter name="addRow">
> <t:addrowlink>Add a row</t:addrowlink>
> </t:parameter>
> </li>
> </ul>
> <t:submit>Submit</t:submit>
> </t:form>
> Adding a row to this form causes an addition of a Upload component. However
> when doing so the enctype of the form tag should be updated to
> "multipart/form-data". However this does not happen. I suppose that reverting
> the enctype back to normal when the last upload component is removed doesn't
> happen too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
