Page 1 of 1

import/export help

Posted: Fri Jun 12, 2009 9:56 pm
by snitchard
Hello,

I had to move my Serendipity blog from one domain to another so I exported alll of the entries by going to the export section. Then I'm presented with a page that appears to be XML or PHP so I save the file with my web browser's "save as" function. Now I have a rss.php file on my desktop.

When I go to the new domain which is also Serendipity and choos to import a generic RSS feed it asks for a URL. I posted the rss.php file in a folder on my new domain and pointed the import to that URL. I then get an error saying

Error on line 149 of /home/content/s/n/i/snitchard/html/blog/bundled-libs/Onyx/RSS.php: File has an XML error (Invalid document end at line 2).
Import successfully completed

How can I successfully import these entries?

Thanks,
Rich

Re: import/export help

Posted: Fri Jun 12, 2009 10:14 pm
by garvinhicking
Hi!

That's not a good way to migrate!

The XML export only holds entries and categories. You will definitely loose authors, plugins, themes, configurations, tags, static pages etc.

If you move s9y, you should simply copy all files and the whole database to the new provider (using a SQL dump with help froma tool like phpMyAdmin).

Regards
Garvin

Re: import/export help

Posted: Sat Jul 25, 2009 10:57 pm
by jdavis
This is not a great solution for a blog hosted by someone else. It essentially means that I lose information going from s9y to s9y.

It would be very convenient if there were a way to import/export a file without losing information.

Re: import/export help

Posted: Mon Jul 27, 2009 9:48 am
by garvinhicking
Hi!

Yes, s9y is tailored to be installed as your own software on your own domain. If it is on a hosted plattform, the hoster should offer you migration solutions - or, of course, it's in the interest of the hoster to keep you on their site and not to go to another hoster. ;)
It would be very convenient if there were a way to import/export a file without losing information.
Sadly this is a lot of work and coupled with many problematic plugin issues, and parsing overhead. There are many other things on our todo list with a higher priority, so better not hold your breath.

The SQL and file migration is really the ideal way here. Can you describe your actual setup in which this does not work out?

Regards,
Garvin