Closed GoogleCodeExporter closed 8 years ago
These steps don't reproduce the problem for me. Maybe there is some difference
between the wave you're trying to import and the ones I'm testing with. Can
you describe a sequence of steps that starts with "create a new wave on
wave.google.com" and reproduces the problem with that wave?
I don't think your diagnosis is correct:
http://code.google.com/p/walkaround/source/browse/src/com/google/walkaround/wave
/server/googleimport/ImportWaveProcessor.java#82 replaces @googlewave.com with
@gmail.com when importing, and
http://code.google.com/p/walkaround/source/browse/src/com/google/walkaround/wave
/server/googleimport/ImportWaveProcessor.java#140 adds the importing user as a
participant.
Please also make sure you've deployed the latest version from git, the code to
add the importing user is a recent addition.
Original comment by oh...@google.com
on 28 Dec 2011 at 9:24
Original comment by oh...@google.com
on 4 Jan 2012 at 12:36
Fixed according to
https://groups.google.com/d/msg/walkaround-dev/GzsczUISc-Y/_KTto0ZZPaUJ .
It's true that private import is less useful than shared import, but that's a
different problem tracked in bug 41.
Original comment by oh...@google.com
on 13 Jan 2012 at 9:14
Original issue reported on code.google.com by
guillaum...@gmail.com
on 28 Dec 2011 at 7:53