Creating new custom data fails
------------------------------

                 Key: MAGNOLIA-3872
                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3872
             Project: Magnolia
          Issue Type: Bug
      Security Level: Public
          Components: admininterface
    Affects Versions: 4.2.4
         Environment: Windows Server 2008 R2
            Reporter: Derivative Partners Research AG
            Assignee: Philipp Bärfuss
            Priority: Major
         Attachments: magnolia-stacktrace.txt

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.
However, adding a new entry to one of these sets of data leads to an empty 
page. In the log files we can see a stack trace (relating to the templating kit 
and DAM). See attached file.
What is interesting, and important, to note as well here is that when opening 
an existing data entry everything works fine. This problem only occurs when 
attempting to add a completely new entry. Our investigations have not found 
anything conclusively wrong, merely that something has not been initialized 
correctly when it should've been.

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.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to