This document contains the steps necessary to create a new webinitiative based on an existing one. This means that the same presentations and forms will be available to the new webinitiative as in the source webinitiative. Pages may also be copied if wanted.
Creating the webinitiative
- Add the backend and frontend hostnames to the configuration.xml using the (configuration.xml generator) and deploy the changes.
- Copy the "static" directory (containing e.g. the "static", "upload" and "upload_mm" directories).
- Remove the contents from the directories "upload" and "upload_mm".
- Use the wizard to create a new webinitiative: Configure > Web Initiative Configuration, Select website: <New website>
Adjustments after creation
- Go to the setup tool (http://WEBSITE:PORT/web/setup) and to the section where the settings of the new webinitiative are to be found.
- Remove all references to the copied webinitiative under "backend_server_alias" and "frontend_server_alias"
- Copy the "frontend_hostname" to the "frontend_server_alias" (might not necessary...)
- Go to "Configure > Web Initiative Configuration" and select the new webinitiative in the drop-down at the top
- Tab "General": Set the "Default presentation" to the same value as the source webinitiative.
- Tab "Functionalities": Copy all settings from the source webinitiative.
Content export
It must be decided for each project exactly which parts need to be copied using export/import. This section gives you a picture of parts which in most cases should be copied and some parts which you should not copy.
- Go to the tab "Content export" in the setup-tool
- Select the source webinitiative
The following parts should in most cases be exported:
- Presentations (This is actually means the presentation variants for that presentation will be copied.)
- Forms:
- Form categories
- Form models
- Form instances
- Rules (meaning "Form rules")
- Pages: If wanted some (or all) pages may be exported and imported.
- Page sections (meaning "Blocks" (dutch: "inzetten"), not "Page versions"): (Even if no pages are exported, there are often page headings/footers and such that should be copied)
- Page sections
- Page section labels
- Personalizations
- Link models
- Queries?
The following part should not be exported:
- Forms
- Handler definitions: These are shared between the different webinitiatives. Exporting and importing these means they will occur double.
Content import
Before the import
- If pages are to be imported: The exported pages are placed in the new page-tree based on the page title of the parent page. Create pages with identical titles (and navigation titles) as the parent pages of the exported pages. (Otherwise the imported pages will be placed under "Orphan pages".)
- If forms using resources are to be imported (e.g. login related forms): The following steps ensures the new rules will be connected to resources owned by the new webinitiative in place of the original one. Otherwise it will work after the import, but the resource connections may be lost later when saving any form rule.
- Check which resources are used in all form rules to be exported. (Usually only one or two. Maybe "wuwebusers".)
- Create these resources based on the original webinitiative. (You can also skip the previous step and copy them all.)
- Temporarily rename the resource "values" in the original webinitiative.
Running the import
- Go to the tab "Content import" in the setup-tool
- Select the new webinitiative, select the exported file and start the import.
- Overview page: Check if the overview page makes sense. Ensure Presentations and Query Types will be overwritten.
Changes after the import
- Form resources: Put the original "values" back in the resources of the original webinitiative.
- Check also the resources at the rules in the new webinitiative
- Page parts: These need to created by hand!** Go to Format > Presentation, tab "Page parts"
- Create page parts available in the original webinitiative
- Pages:
- Check if imported pages are to be found under "Orphan pages".
- The order of imported pages might be other than the original. Adjust this if needed.
Possible problems in the original webinitiative
- Redirects on redirect pages may have been lost.