[COREblog-en] Migration of COREBlog to COREBlog2

[Donna M. Snow]

Hi Nick (and others who might be interested),

So I got a bit further yesterday...

This is the original site.. http://www.digitalmusicnews.com .. but I 
hope to before we launch. More concerned about getting 2 years worth of 
articles and blogs migrated to Plone (look & feel is not a priority at 
this point)

Here is the one entry that actually made it through...
http://demo1.csquaredtech.com/import-test/78

and when I run a port I get the following...

Error Type
    BadRequest
Error Value
    The id "78" is invalid - it is already in use.
Request made at
    2006/06/22 10:54:01.238 GMT-7

Which I'm guessing means that two blogs got assigned id "78"?

Taking a look at that today .. seems like a minor fix..

so now I need to figure out how to get the author and comments to 
migrate (last modified date would be good too ..but I'm not sure that's 
feasible)
Do I need to setup the bloggers with user ids/membership before I port 
so it won't assign "admin" (which is me).

Also, can I set up a blog per blogger.. at the moment my client has four 
bloggers.. I know Quills allows for multiple blogs (I've used it for 
clients before) but wonder if it's ok to have more than one blog with 
COREBlog2 is ok.

BTW, I used the right export script the first time.. didn't get past 
"start!".. and then tried using the export entries button in the zmi 
(orig site) and it didn't work either.. BUT I actually have the export 
working and I'm THIS close to getting this migration script working!

Thanks for the tips Nick!

Donna M. Snow


Nick Owen wrote:
> On 6/21/06, *Donna M. Snow* <donnamsnow at gmail.com 
> <mailto:donnamsnow at gmail.com>> wrote:
>
>     Hi,
>
>     I have a client whose site resides on at Zope 2.7.4-0 instance with
>     COREBlog 1.0 installed. He has 300+ blog entries we need to
>     migrate to a
>     Zope 2.9/Plone 2.5/COREBlog2 setup.
>
>     I tried the following (read the read me.. installed the files.. added
>     the port at the end of the url)
>     http://coreblog.org/trac/coreblog2/browser/trunk/migration
>
>     I get:
>
>     start!
>     {}
>
>     and nothing else..anyone successfully exported entries from
>     COREBlog 1.0 and imported into COREBlog2?
>
>     It's important that I'm able to migrate the former entries as
>     intact as possible.
>
>     any suggestions? maybe something I need to do on the new instance
>     side??
>
>
>     Donna M. Snow 
>
>
>
> I had the same problem.  It was awhile ago, though and my memory is 
> dull.  IIRC make sure the port script is to be "Script(Python)" , not 
> "Controler Python Script".  Here are some random notes I dug up:
>
> port - the migration script - is in portal_skins/custom
>
> - COREBlog_Export - the exported text data - is also in
> portal_skins/custom
>  Be sure not to include ".txt" extension in ID.
>
> - Your COREBlog2 URL might be http://localhost:8080/test212/
>
> - Then access http://localhost:8080/test212/port with web browser.
>
> And I think the thing that really got for me was that I was using the 
> export button on the old blog, and not the custom export script:
>
> You need to export using another export script. It is in migration
> directory, named 'coreblogexport.dtml.txt'.
>
> HTH,
>
> nick
>
> -- 
> Nick Owen
> WiKID Systems, Inc.
> 404.962.8983 (desk)
> 404.542.9453 (cell)
> http://www.wikidsystems.com <http://www.wikidsystems.com>
> At last, two-factor authentication, without the hassle factor
> Now open source: http://sourceforge.net/projects/wikid-twofactor/
> ------------------------------------------------------------------------
>
> _______________________________________________
> COREblog-en mailing list
> COREblog-en at postaria.com
> http://postaria.com/mailman/listinfo/coreblog-en
> Unsubscription writing to coreblog-en-leave at postaria.com