Updating existing Web Forms using an import?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2007 05:14 AM
Hi,
Is it possible to update existing Web Forms in Alfresco WCM using an Alfresco import?
I have tried the following:
1/ On the Alfresco source server create an Export of the Web Forms Space.
2/ On the Alfresco target server try to import the resulting .acp file in the Web Forms Space.
3/ I get the error:
This is correct: I already have a Web Form with the name "servicemenu".
What I would want Alfresco to do here is to update my existing servicemenu Web Form with the new one in the import.
Any thoughts on how to accomplish this?
A possible "workaround" I see is the following:
- remove the servicemenu Web Form from the .acp file
- update the servicemenu's .xsd and .xsl (our template) files by hand using the CIFS interfacce
- import the remaining Web Forms using the .acp file
Doing this for every export/import action we want to do will take a lot of time however..
regards,
Edgar
Is it possible to update existing Web Forms in Alfresco WCM using an Alfresco import?
I have tried the following:
1/ On the Alfresco source server create an Export of the Web Forms Space.
2/ On the Alfresco target server try to import the resulting .acp file in the Web Forms Space.
3/ I get the error:
Failed to execute import: org.alfresco.service.cmr.view.ImporterException: Failed to import package at line 1545; column 20 due to error: Duplicate child name not allowed: servicemenu
This is correct: I already have a Web Form with the name "servicemenu".
What I would want Alfresco to do here is to update my existing servicemenu Web Form with the new one in the import.
Any thoughts on how to accomplish this?
A possible "workaround" I see is the following:
- remove the servicemenu Web Form from the .acp file
- update the servicemenu's .xsd and .xsl (our template) files by hand using the CIFS interfacce
- import the remaining Web Forms using the .acp file
Doing this for every export/import action we want to do will take a lot of time however..
regards,
Edgar
Labels:
- Labels:
-
Archive
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2007 05:40 AM
I have now done my initial import of Web Forms by removing the "servicemenu" Web From from the export .acp file as follows:
1- rename the .acp file to a .zip file for easier editing
2- in the zip archive open the top-level .xml file defining the contents of the export
3- in this file remove the <wcm:formfolder> as well as the <view:reference> elements for the servicemenu Web Form
4- rename the .zip file to .acp
5- perform the import
Now, this works fine.
However: how I am to go about importing the next .acp export where I want to update all of the Web Forms I have just imported?
I think the best way for now is to create a snapshot of the CIFS folder defining the Web Forms and then to update the .xsd and .xsl files by hand on my target server again using the CIFS interface?
cheers,
Edgar
1- rename the .acp file to a .zip file for easier editing
2- in the zip archive open the top-level .xml file defining the contents of the export
3- in this file remove the <wcm:formfolder> as well as the <view:reference> elements for the servicemenu Web Form
4- rename the .zip file to .acp
5- perform the import
Now, this works fine.
However: how I am to go about importing the next .acp export where I want to update all of the Web Forms I have just imported?
I think the best way for now is to create a snapshot of the CIFS folder defining the Web Forms and then to update the .xsd and .xsl files by hand on my target server again using the CIFS interface?
cheers,
Edgar
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2007 10:11 AM
Edgar -
This is probably the best way to handle for now. Alternatively, you can use the Clipboard to Copy a Web Form into a dedicated Web Project, which with 2.0.1 you've configured to deploy to your 2nd server. Once replicated to the 2nd server, you can again use the Clipboard to paste the replicated Web Form to the Data Dictionary.
Cut | Copy | Paste works on both files and folders bi-directionally, and carries with it metadata. Similarly, deployment ensure replication of both content and metadata as well. Thus, using a combination could save the hassle of manually pushing and re-created forms on your target server.
This is an additional area of clean-up for us (change migration from a dev instance of Alfresco to a production instance of Alfresco).
Kevin
This is probably the best way to handle for now. Alternatively, you can use the Clipboard to Copy a Web Form into a dedicated Web Project, which with 2.0.1 you've configured to deploy to your 2nd server. Once replicated to the 2nd server, you can again use the Clipboard to paste the replicated Web Form to the Data Dictionary.
Cut | Copy | Paste works on both files and folders bi-directionally, and carries with it metadata. Similarly, deployment ensure replication of both content and metadata as well. Thus, using a combination could save the hassle of manually pushing and re-created forms on your target server.
This is an additional area of clean-up for us (change migration from a dev instance of Alfresco to a production instance of Alfresco).
Kevin
