phillip at communitybandwidth
Nov 19, 2008, 7:36 AM
Post #2 of 2
All I can say is that I've done what you're describing several times
on the 1.10.x series of Bricolage and, each time, it worked just fine.
The only things to keep in mind are leaving certain nodes in the XML
blank, i.e., the story ID, etc. (anything that Bricolage will have to
figure out at the time of the import, basically).
I wonder if you could import them into 1.10.x and then use something
bric_soap story list_ids | bric_soap story export - | bric_soap story
create --server some.host.org -
To move them to your other 1.11.x instance?
On 18-Nov-08, at 5:55 AM, Adeola Awoyemi wrote:
> Hi all,
> Not sure if anyone is experiencing this?
> 1. I created a story and exported it using bric_soap.
> 2. I used the exported xml as a template to auto generate new
> stories for migration.
> 3. I use "bric_soap story create xxx.xml" to create the stories
> using the xml files created from the template
> Now when I go back to the CMS interface, previewing/publishing any
> of the new stories doesn't show all the content that was migrated.
> When I check the stories out and do a preview it still doesn't work.
> Then I hit "Save" or "Save and Stay" and then preview it the story.
> Now I get all the content. So it seem like there is a problem with
> the way bric_soap puts stories into the system.
> I have already created a bug report regarding this issue.
> We're a bit stressed for time at the moment so I can't give more
> debug info on this but will provide more once we get this stuff out
> the door.
> Can anyone can identify with the same issues? Does anyone have any
> hints as to what could be happening or is this something that is
> already fixed?
> We're running Bric 1.11.2 on Ubuntu 8.04
>  http://bugs.bricolage.cc/show_bug.cgi?id=1394
> Creative Developer - Digital Craftsmen Ltd
> Exmouth House, 3 Pine Street
> London, EC1R 0JH
> t: +44 20 7183 1410
> f: +44 20 7099 5140
> m: +44 75 9527 7886
> w: http://www.digitalcraftsmen.net/
Simplifier of Technology