MoMaR5 / regalandroid

Automatically exported from code.google.com/p/regalandroid
0 stars 0 forks source link

G3, "No value for web_url" #18

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I'm trying to use the beta in the downloads area to connect to a G3 gallery 
(which is password protected). It connects ok and shows that it's logged in, 
but when I hit the 'Enter gallery' button and it tries to fetch the albums, I 
get this:

  G3GalleryException: No value for web_url

This is on Android 2.2.

Original issue reported on code.google.com by ciaran.g...@gmail.com on 16 Dec 2010 at 2:02

GoogleCodeExporter commented 8 years ago
hello, could you 
* give me your gallery url
* create me a user/passwd
so that I can reproduce this error ? (cause I did not encounter it on my 
gallery)
You can send them via email to : anthony dot dahanne at gmail.com
thanks

Original comment by anthony....@gmail.com on 16 Dec 2010 at 2:07

GoogleCodeExporter commented 8 years ago
hello ! I received your email but the credentials you sent me are not working.
could you please resend them to me ?
thanks

Original comment by anthony....@gmail.com on 20 Dec 2010 at 1:49

GoogleCodeExporter commented 8 years ago
I had this issue too until I updated my gallery install to the latest release 
(I was running rc2). I'd suggest looking at your gallery version first. It 
worked for me anyway.

Original comment by dsti...@gmail.com on 21 Dec 2010 at 6:11

GoogleCodeExporter commented 8 years ago
I'm running RC2 as well - let me try fixing that before you spend time looking 
at this.

Original comment by ciaran.g...@gmail.com on 22 Dec 2010 at 3:24

GoogleCodeExporter commented 8 years ago
hello ! any update ?
If it is a matter of using RC2, I will update the release note
thanks

Original comment by anthony....@gmail.com on 3 Jan 2011 at 4:04

GoogleCodeExporter commented 8 years ago
Yes, I can confirm that upgrading to the G3 release, instead of using RC2, 
makes this error message go away.

It still doesn't work for me though, but I'll log a separate issue for that 
because it's totally unrelated. Using the G3 release definitely resolves the 
error I originally reported here.

Original comment by ciaran.g...@gmail.com on 4 Jan 2011 at 11:00

GoogleCodeExporter commented 8 years ago

Original comment by anthony....@gmail.com on 4 Jan 2011 at 3:04