[wp-hackers] [Gsoc Idea] Tagging/Taking a snapshot of WP installation

[Mujtaba Boori]

Hey.

I am interested in doing the export/import as listed in idea list.

However, I have many ways of doing not really sure which one is good.

one way of doing it. take the URL of the WP and verify user/pass then
creates xml file remotely and download it in exported WP

other way, it is to transfer all data without the need for xml. if that
possible.

any suggestion ?


On Wed, Mar 10, 2010 at 7:08 PM, Justin Shreve <justin.shreve at gmail.com>wrote:

> Here's another idea (that I previously mentioned off-list):
>
> Make sure that there is a filter or hook when a snapshot/backup is made so
> people can create plugins to do various things with the backups (create a
> plugin to email to a specified list, FTP to a server or upload to a third
> party backup service). You could create a example plugin (or two, or
> three!)
> as one of the delieverables of the project (make sure to mention it in your
> proposal!).
>
> On Wed, Mar 10, 2010 at 1:36 PM, Ankit Ahuja <ahuja.ankit at gmail.com>
> wrote:
>
> > I'm applying. I'm trying to think of other possible ideas besides the
> ones
> > listed.
> >
> > Yes, this could definitely include enhancing the import/export
> > functionality
> > as both are interrelated.
> >
> > On Wed, Mar 10, 2010 at 11:55 PM, Justin Shreve <justin.shreve at gmail.com
> > >wrote:
> >
> > > Sounds pretty interesting.
> > >
> > > One of the ideas on the wiki is improve the backup/import system -
> > > this could be a part of it.
> > >
> > > Are you applying or just offering some ideas?
> > >
> > > On Wednesday, March 10, 2010, Ankit Ahuja <ahuja.ankit at gmail.com>
> wrote:
> > > > What this basically means is being able to take a snapshot of a WP
> > > > installation at any particular time and then being able to revert
> back
> > to
> > > it
> > > > if something bad happens ( say files are deleted or the blog is
> hacked
> > )
> > > >
> > > > The snapshot will include the following files:
> > > >
> > > > 1. WP Core Files
> > > > 2. Current theme's files
> > > > 3. Installed plugins (only the enabled ones)
> > > > 4. Maybe a content XML ( the one that is produced as part of the
> Export
> > > > process )
> > > >
> > > > This will allow the user to tag a particular version of the entire WP
> > > > installation. And then, if something bad happens, the user can simply
> > > revert
> > > > to a snapshot. The reason to include all of the core and plugin files
> > is
> > > > because of the nasty hacks that can introduce code at hard to find
> > > places.
> > > >
> > > > Snapshots can also be used when moving blogs to different servers.
> > > >
> > > > Additionally, the user could see a diff of the current status of blog
> > v/s
> > > > the last snapshot version. This diff would be at an abstract level
> for
> > > cases
> > > > where entire themes/plugins are changed. It will be useful to keep an
> > eye
> > > > out for spams/hacks.
> > > >
> > > > This is an idea for a GSoC 2010 project. I would love to know what
> you
> > > think
> > > > about it. Thanks!
> > > >
> > > > -Ankit
> > > > _______________________________________________
> > > > 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
> >
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
Mujtaba Ali Alboori