Pre-Made Forms
KodHedz Software has created a few forms for use as templates for your own custom forms. These include a workflow and layout that will be compatible with most DotNetNuke Portals and include several standard forms to create things such as a New User, Role Registration, or New Portal Creation
New User – Default
This form represents the most basic fields and settings for New User Registration to a website. It includes the default fields that are used in the standard DotNetNuke registration control, as well as a textbox for comments. It is meant to be used as a template for your form construction.
New Portal – Default
This form represents the most basic fields and settings for New Portal Registration, where an anonymous or already registered user can sign up and create a portal with them as the administrator of that portal. There are a few extra fields for opting in for newsletters, and comments. It is meant to be used as a template for your form construction.
New Role – Default
This form represents the most basic fields and settings for New Role Registration, where an anonymous or registered user can be added to a security role within the portal. There are a few extra fields for opting in for newsletters, and comments. It is meant to be used as a template for your form construction.
New User - PayPal
This form represents the most basic fields and settings for New User Registration using a merchant account with PayPal to receive payments for subscriptions. It will create a new Registered User within your portal, and accept payment to the PayPal account that was set up within your portal.
New Portal - PayPal
This form represents the most basic fields and settings for the New Portal Registration process using a merchant account with PayPal to receive payments for subscriptions. It will create a new Registered User within your portal, create a new portal with the new user as admin of the new portal, and accept payment for this to the PayPal account that was setup within your portal.
Ready to Go Portal
This form is included as an example of how to use form associations to call a custom control to handle post-processing after the form is posted. For any custom form type, you will need to create a custom control and install it as if it were a module or skin object (skin objects cannot install SQL scripts, where as modules can install SQL scripts). In this case, you would need to have the KHZ.PortalDuplicator Module installed, and have created at least one template of a portal by using that module. You can request a trial copy of the Portal Duplicator at WWW.KODHEDZ.COM This process creates a portal using a template file that you select while completing the form; the new portal includes content as well as the pages and modules from the template.