Hi, This issue isn't easy. I have filed a feature request that you get a -s option on the repligard command that igneores the sitegroup setting. My reasoning for this is as follows:
I'm implementing large changes in my system (upgrading from 1.4beta5 to 1.4.2) and I do not have the option to keep them in sync (hell, 1.4beta5 doesn't even have propper repligard functionality). Therefore I make a bunch of snippets that I'll use when finally upgrading my site. I then use nadmins fine funtions to export these snippets. Then, I upgrade the old site and try to import the snippets. Even when using admin*sitegroup, I end up importing the snippetsinto a new sg. What I want is to say to repligard "do not bother about the oter sg use the one in your config file to decide who you should import to". That's what I whant the -s setting to do. This does not solve all problems. It's not intended to. But it solves mine, therefore I suggested it. It is hard to get a fine tool like repligard correct. Here's another thing I am wondering about: is it possible to have two objects with the same GUID in two different sitegroups? Should it be possible? It might for example be ok in some cases to be able to move trees(or parts thereof) of content or snippets in and out of your webserver and back to the internal one. Althought they do not share the same sq (if that is the admins haven't been realy clever), the import should place the content in the correct sg. I'm sorry if my language seems angry or so. That is not the intention. I'm just trying to make some suggestions on how midgard should work. It's a product I realy love. Tarjei --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
