New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error occurred when migrate wordpress exported xml files #1

Closed
ghosrt opened this Issue Mar 6, 2014 · 8 comments

Comments

6 participants
@ghosrt

ghosrt commented Mar 6, 2014

using node.js v0.10.26 on Windows 8.1 Pro, all settings by default

here's the log:

[error] TypeError: Cannot read property '1' of null
TypeError: Cannot read property '1' of null 
at ELEMENTS.replacement (D:\node.js\hexo\node_modules\hexo-migrator-wordpress\node_modules\to-markdown\src\to-markdown.js:71:70)
at D:\node.js\hexo\node_modules\hexo-migrator-wordpress\node_modules\to-markdown\src\to-markdown.js:96:41
at String.replace (native)
at replaceEls (D:\node.js\hexo\node_modules\hexo-migrator-wordpress\node_modules\to-markdown\src\to-markdown.js:95:23)
at toMarkdown (D:\node.js\hexo\node_modules\hexo-migrator-wordpress\node_modules\to-markdown\src\to-markdown.js:78:16)
at D:\node.js\hexo\node_modules\hexo-migrator-wordpress\index.js:59:54
at D:\node.js\hexo\node_modules\hexo-migrator-wordpress\node_modules\async\lib\async.js:111:13
at Array.forEach (native)
at _each (D:\node.js\hexo\node_modules\hexo-migrator-wordpress\node_modules\async\lib\async.js:32:24)
at Object.async.each (D:\node.js\hexo\node_modules\hexo-migrator-wordpress\node_modules\async\lib\async.js:110:9)

I have no idea about how to deal with it.

@jerriep

This comment has been minimized.

Show comment
Hide comment
@jerriep

jerriep Apr 23, 2014

@ghosrt I also ran into this problem. I initially pointed to migrator to the RSS feed of my blog as that is what the documentation at http://hexo.io/docs/migration.html states. I then noticed that the readme for te migrator (https://github.com/hexojs/hexo-migrator-wordpress/blob/master/README.md) actually states that you should export the Wordpress blog and point the migrator to the exported .xml file.

I did it that way and then everything worked fine for me. Maybe you can see if that works for you?

Only problem now is that I need to figure out some way to get all the images migrated as well :(

jerriep commented Apr 23, 2014

@ghosrt I also ran into this problem. I initially pointed to migrator to the RSS feed of my blog as that is what the documentation at http://hexo.io/docs/migration.html states. I then noticed that the readme for te migrator (https://github.com/hexojs/hexo-migrator-wordpress/blob/master/README.md) actually states that you should export the Wordpress blog and point the migrator to the exported .xml file.

I did it that way and then everything worked fine for me. Maybe you can see if that works for you?

Only problem now is that I need to figure out some way to get all the images migrated as well :(

@ghosrt

This comment has been minimized.

Show comment
Hide comment
@ghosrt

ghosrt Apr 24, 2014

@jerriep I've read your reply, but I still stuck on this situation right now, since I'm using the exported xml file at first, I can't find a solution to solve this problem right now. However, thank you for replied my issue.

ghosrt commented Apr 24, 2014

@jerriep I've read your reply, but I still stuck on this situation right now, since I'm using the exported xml file at first, I can't find a solution to solve this problem right now. However, thank you for replied my issue.

@tommy351

This comment has been minimized.

Show comment
Hide comment
@tommy351

tommy351 Apr 27, 2014

Member

RSS migrator was fixed. Now I'm working on WordPress migrator.

Member

tommy351 commented Apr 27, 2014

RSS migrator was fixed. Now I'm working on WordPress migrator.

@tommy351 tommy351 added the bug label Apr 27, 2014

@tommy351

This comment has been minimized.

Show comment
Hide comment
@tommy351

tommy351 Apr 27, 2014

Member

This plugin was refactored in 0.1.0. The bug should be fixed.

Member

tommy351 commented Apr 27, 2014

This plugin was refactored in 0.1.0. The bug should be fixed.

@tommy351 tommy351 closed this Apr 27, 2014

@miibotree

This comment has been minimized.

Show comment
Hide comment
@miibotree

miibotree Jul 24, 2015

have you fix the bug yet?@tommy351, it seems that the bug still exists

miibotree commented Jul 24, 2015

have you fix the bug yet?@tommy351, it seems that the bug still exists

@SunnyBingoMe

This comment has been minimized.

Show comment
Hide comment
@SunnyBingoMe

SunnyBingoMe May 4, 2016

Contributor

Update:
This problem is due to node_modules\to-markdown\src\to-markdown.js is not expecting img > src to be null. See simple fix here: https://gist.github.com/SunnyBingoMe/f74589ef688c0eed962314fdb61a1576


-- Same problem, hexo-migrator-wordpress version 0.1.2. Windows 10.--

Contributor

SunnyBingoMe commented May 4, 2016

Update:
This problem is due to node_modules\to-markdown\src\to-markdown.js is not expecting img > src to be null. See simple fix here: https://gist.github.com/SunnyBingoMe/f74589ef688c0eed962314fdb61a1576


-- Same problem, hexo-migrator-wordpress version 0.1.2. Windows 10.--

Xuanwo pushed a commit that referenced this issue May 5, 2016

Merge pull request #1 from SunnyBingoMe/id-url-meta-data
Added post_id as URL to meta data
@zhuziyi1989

This comment has been minimized.

Show comment
Hide comment
@zhuziyi1989

zhuziyi1989 commented Aug 13, 2016

@SunnyBingoMe 谢谢~

@SunnyBingoMe

This comment has been minimized.

Show comment
Hide comment
@SunnyBingoMe
Contributor

SunnyBingoMe commented Aug 14, 2016

@zhuziyi1989 客气

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment