By vivalditec on Tuesday, 07 January 2014
Replies 3
Likes 0
Views 1.2K
Votes 0
There is a blog import feature in admin, that supports importing from Wordpress XML, but it's only available for Admin, and it comes with a couple of caveats:


Backup your existing database.
Put your site offline to avoid any interferance of database activities.


Is there any reason that this is not available for the end user, so the users can import their Wordpress blog themselves?

Why do you recommend to take the site offline before importing?

Would it be possible to reuse the migration code from the admin and make it available for the end users?
Hello,

So sorry for the delay in getting back to you. The migration is not made to be used by all users. As this affects the whole site greatly we only have it in backend for the use of the Super User. As for backing up the site and putting it offline, these are just precautions that you should take just in case there is some issues when migrating. Hope this helps.

Thanks!
·
Wednesday, 08 January 2014 00:08
·
0 Likes
·
0 Votes
·
0 Comments
·
OK, that's cool.

I didn't review the code in great detail, but looking at the source code, I didn't see any obvious reasons for this restriction. I guess maybe it is because loading very large imports will slow down the site?

What I would like to do is to take your GPL'd import code, and make an importer for use by the public. I hope doing it async, with throttling, should work.
·
Wednesday, 08 January 2014 18:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

So sorry for the delay in getting back to you. Feel free to hack the codes all you want We did not really place any restriction on the codes. It is just place in the backend where only administrators can access it.

Thanks!
·
Wednesday, 08 January 2014 18:28
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post