Dieter Heine wrote: > The reason for the failed allocation was the sitegroup dependency in the > xml-file. As exported from the source midgard all blobs have the > sitegroup field set to the GUID of the source sitegroup. Fine, I thought > and exported on the target system - same midgard release - a single blob > just to find the GUID of the target sitegroup. But there the sitegroup > reference is completely missing in the xml-file. This was a big suprise > because it seems as if both midgard systems doesnot behave the same way.
Depends on the repligard config file ou use. I believe the default is repligard.xml, and there's another named repligard_withsg.xml which will also do sitegroup related work. > Before I imported successfully most tables suddenly an single obscure > bug was found by the message: "form of line not valid". With the line > number given I found a record_extension of a "page_element^C". A number > should be found instead of Ctrl-C. Since I couldnot find the correct > number I left it out and the import itself seemed to work without error. This one is significant. Sounds like a bug. > After a new host-prefix (Guild) has been added I called the root-page > directly on the target system but every image was missing. Although in > Asgard nearly all has been imported the page with all blobs was still > missing. I remembered that the first import was interrupted by the > Crtl-C bug I tried to import again to complete it. It worked but the > visual homepage was missing lots of my programming that I already saw > in target asgard's snippets. However mgd_include_snippet doest not work > since a call in code-init shows "call to undefined function". It can > be reproduced by looking at http://insight.kn-bremen.de:8080/Guild/home. > The only reason must be the failed snippet inclusion. The string is ok > but the inclusion is "void" due to the return value of > mgd_include_snippet. I have no idea how to track this kind of bug but to > search mysql.log. If it says mgd_include_snippet is undefined there's something else going on; it means the function wasn't compiled in. Did you ever do --enable-mgd-preparser? This will indeed exclude this function. The 1.4.2 release did not properly rebuild everything if you reconfigured without this option. The solution in that case is to unpack a clean midgard-php4 somewhere and configure again. > The silly problem with the according page (home) of this page_element is > also that it cannot be written by a member of the sitegroup admin. It's > the only page unter Guild that appears in asgard without callbacks. But > the biggest fault happens with groups and persons itself. Most (>>10) of > all arrived in SG0. But not all (3). Since all other records of the > import found the right sitegroup I still believe it was possible to > remove the sitegroup GUIDs in the xml-file before it has been imported. > > > If you are interested the ruins can be found on > http://insight.kn-bremen.de:8080/Guild . I'd rather have the situation as you had before the install (if you have a backup) and try it myself. > At the moment I don't think that repligard is a sancrosanct for > migration between different sites. Due to my plans before (in the > dev-list) about multiple db-handling and my experiences now I am not > quite sure. But many doubts about repligard for migration are still > alive because a complete import from different sites may have > unpredictable results. If it does, it's simply a repligard bug that needs to be fixed. There's nothing in its design that would prevent doing this kind of import. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
