For your administration:

One step in recreation of the bug was missing :

3A: put a value in the required field.

The issue is logged as: http://jira.magnolia-cms.com/browse/MAGNOLIA-3245

Regards, Bert
________________________________
Van: [email protected] [[email protected]] namens 
Bert Leunis [[email protected]]
Verzonden: maandag 5 juli 2010 14:37
Aan: [email protected]
Onderwerp: [magnolia-user] bug in saving dialogs after making an required 
field-error?


Hello Magnolians,



We experience some unexpected behaviour when creating paragraphs using a 
magnolia dialog. This is the scenario, that I was able to follow on the 
demoauthor-site of magnolia:



1. click on the New teasers button on the homepage.
2. do not fill in the required field, but click save
3. an alert is given about the required field
4. now save the dialog.
5. result: the teaser paragraph is NOT shown. :-(



Cause: the mgnl:template variable in the MetaData of that node is empty. The 
first time the dialog is created, the paragraph name is in the url: "... 
&mgnlParagraph=stkTeaser ...". The second time the parameters from the url are 
moved to hidden fields in the form. But this field is empty:



<input type="hidden" name="mgnlParagraph" id="mgnlParagraph" value="" />



This seems to be the problem. I guess this is a bug? We are at version 4.3.2, 
but maybe this already existed before this version?



It is a very inconvenient feature, especially when the required fields are on 
the second tab, where users do not spot them easily.



Regards from Bert


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

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

Reply via email to