View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003015 | Composr | catalogues | public | 2017-01-06 09:38 | 2017-01-08 23:23 |
| Reporter | Patrick Schmalstig | Assigned To | Chris Graham | ||
| Severity | Major-bug | ||||
| Status | closed | Resolution | won't fix | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0003015: Attachments do not work properly | ||||
| Description | Fields on catalogues that have attachment support do not work properly for two reasons: 1. Let's say there are three fields with attachment support. What happens is in the first field's attachments, attachment #1 will properly render, but will have one attachment box for each field supporting attachments. So if there are three fields, attachment #1 will have three upload fields. The rest of the fields with attachment support will only have one upload box for attachment #1, but it is not properly rendered; it is rendered by the browser and not Composr's CSS. 2. Attachments flat out don't work. Trying to submit a catalogue entry with any attachments results in an error saying wait for the files to be uploaded, even if all the files have already uploaded. | ||||
| Steps To Reproduce | Reproducing this bug... if I upload absolutely no attachments, the catalogue entry submits. If I have any attachments, it will fail saying I need to wait for the files to upload, which they've already uploaded. | ||||
| Tags | No tags attached. | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
| related to | 0003022 | non-assigned | Allow multiple posting fields per form |
|
|
What web browser? I just did a test in Chrome trying to reproduce '2' and it was okay. |
|
|
Ok, I'll take '2' as a problem that happens if you have multiple posting fields, even if just filling the first one in. I tested in your 'journals' catalogue on your site (which has just a single field) and it worked fine for me. Unfortunately we can't support multiple posting fields, which is a limitation I forgot to document / enforce. It would be really complex to do that. I've added a new issue for it. In the next RC I'll make it so it won't break, just the additional posting fields will behave like long trans fields. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-01-06 09:38 | Patrick Schmalstig | New Issue | |
| 2017-01-08 22:47 | Chris Graham | Note Added: 0004674 | |
| 2017-01-08 23:14 | Chris Graham | Relationship added | related to 0003022 |
| 2017-01-08 23:23 | Chris Graham | Note Added: 0004676 | |
| 2017-01-08 23:23 | Chris Graham | Status | non-assigned => closed |
| 2017-01-08 23:23 | Chris Graham | Assigned To | => Chris Graham |
| 2017-01-08 23:23 | Chris Graham | Resolution | open => won't fix |
