
Upgrade forms module to controller
Reported by dleffler | April 29th, 2011 @ 03:11 PM | in 2.1.1 (closed)
Forms module needs to be upgraded from old school (1.0) to 2.0 controller.
- Complete initial implementation
- In-place migration for 1.0 data (forms & forms data)
- Handle website upgrades from earlier version with 1.0 files
Comments and changes to this ticket
-
dleffler September 25th, 2012 @ 07:52 PM
Would be nice to change the drop-down list of controls into a tool panel on one side like phpFormGen phpformgen.sourceforge.net or something similar.
-
dleffler September 26th, 2012 @ 06:20 PM
- Assigned user set to dleffler
- Milestone order changed from 1 to 0
-
dleffler September 29th, 2012 @ 02:15 AM
- Milestone order changed from 32 to 0
Note to self
- showall should show all form records (data_view)
- show should show individual record
- show_form would show entry form (Default)
-
dleffler November 21st, 2012 @ 08:56 PM
- Milestone changed from 2.1.0 to 2.1.1
- Milestone order changed from 22 to 0
-
dleffler January 11th, 2013 @ 01:13 AM
abstract thinking...since we can store all module specific settings within an expConfig object...
- the form data would be system-wide and not assigned to a
module, kinda like expFile
- form controls would define the form data and be linked to the form
- form data (if stored in the db) would also be linked to the form
- we'd have a forms manager to see all the forms in the system, create new forms, etc..
- traditional forms & reports would be consolidated into
module views with input (form) or output (report) as actions/views
- you'd have to select a form to attach to the module, but you could have input on one page and output on another page all from the same set of data and with admin assigned permissions, e.g., a 'contact' form would allow basic user input, but a contact list might only allow 'editor' input
- we would have 'showall' views (reports view_data) with all records, but in more than just tabular format...something like a user defined portfolio type display, e.g., more than just a title/body fields for each item...think along the lines of an address listing
- we would have 'show' views (reports view_record) with optional pagination to other records and filtering/search
- the form data would be system-wide and not assigned to a
module, kinda like expFile
-
dleffler January 11th, 2013 @ 02:11 PM
As a note or update...I have the basics of a new form controller working locally, though I'm not sure it will make it into the next release.
- we'll ship the old and new form modules in the first release of forms 2.0
- we'll deprecate (remove) the old form module in the release after that (providing forms 2.0 is successful)
- we'll provide an upgrade/migration path to 2.0 from the old module (a given)
- the initial release will at least provide all the features of the current forms module
- the additional features (wish list) may be integrated later
-
dleffler January 13th, 2013 @ 12:25 PM
Locally, I have have much of the 1.0 forms converted to 2.0 with the following still needing some initial integration:
- edit control/save control/delete control (on the form designer)
- confirm submission/save submission (on the enter data/edit form views)
- append fields from existing form (on the form designer)
- method to restrict data entry and/or data viewing...likely this will be a checkbox in the module config (or form) which exits the showall/show methods early if set and other perms don't exists. e.g., we'll need conditional permissions enforcement INSIDE the method, NOT in the pre-render function.
While it would appear that these lack of method prevent forms 2.0 from working they are simply the last steps in the normal sequence of using forms, so they were save until later to integrate.
Have already added a 'display form by title' feature using a new 'sef_url' entry so that
- /forms/showall/title/name-of/form will display the site-wide form data in table format and
- /forms/show/title/name-of-form will display the site-wide form data entry view and
- /forms/show/title/name-of-form/id/1 will display the site-wide form data record
-
dleffler January 15th, 2013 @ 01:20 PM
Note to self: All 1.0 features implemented locally EXCEPT the append controls to forms. Still require the following:
- upgrade script to at least import existing forms/data into 2.0 format, though we'll also want to remove the old files/tables
- migration script
-
expNinja January 15th, 2013 @ 09:38 PM
(from [b8f7010fef6244a565450afad1acf257337d3470]) Initial commit of Forms module v2.0, includes all the features of the old school module except append form controls. A form is now site wide and must be attached to a module, but the commands are in the module view [#140] https://github.com/exponentcms/exponent-cms/commit/b8f7010fef6244a5...
-
expNinja January 17th, 2013 @ 01:56 PM
(from [05ce912d3b01a055a346a773798851902309fe46]) Adds 'placeholder' property to text controls, adds forms upgrade script (still need forms migration script) [#140] https://github.com/exponentcms/exponent-cms/commit/05ce912d3b01a055...
-
expNinja January 17th, 2013 @ 07:38 PM
(from [2231b6f5afd6988dfe57d9e80f82d253015a097f]) Fixes some display messages when form is not yet assigned, etc... [#140] https://github.com/exponentcms/exponent-cms/commit/2231b6f5afd6988d...
-
expNinja January 18th, 2013 @ 05:49 AM
(from [c036a28b16e06836e59ba6710d334d1122cc884f]) Fixes some anomalies with tabviews and adds new form control features to installation/upgrade correcting some anomalies there, and fixes a breakdown in the upgrade forms upgrade script [#140] https://github.com/exponentcms/exponent-cms/commit/c036a28b16e06836...
-
expNinja January 18th, 2013 @ 04:09 PM
(from [4d0310ca1cb948c43adfebc00b1d80e50c96e989]) Fixes upgrade_forms script to actually rename old form data table and account for bad forms in the container table, updates sample data for new forms module, fixes design form to allow re-ranking controls [#140] https://github.com/exponentcms/exponent-cms/commit/4d0310ca1cb948c4...
-
dleffler January 19th, 2013 @ 05:38 PM
As a note, we still lack a migration script which must migrate both formmodule and contactmodule
And the 'append form controls' feature which was present on the old formmodule...however we can now copy forms to create a duplicate shell to begin with.
-
expNinja January 26th, 2013 @ 05:20 AM
(from [be02e94488ddaf3eea44e866c37cc5c72efa7b9e]) Updates migration of 0.9x contactmodules into 2.0 forms (still lack formmodule to forms migration) [#140] https://github.com/exponentcms/exponent-cms/commit/be02e94488ddaf3e...
-
dleffler January 26th, 2013 @ 04:13 PM
migration script complete locally, awaiting testing before closure
-
expNinja January 26th, 2013 @ 09:47 PM
- State changed from open to resolved
(from [d87882112dc7942c4d998acacec3cb1d62253bbf]) Adds migration of 0.9x formmodule to forms, fixes minor issue w/ calendarmodule migration [#140 state:resolved] https://github.com/exponentcms/exponent-cms/commit/d87882112dc7942c...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS