search

MoMaR5 / regalandroid

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

G3ItemNot FoundException #62

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
On which type of gallery your problem occurred ? (G2, G3, Piwigo ?)
G3
What version of regalandroid are you using? On what Android versions?

1.1.0
Can you provide your gallery url so that a developer can reproduce the
issue ? do we need to login ? in which album the problem occurred ?
www.shawnshay.com

What steps will reproduce the problem?
1.Connect
2.
3.

What is the expected output? What do you see instead?

You could not get connected to the configured gallery
: http://www.shawnshay.com/gallery3

A Problem occured during the gallery connection, the details: 
net.dahanne.gallery3.client.business.exceptions.G3ItemNotFoundException

Please provide any additional information below.
Droid X, tried with user and password and no user and password

Original issue reported on code.google.com by Shawn.S...@gmail.com on 23 May 2011 at 4:34

GoogleCodeExporter commented 8 years ago 
Same problem as above:-

Gallery 3
Regal Android 1.1.0
URL: marinefocus.com.au/gallery3
Steps: Enter gallery then output below is displayed then click OK and get 
message "This Album does not contain any pictures!"

Output:
You could not get connected to the configured gallery
: http://marinefocus.com.au/gallery3

A Problem occured during the gallery connection, the details: 
net.dahanne.gallery3.client.business.exceptions.G3ItemNotFoundException

Additional info:

Ideos X5
Android 2.2.1 Froyo
With no username password
Comments module not installed

Original comment by preissen...@gmail.com on 27 May 2011 at 1:16

GoogleCodeExporter commented 8 years ago 
Login to the gallery as admin, and in Modules enable the REST module.

Original comment by touchsto...@gmail.com on 12 Jun 2011 at 10:44

GoogleCodeExporter commented 8 years ago 
Additionally, I have seen this exception when trying to reconnect after having 
encounter another exception (such as the 414). In this case, opening the app 
settings and closing them seems to clear the condition and allow login to work 
properly.

Original comment by touchsto...@gmail.com on 12 Jun 2011 at 10:50

GoogleCodeExporter commented 8 years ago 
hello all,
thank you touchsto, you are right, you need to enable rest module in g3 to be 
able to browse g3 with regalandroid.
Touchsto, the 414 must be fixed first; I shall have a look in the next weeks.
bye

Original comment by anthony....@gmail.com on 18 Jun 2011 at 3:09