Skip to content
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

WordPress Importer #49

Closed
balupton opened this issue Sep 28, 2011 · 15 comments

Comments

Projects
None yet
6 participants
@balupton
Copy link
Member

commented Sep 28, 2011

As a User, I want the ability to import my wordpress data, so that migration will be a lot easier

See obazoud@e21b10f for reference.

Pull request here: #78


Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

@balupton

This comment has been minimized.

Copy link
Member Author

commented Oct 2, 2011

@obazoud does arranging a skype call sometime so we can brainstorm an architecture to support multiple importers sound good to you?

Hopefully I can make them some sort of plugin, so people can easily write their own importers and we could provide a generic ImporterPlugin class for them to extend that will contain a bunch of common functionality.

Thoughts? For a Skype call, I'm good anytime Monday and Tuesday between 9am-9pm Sydney Time (GMT +10:00)

@eldios, feel free to jump in on the call too if you'd like.

@obazoud

This comment has been minimized.

Copy link
Contributor

commented Oct 3, 2011

Hi,
@balupton Thanks for the invitation.
I live in Paris (GMT +1:00).
I would prefer a chat on IRC like that other people could easily participate.

@balupton

This comment has been minimized.

Copy link
Member Author

commented Oct 3, 2011

Sure, let's jump on irc now. #docpad on freenode, or this time Tuesday?

@eldios

This comment has been minimized.

Copy link
Contributor

commented Oct 3, 2011

looks good to me.
Probably it's better at 9PM since when there is 9AM here is like 2AM and I won't probably be online... hopefully... :P
Let's hear from you at 9PM (GMT+10) (12AM UTC) on the IRC chan, ok?

@balupton

This comment has been minimized.

Copy link
Member Author

commented Oct 4, 2011

Cool. So sounds like this will be done pretty soon.

A few ideas. What if we were to create a standard architecture for importers, which is then extended by the specific importers. This will be similar to the way plugins work. One benefit of this is that we could introduce a web interface for importing which has descriptive and helpful information for the user about importing their website. Such a setup procedure could go like this:

  • Step 1. Welcome to docpad
  • Step 2. Do you have an existing site that you'd like to be imported? If so, let us do that.
  • Step 3. What skeleton would you like to go with?
  • Step 4. Skeleton configuration. E.g. selecting themes etc.
  • Step 5. Welcome to your new website. You have these plugins enabled, here are some help links, etc.

Created an issue for the web interface discussion here: #62

Created an issue for the standard importer architecture here: #63

@jwhitley

This comment has been minimized.

Copy link

commented Sep 19, 2012

I'll observe that any import facility is better than none. Also, integration of import into a larger setup process is a major pain when the inevitable bugs or issues are found while importing. For example, I've found that sometimes it's just easiest to do a one-off enhancement of an importer to refactor a site when doing a migration. Small, independent importer scripts make it really obvious where a fix goes when things break, and are generally easy to hack to smooth out those odd edge cases.

FWIW, I have an existing site (in Tumblr, as it happens) that I'd consider migrating to docpad, but key features over and above importers are missing. The prime example in my mind is @obazoud's alias plugin in #78. With that in place, I could fire up Jekyll's Tumblr importer and be running in fairly short order. Not perfect, but it's a start.

@balupton

This comment has been minimized.

Copy link
Member Author

commented Dec 30, 2012

@ashnur is working on this at https://github.com/ashnur/docpad-plugin-wphook

We should set the requirements to be:

  • pages
  • posts
  • uploads
  • comments
@ashnur

This comment has been minimized.

Copy link
Contributor

commented Jan 1, 2013

What I am doing is not really an importer, rather than a bridge between WP Admin and a docpad installation. So pages and posts are realatively easy, but uploads I just don't even tried. For images I just look in the html source, and scrape/save them, replacing the src in the post's content. As for comments, I don't have any idea, I am planning to use either facebook or disqus on the site I need this WP thingie for.
So, we have no original content in WP. For that to import into docpad, there are many WP plugins which one could use to export any data into JSON, and maybe use those for building documents. But I am not sure how to store comments in a docpad install, so that is still a big question mark to me.

@jaydson

This comment has been minimized.

Copy link

commented Jan 2, 2013

To solve the comments stuff, i think that the first step of migration is change the way of how comments works.
The user can't have comments in static documents, so, disqus(or other similar tool) is necessary.

@balupton

This comment has been minimized.

Copy link
Member Author

commented Jan 2, 2013

@jaydson yeah, while they can't have comments on static servers, if they host their docpad instance on dynamic servers (node.js servers) then we can handle comments ourselves. I've done up the nativecomments plugin to showcase this.

@jaydson

This comment has been minimized.

Copy link

commented Jan 5, 2013

I just found this project: https://github.com/thomasf/exitwp
Is a tool for making wordpress migration to jekyll.
Basically, the user need to run the wordpress export tool, paste the XML generated into the exitwp folder, and execute the python script.
Well, i tested, and it works fine for posts, pages and images.
It generates each post as a markdown file.
Maybe we can use this project, or at least use the concept.

@balupton

This comment has been minimized.

Copy link
Member Author

commented Jun 18, 2016

@balupton balupton closed this Jun 18, 2016

@ashnur

This comment has been minimized.

Copy link
Contributor

commented Jun 19, 2016

On the page https://discuss.bevry.me/t/deprecating-in-memory-docpad-importers-exporters/591?u=balupton
I get only a blank page and javascript errors.

@balupton

This comment has been minimized.

Copy link
Member Author

commented Jun 20, 2016

@ashnur

This comment has been minimized.

Copy link
Contributor

commented Jun 20, 2016

Yeah, it works now, thanks. Also, the change and the reasoning seems quite sound.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.