This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.
Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.
Before posting questions here you might want to review the developer documentation.
We want to create a Form Wizard Pro module that will produce up to 5 printed forms, ready for the user to print, sign, and mail in. We want to check a set of 5 checkboxes at the beginning of the form. Once the user makes these selections, then only questions appropriate to the user's choices will be visible to the user.
This isn't a problem. I am developing a little JavaScript module to place on a page under a Form Wizard module. It will not be visible to the user. When the user makes checkbox selections, it will scan the FW form and show/hide the appropriate questions. When the user has completed the form, then a custom form submission handler will generate the forms for download and printing.
The purpose of this is to make it so the user does not need to re-answer some of the same questions multiple times for these forms. Nor will users need to answer questions that are inappropriate to what they need.
Here's the question-- Once a form is developed and tested on a development system, is there a way to copy that FW form to the database running the live production web site? Or is it necessary to do all this development on a hidden page on the live server, because it can't be copied?
Thanks.
There is built in functionality to import and export complete form definitions or individual questions.
You would have to copy any feature settings manually and anything like custom javascript you would have to replicate in the new environment.