7fd062814d
Currently, modifying existing orders will recalculate values if exchange rate has changed, which destroys previous data (our use case is just to modify Planning value fields). Since fields also have onChange event which also triggers caclNeworderTotal, onload event seems redundant. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> Signed-off-by: Chris Cormack <chrisc@catalyst.net.nz> |
||
|---|---|---|
| .. | ||
| acqui-home.tmpl | ||
| addorderiso2709.tmpl | ||
| ajax.tmpl | ||
| basket.tmpl | ||
| basketgroup.tmpl | ||
| basketheader.tmpl | ||
| booksellers.tmpl | ||
| histsearch.tmpl | ||
| lateorders.tmpl | ||
| neworderbiblio.tmpl | ||
| neworderempty.tmpl | ||
| newordersuggestion.tmpl | ||
| orderreceive.tmpl | ||
| parcel.tmpl | ||
| parcels.tmpl | ||
| supplier.tmpl | ||
| uncertainprice.tmpl | ||
| z3950_search.tmpl | ||