[wp-hackers] Blog Import/Export Idea - Google Summer of Code 2010

[Meher Anand]

On Tue, Mar 23, 2010 at 3:17 AM, Andrew Gray <andrew at graymerica.com> wrote:

> This was my point exactly,   If you built a system to automatically move
> the blog via those steps, you would serve the same purpose, but it would be
> pretty simple.
>
> I think a "move my blog" system would be great if it automated all the
> steps.
>
> One of the Amazon S3 backup plugins does this exact thing, but uses Amazon
> S3 Buckets as the middle step.
>
> I just do know know how much utility there would be in a "move part of my
> blog" system that only moves some of it, such as a date range.
>
> I could see a system where you install a plugin in on both sites, copy an
> access key from one to the other, click a button and it moves everything for
> you.  I just do not think that remotely accessing mysql would be the way to
> do it.
>
> This is probably better suited as a plugin, then in the core however.
>
>
> The user is given an option to move either part of the blog or the entire
blog. That's why the check-list. And sorry I had skipped the SQL connections
question by mistake. If remote SQL connections are not allowed, then what
the user could possibly do is to install the same plugin on the old blog.
The plugin would have an option like "My db server is not remotely
accessible. I would like to take a backup of it" which the user can click
on. The plugin, after executing, would create a zip file with all media and
database in .sql format and this file would then be downloaded by the new
blog, unZIPped into a temp directory and the necessary updations will be
made.

Whether this would be core-functionality or plugin is not my call as this
would not affect my coding part significantly. Please let me know about any
other flaws in my idea.

Thanks and regards.

Meher Anand

>
> Andrew
>
>
> On Mar 22, 2010, at 5:30 PM, Jue Wang wrote:
>
> > I think he means the 'blog_url' and 'blog_home' entries in the wp_options
> > table.
> >
> > @Andrew, I think there is a role for some kind of "back-up / migrate
> site"
> > functionality that only requires going through the WP interface, which
> could
> > be partially what Meher is going for. The current export contains an XML
> of
> > entries and comments -- what if you could additionally include options,
> > assets, and media in the same export? Then pop that back into another
> blog,
> > click the 'import' button, and you're done. No mucking about in
> FTP/MySQL.
> > Incidentally, this is exactly what backup/restore is supposed to do in
> > Movable Type, but it's horribly buggy and mostly useless.
> >
> >
> > On Mon, Mar 22, 2010 at 5:25 PM, Mike Schinkel
> > <mikeschinkel at newclarity.net>wrote:
> >
> >> On Mar 22, 2010, at 5:20 PM, Andrew Gray wrote:
> >>> 4. Change the URLs in the config table
> >>
> >> As I'm working on a domain-switcher plugin for my own use (and possibly
> to
> >> release if there is significant interest in other's testing it) I'm
> curious
> >> for you to elaborate on this step?
> >>
> >> -Mike
> >> _______________________________________________
> >> wp-hackers mailing list
> >> wp-hackers at lists.automattic.com
> >> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >>
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>