Skip to Content

Changes for page ERPrototaculous

Last modified by Ravi Mendis on 2010/11/18 05:07
From version 152.1
edited by Ravi Mendis
on 2009/07/20 08:15
Change comment: There is no comment for this version
To version 156.1
edited by Ravi Mendis
on 2009/07/20 08:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -87,9 +87,9 @@
87 87  In ERPrototaculous you may still have typical WebObjects forms (i.e WOForm) as well as use ajax forms (i.e **AjaxUpdaterForm**).
88 88  They behave differently in that an AjaxUpdaterForm will update the contents of a container as opposed to the entire page.
89 89  
90 -{{warning title="Name your form controls!"}}
90 +{{warning title="Warning"}}
91 91  
92 -You must name your form controls, otherwise under certain circumstances Prototype (ajax) form submission will break.
92 +You must *name your form controls*, otherwise under certain circumstances Prototype (ajax) form submission will break.
93 93  
94 94  {{/warning}}
95 95  
... ... @@ -120,7 +120,7 @@
120 120  So you should make sure the actions in ERPrototaculous (or AjaxUpdaterButton and AjaxRequestButton) return the proper page fragment as opposed to the entire page.
121 121  This breaks with WO-tradition, so this is where you need to be careful.
122 122  
123 -{{note title="Actions"}}
123 +{{note title="Note"}}
124 124  
125 125  ERPrototaculous actions *differ* from Ajax.framework actions - _They must return only the page fragment_.
126 126