1- >> Create content >> google wave (Embedd a wave into a drupal node.)
2 - Paste in wave ID -- changed %252 to + sign
3 - Preview see "You are not a participant in this wave"
4 - Add Public to wave mail list (public@a.gwave.com) to original wave just to be sure ;-)
... should this have worked?
Same message "You are not a participant in this wave"
5 - ????

I created a drupal user with the exact wave creator googlewave address. (me!)

Hmmmm. Where to look first for answers.
Thought I'd drop a quick post.

Cheers,
alar

Comments

alar’s picture

alar commented
Component: User interface » Documentation

BTW: I'll help with the documentation when I get it figured out :-)

Anonymous’s picture

Anonymous (not verified) commented

Hi, I've come accross this issue too. It seems to be related to the wave embed api. Until now I can replicate the following things:
If a wave was created before the last wave embed api update you'll get the message "You're not a participant of this wave." even when you're logged into wave or the wave is public.
Any new wave I've created since then just works. You'll get either the participant message if the wave is not public or see the wave as "Anonymous".

Also be sure to log into wave. ;)

Anonymous’s picture

Anonymous (not verified) commented

BTW: Good that you mentioned the plus sign conversion. Maybe I should do this automatically e.g. just paste the wave url and I'll extract the wave id?

Anonymous’s picture

Anonymous (not verified) commented
Version: 6.x-1.0-beta1 » 6.x-1.0-beta3
Component: Documentation » Miscellaneous
Assigned: Unassigned »
Category: support » bug
alar’s picture

alar commented

I've reviewed the google wave api documentation http://code.google.com/apis/wave/embed/guide.html. When I use their example and the example Google wave id:
googlewave.com!w+Ism0RMW_A
All is well. It works.
I can see the embedded wave in Drupal.

If I PASTE in my own wave (with addressee public@a.gwave.com included!)
I still see "You are not a participant in this wave".
googlewave.com!w+ByhlnVHVkC

I am creating new waves to test, so it doesn't sound like the same problem you were having, but it does look like other people using the Wave API are having similar problems.

Cheers,
alar

Anonymous’s picture

Anonymous (not verified) commented

Thanks for the update.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Closed (fixed)

Hey, it seems that Google has fixed this issue.

I just tested and it seems to work now. On my way to release 1.0 within the next days. :-)