History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CRM-3000
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed/Completed
Priority: Major Major
Assignee: Donald A. Lobo
Reporter: David Greenberg
Votes: 0
Watchers: 0
Available Workflow Actions

Unclose Issue
Operations

If you were logged in you would be able to see more operations.
CiviCRM

Prevent reloads of new contribution, event registration, new membership, new relationship forms by Implementing dojo method to add custom fields to the form

Created: 17/Apr/08 12:33 AM   Updated: 06/Aug/08 03:25 AM
Component/s: Core CiviCRM
Affects Version/s: 2.0, 1.8, 1.9
Fix Version/s: 2.1

Time Tracking:
Not Specified

Verified for 2.1: Yes
Verified for 2.0: No


 Description  « Hide
Currently these forms reload when a "type" is selected - to allow us to retrieve and inject additional custom fields into the form based on the object type (e.g. a Participant with participant role of "Speaker" may have a set of custom fields associated with that type). The New Event Registration form reloads twice (once when Event is selected, and again when Participant Role is selected)
.
These reloads are confusing, slow down data entry and may cause loss of data entered in a field while page is reloading.

The new model should retrieve additional fields / properties via ajax w/o reloading the entire page.

Implement this interface for all the places, where we use custom data and reload the page.

 All   Comments   Work Log   Change History   FishEye      Sort Order:
David Greenberg - 24/Apr/08 10:08 PM
When implementing / testing the new method - verify that we handle the case where the form is submitted w/ formRule errors. (In 2.0, this causes problems - for example you can't change the Participant Role after a formRule error.)

Kurund Jalmi - 26/May/08 12:27 PM
- finally after lot of QA closing this issue, let me if we have missed anything..

kurund

Donald A. Lobo - 06/Aug/08 03:25 AM

Done a lot of testing in event registration, this is a pretty big issue to test comprehensively