Developer forum

Forum » Development » Moving websites and Ecom to other solution : suggestions required.

Moving websites and Ecom to other solution : suggestions required.

Vilius Janulis
Reply

Hi,

 

Basically what I am trying to do is moving few websites (website with pages and paragraphs, templates and etc) from one solution to another one (have one website in there), along with two ecom shops with categories and products.

 

 

Can anyone give me some suggestions how this should be done theoretically at all ?

 

 

I mean i can not use websites module to export / import pages, so what it will have to be done manually ? since destination solution also has a website and i cant overwrite everything ? or use some kind of insert into/ update some tables with data integration module?

Regarding Ecom, we have a data integration module on both solutions, so theoretically we can move all shops , categories and products by using Ecom provider right ?

 

 

Some answers , tips and suggestion is very welcome :)

Thank you.

 

 

 


Replies

 
Morten Snedker
Reply

Hi Vilius,

 

A backup of the database and restore to a new database..?

That is real-world, however, not theory.  :-)

 

Regards /Snedker

 
Vilius Janulis
Reply

"have one website in there" - that means that solution i have to move few websites to, has a website of its own, that has to be left alone. SO i cant just restore and overwrite ... :S and not really a way to merge them ..

Any more suggestions ? :)

 
Morten Bengtson
Reply

I'm also very interested in a solution to this problem. It has always been a major problem when working with DW. You cannot easily copy a website (or any other content) from one DW solution to another. Deploying changes from test to production is not an easy task either. With DW you need to do everything two or more times (create pages, paragraphs, items etc.)... manually. What we really need is some sort of package manager, but I don't know if that could ever work reliably in DW.

 
Morten Snedker
Reply

First off "website" should be defined. If a website is

- Area
- Page
- Paragraph
 

- then maybe a "WebsiteProvider" for Data Integration would cut it? With build-in logic to handle colliding IDs between existing table content and of that being imported.

Then, obviously there may be issues with users (page permissions), newsletters, hardcoded id's in templates etc, to consider. But that apart: would it be an idea worth persueing?

 

Regards /Snedker

 
Morten Bengtson
Reply

You can take a look at what other content management systems offer, like the Package Designer in Sitecore and the Package Creator in Umbraco ;-)

A WebsiteProvider for Data Integration could be useful in some scenarios, but I'm not sure that it would have the flexibility needed for this. Often we want to pick and choose a few pages (in different locations in the site tree), some related content and images, which we can then install or update on the other solution.

The auto-generated ids are definitely one of the main problems, which makes it difficult to "merge" data without any conflicts.

 
Vilius Janulis
Reply

Agree, it should be easier somehow to move things around :)

 
Remi Muller
Reply

Still very much appreciated. Have a look at this feature request and which links to related topics.

http://developer.dynamicweb-cms.com/forum.aspx?ThreadID=31479

 

 

You must be logged in to post in the forum