Hi,

I did a migration from wordpress importing the file: mysite.wordpress.2012-07-10.xml and now I want import again the same site of Wordpress but I don't want to delete the last contents imported in the first migration. I need to add new contents or authors (update) from wordpress, no deleting.

I have tried to select the option "Remove migration bookkeeping", the last content and authors are keept but when I tried to import with the file mysite.wordpress.2012-09-26.xml appears the follow error:

Could not prepare directory wordpress://

I review the directory sites/default/files and has permissions of writting.

Thanks for your help.

Comments

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Category: bug » support
Status: Active » Postponed (maintainer needs more info)

There isn't enough information to tell why you got the "prepare directory" error. What's your private path at /admin/config/media/file-system? Is that path, plus the "wordpress" directory within it, writable"?

It should be noted that to import new content, all you need to do is get a fresh WordPress export and import it directly. By removing the migration bookkeeping, you're going to get duplicate items, because it's the bookkeeping that tells wordpress_migrate what's already been imported so it can skip it on reimport.

cabita’s picture

cabita commented

Thanks for your answer. I have found the directory "wordpress" and I have assigned permissions..

However, I would like to clarify with respect to update the migration. I have selected bookkeeping to keep the last contents and when I import the new file load all posts (last and new posts). REally not update, not compare, really import all again but keeps the last contents. am I right?

I had to import the xml file by drush because the other way always happened an error .

For future versions of modules should be wonderful can choose the contents will be imported to drupal. It's only a suggest, the module is great.

Thanks.

Claudia.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

If what you want is, when importing a new export from the same blog, to only import new content from that blog while keeping the previous content that you had imported, you must NOT purge the bookkeeping. It's the bookkeeping that lets the module know what's already been imported, so it doesn't import it again.

cabita’s picture

cabita commented

Hi,

Ok, thanks for your answer but if not purge then I have to delete the last migration because appears an error message indicating the ids are repeated. In my tests if there is a migration not allow a new migration of the same blog and only update, in this case, I have to delete the last migration and migrate again all. Then not update.

Thanks in advance.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

OK, here's how it works for me:

1. I import an XML file exported from WordPress.
2. At a later date, I get a new export from WordPress and import that (I do NOT remove the previously-imported content or the bookkeeping).
3. Any content that was added to WordPress since the initial import is now in Drupal, without affecting the content that was initially imported.

Are you saying that in step 2, you're getting some kind of duplicate ID errors? If so, can you paste in the exact error message?

Thanks.

Note: When replying to an issue with the status "postponed (maintainer needs more info)", please change the status back to "active" to be sure we come back to it.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

No further information provided.

aschiwi’s picture

aschiwi commented

@mikeryan: When I tried to import an updated xml from WordPress I got this error:


Error message
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'http://www.[snip].de' for key 'filename'

Updating to 2.1 fixed this problem for me.

P.S. thanks for this great module :)