[MAGNOLIA-3872] Creating new custom data fails Created: 27/Oct/11 Updated: 17/Nov/11 Resolved: 17/Nov/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 4.2.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Derivative Partners Research AG | Assignee: | Philipp Bärfuss |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows Server 2008 R2 |
||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Description |
|
In our installation of Magnolia we have a few sets of custom data - which we can add, delete and edit via the Magnolia Admin interface. The data that can be entered in the form is a mixture of free text fields, radio buttons, check boxes and file upload fields. Editing this data works fine, changes are stored and available on the public page, including new images. Our current work around to get a new data entry is to copy an existing entry and editing all the data. Annoying, but it works. |