I looked at other bug reports but they don't have any closure. Perhaps I'll try my own.

Looking at your module's description and use case, it exactly fits into what I want. I started with a signel Drupal site, and then later decided to create a subsite. Now I want to migrate some of the content (blog entries, book) from my site to the subsite.

Both, my site (www.researchut.com) and the subsite (astrogem.researchut.com), are running Drupal 7. I exported the data types, blog (http://www.researchut.com/blog) and book(http://www.researchut.com/gemology) from the site.

Issue 1:
On my subsite, importing the data type "book" succeeds. But the actual content is not imported.
Actual node: http://www.researchut.com/gemology/amethyst
Imported node: http://astrogem.researchut.com/node/142

Issue 2:
On my subsite, when importing the data type "blog", it completly fails stating the following error message.

When the dataset was created the node content type was different from this site's node content type. Please manually compare the content type: blog
The Nodes dataset file 20131119_173258_nodes_blog.dataset was not imported.

Comments

riteshsarraf’s picture

riteshsarraf commented

Issue 1 is invalid. The entire content was imported. Just that on the subsite the content had to be edited and "Text Type" had to be selected as "Full HTML".

Issue 2 still applies.

bailey86’s picture

bailey86 commented

Issue 1.

This would (probably) not be needed if the content types are an exact match - make sure the fields are the same and have the text type set the same.

Issue 2.

The only reason I can think that the mismatch is being reported is that the blog content type has been modified. It may be possible to use the Features module to export the blog content type and import that content type into the new site. This should mean that the content types will be a decent match.

For further information it should be possible to modify the code to print out the content type objects and then compare them.

Cheers,

Kev B

riteshsarraf’s picture

riteshsarraf commented

Hello Kev,

For Issue 2, what do you mean when you say "has been modified" ??

The content type is 'blog'. The text input fed to blogs were depending on what WYSIWYG editor was used. It was a mix of TinyMCE and CKEditor.

Shouldn't that not be a concern? I mean, the actual content is nothing but just data which should be imported.

I understand why in Issue 1, the content was not displayed. But plainly erroring out is something I've not been able to understand.

Which source file do I modify to print the content type?

riteshsarraf’s picture

riteshsarraf commented

Okay!! Yes. It does have customized content type, as in, some taxonomy vocabs and a external module(AddThis)

bailey86’s picture

bailey86 commented

OK - so if you updated the blog which was being imported into does the import work?

The data can come into a content type which has extra fields - but not into a content type which does not have enough fields - because it would not know what to do with the data.

Please let me know the outcome.

Thanks,

Kev

Anonymous’s picture

Anonymous (not verified) commented

I am having the same issue as number 2. This is after I have just did a features import of the content type. The data and the content type HAVE NOT changed.

bailey86’s picture

bailey86 commented

The content type match check is quite strict. This is how you can check the mismatch:

https://drupal.org/comment/7463826#comment-7463826

And it looks like the features module adds extra info to the content type, and these might not match, and so have to be unset. Someone has posted their workaround here:
https://drupal.org/comment/7809689#comment-7809689

Let me know how you get on. It might be a relatively easy fix to allow for features. When I get chance I'll look into it.

riteshsarraf’s picture

riteshsarraf commented

@bailey86

That's what I thought too. And so I went and created the same fields (i.e. Taxonomy and AddThis). But still the import failed.

Anything else I should try?