Exponentcms Exponent CMS → 2.2.0release-candidate

Comments and changes to this ticket

• 

  dleffler April 6th, 2013 @ 07:26 PM

  A big question is: do we revert to using expDefinableFields (which were only being used in eventregistration and did not work) or use the new forms controller in some ajax type fashion?

• 

  expNinja April 6th, 2013 @ 08:17 PM

  (from [11eaffd7d7bdf77f9ff22770da691e71fe2fe270]) Prep for addressing event registration 'show' view; revises slingbar menu structure with icons for ecom menu and moves manage definable fields to ecom menu since it's only used there [#981] https://github.com/exponentcms/exponent-cms/commit/11eaffd7d7bdf77f...

• 

  dleffler April 6th, 2013 @ 08:52 PM

  Note to self: it appears that expDefinableFields was implemented to replace the user_input_fields used in the product model for eventregistration and allow more than six and only text input fields

• 

  expNinja April 6th, 2013 @ 10:04 PM

  (from [a1997d46f2879c6aa025ce4c7c310956af208ed4]) Prep for addressing event registration 'show' view; fixes edit er options display toggling [#981] https://github.com/exponentcms/exponent-cms/commit/a1997d46f2879c6a...

• 

  expNinja April 7th, 2013 @ 12:35 AM

  (from [982fed2c6244b553d76864a5564cef91403e9de3]) Prep for addressing event registration 'show' view; revises store category popup menu to resemble page tree popup menu [#981] https://github.com/exponentcms/exponent-cms/commit/982fed2c6244b553...

• 

  expNinja April 7th, 2013 @ 01:02 AM

  (from [623529cc597ef26fdb2b0259cfd4edcec33f607f]) Prep for addressing event registration 'show' view; tixes to expDefinableFields tables to get them working again [#981] https://github.com/exponentcms/exponent-cms/commit/623529cc597ef26f...

• 

  expNinja April 9th, 2013 @ 11:26 AM

  (from [a26917a7c242281db9347b0f695f292dc7402853]) Initial work to get expDefineableFields working again (though they were never fully implemented and we may go with our new forms module) [#981] https://github.com/exponentcms/exponent-cms/commit/a26917a7c242281d...

• 

  dleffler April 11th, 2013 @ 11:57 AM

  Perhaps the disparity of purposes could best be filled by two separate 'show' views...however, the current multi-registration view stores its data in the eventregistration_registrants table (with all data fields serialized into a single field) and the complex form view (if using the forms modules) would presumably save its data in a separate forms table (each data field separate)

  As a note, the current programming structure only allows one expDefineableFields record to be stored per order (based on the only discriminator of the content_id holding an order_id) meaning if they are used, you would have to settle for single registration and checkout for each individual registration. This is unacceptable, esp. now that we have sitewide forms.

• 

  dleffler April 12th, 2013 @ 11:20 PM

  Perhaps the best 'all around' approach may be to activate/revert to a 'hasUserInputFields' to force it through displaying a 'addToCart' method/view which would display a form...either a generic one (name, phone, email) or a custom one (form designer/forms). The data would them be saved to either a revised eventregistration_registrant table (may change name to be able to upgrade existing data) or the forms save to database table.

• 

  dleffler April 26th, 2013 @ 01:00 AM

  • Title changed from “Feature request - Type of event registration 'show' view” to “Feature request - flexible event registration 'show' view”
  • Milestone set to “2.2.0release-candidate”

  Well, have settled on an implementation for both multiple & single registration both of which will use site 'forms' to design/manage controls (due to the many limitations of expDefinableFields at this point).

  Locally I already have replaced most of the multi-registration view with relying on an assoc. form instead of hard coding the controls/names within the view...though I still require updating the edit/view/delete registrants views to work with a forms table instead of a serialized eventregistration_registrants table (which is a good thing). This means the event registration data is now more generally available as form data.

• 

  dleffler April 26th, 2013 @ 01:59 AM

  FWIW, we now have 3 types of registrations to deal with:

  • multi-registrant (simple data)
  • single-registrant (complex data)
  • basic registration (no data)

  Just a reminder that options apply to EACH individual registered in that purchase, however, you can now add multiple purchases to the cart.

• 

  dleffler April 26th, 2013 @ 09:35 PM

  recent push added single/multi registration using site forms stored in form data table

• 

  dleffler April 26th, 2013 @ 10:03 PM

  • Tag changed from “event registration” to “event registration, ecommerce”
• 

  expNinja April 27th, 2013 @ 09:40 PM

  (from [885a128edfe53b9f449eeafa78c0fd47b3aa4745]) Fixes some issues with new event registration computations, esp in regards to events with NO form assigned (yes you can still use them as very simple purchases with only the name & quantity being stored) also reverts to accurate calculation of number registered instead of storing that data with the event itself [#981] https://github.com/exponentcms/exponent-cms/commit/885a128edfe53b9f...

• 

  expNinja April 28th, 2013 @ 12:02 AM

  (from [c093450f2e65a18653ba39de4547e8306988d093]) Fixes some anomalies with complex forms in muti-registration...though we don't limit number of controls, we strip out static text controls and add horizontal scrolling [#981] https://github.com/exponentcms/exponent-cms/commit/c093450f2e65a186...

• 

  expNinja April 28th, 2013 @ 04:00 AM

  (from [eee1befef13764aeadbd2b81dce7524a46d68d5e]) Now does better job of capturing customer name on guest checkout of non-form event registration [#981] https://github.com/exponentcms/exponent-cms/commit/eee1befef13764ae...

• 

  dleffler April 29th, 2013 @ 11:23 AM

  • State changed from “new” to “resolved”
• 

  expNinja April 29th, 2013 @ 03:45 PM

  (from [d0146e6cca0fff8ae125d9c70a9d7a5b71402152]) Updates store database sample to work with current code & fixes sample store files to be extracted correctly [#981] https://github.com/exponentcms/exponent-cms/commit/d0146e6cca0fff8a...

• 

  expNinja April 29th, 2013 @ 04:01 PM

  (from [0e353945a12cf35951a5c56ad260a7376c16d80d]) If checking out with $Zero cost, will not display billing calculators; fixes issues related to 'paid' status of order so we can view in event registration, but also update/change it within the order; [#981] [#734 state:resolved] https://github.com/exponentcms/exponent-cms/commit/0e353945a12cf359...