On Mon, Feb 10, 2014 at 11:34 AM, Ryan Ollos <[email protected]>wrote: [...]
> > If you are suggesting that the use of RPC plugin somehow circumvents these > difficulties please explain. For the time been I'll just include other resources that might be valuable as well https://trac.edgewall.org/wiki/TracImport https://www.mail-archive.com/[email protected]/msg18485.html > So far you've failed to explain how the RPC > plugin could be used in the migration. > > That's «by design» . I do not recommend (yet) to do so ... and I say (yet) because e.g. I plan to add support for timestamps in the API , but that's WiP ... If the OP based on the limitations I mentioned before considers that this is the way they choose to import their data then I will point him to a (relatively simple) script to get this done . > Eventually we should somehow support migrating from multiple trac > environments, though handling plugin data for more than a few plugins would > probably be outside the scope of what we could ever support. > That depends ... I cannot make any assumptions on non-existing code . Nevertheless this is such a common use case that maybe someone else has started to work on such a feature ? -- Regards, Olemis - @olemislc
