I have a solution in french, which requires another language layer, everything has to be exported and translated. This is where I'm at a loss.
I need to export the metadata from my first language layer out of my solution, have it translated and then imported back into the solution.
I've considered the following:
- Manual method, which means that I have to go into each page (around 120 pages) and copy metadata out and into a bunch of documents. This would take me quite a bit of time.
- "Automatic" method, exporting the SQL database the solution is based on and simply translating that and then importing it again.
- Third method, maybe I have overlooked something, but if you have any solution to this problem and saving me quite a few workhours of copy pasting, I'm open to suggestions!
Looking forward to your answers!
Developer forum
E-mail notifications
Exporting meta data in the old Dynamicweb version (the one before DW 7)
Posted on 09/11/2009 16:44:03
Replies
Posted on 10/11/2009 16:23:17
The Import/Export module offers an activity for exporting pages to an XML file and importing from XML to pages. This could probably save you some time.
Posted on 10/11/2009 16:27:01
Yeah and it will undoubtedly, but it doesn't export the metadata, so I am trying to find another way of exporting the metadata.
Do you have any tips in regards to the metadata export?
Do you have any tips in regards to the metadata export?
Posted on 11/11/2009 08:47:01
Hi Henrik
Just a remark to your Automatic Method suggestion:
You can still use the Import/Export module, but you have to make a couple of custom activities for the module to import and export fields that are not supported in the standard version.
This way you can make an export activity that exports just what you need in a format you like, then make an import activity that imports the whole thing again when the meta data is translated.
You can make a little script to translate the page-ids into the new page-ids, setting the right area-id etc., before importing the translated data again.
- Lasse
Just a remark to your Automatic Method suggestion:
You can still use the Import/Export module, but you have to make a couple of custom activities for the module to import and export fields that are not supported in the standard version.
This way you can make an export activity that exports just what you need in a format you like, then make an import activity that imports the whole thing again when the meta data is translated.
You can make a little script to translate the page-ids into the new page-ids, setting the right area-id etc., before importing the translated data again.
- Lasse
Posted on 11/11/2009 09:40:07
Hey Lasse
Do you have any documentation or suggestion how I might do this? I haven't tried this before and I wouldn't know where to begin to be honest.
But it definitely sounds like what I'm looking for!
Do you have any documentation or suggestion how I might do this? I haven't tried this before and I wouldn't know where to begin to be honest.
But it definitely sounds like what I'm looking for!
Posted on 12/11/2009 10:09:50
Hi Henrik
The Import/Export custom activities are documented in our Extensibility Documentation.
http://engage.dynamicweb-cms.com/Development-200.aspx
Or direct link to the pdf:
http://engage.dynamicweb-cms.com/Admin/Public/DWSDownload.aspx?File=%2fFiles%2fFiler%2fDocumentation+portal%2fDynamicweb+CMS%2fDocumentation%2fDevelopment%2f(en-US)_Extensibility_API__Dynamicweb_eCommerce.pdf
- Lasse
The Import/Export custom activities are documented in our Extensibility Documentation.
http://engage.dynamicweb-cms.com/Development-200.aspx
Or direct link to the pdf:
http://engage.dynamicweb-cms.com/Admin/Public/DWSDownload.aspx?File=%2fFiles%2fFiler%2fDocumentation+portal%2fDynamicweb+CMS%2fDocumentation%2fDevelopment%2f(en-US)_Extensibility_API__Dynamicweb_eCommerce.pdf
- Lasse
You must be logged in to post in the forum