GR fails to place new albums in the correct place.

ezra

Joined: 2003-06-24
Posts: 7

Posted: Tue, 2003-06-24 02:14

First off... I'm using the latest stuff as of now: Gallery 1.3.4 and GR 1.0.1 on a RH 9 box connecting to a Linux/Apache server.

When I create a new album in GR with the "New Album" button, it consistently (except for the first time) fails to place the new album in the right place if I want it placed at the root of the tree. (That's the most descriptive term I can think of for the highest level in the hierarchy of albums.) Every where else is fine.

The above is the real bug that I have found. Something else that I noticed is that if GR is logged in, and I go to my gallery web page and log in, the main page has the appearance of a user who is not logged in, but if I view inside an album, all of the other pages have the optoions that come with being logged in. (All this applies to an administrator account logging in).

Right now, GR has locked up upon loading, that's a first, I've been using it for an hour or so tonight. Maybe a good feature idea would be some kind of abort option/button.

I think GR needs a 'refresh' button to refresh its data on the albums in case I moved an album using the web-interface since GR's data was last sent. Or, maybe lock each other out: if GR is logged in, then you can't log in from the web and vice versa.

All of this is said with tons of humility, I am a newbie, and I know it, and I totally lappreciate this software and the gallery-people.
Thanks

paour

Joined: 2002-08-14
Posts: 1479

Posted: Tue, 2003-06-24 02:30

That's a lot of feedback

Creating a top-level album: this is fixed in GR 1.1b4 (not yet publicly available).

I agree GR needs an abort button.

Refresh can be achieved by clicking 'Log out' and then 'Log in'.

Currently, there is no locking between GR and Gallery. Similarly, if you have 2 concurrent web browser sessions of the same album, you can get a situation where changes made in one session cancel or overwrite changes made in the other. This is a design flaw of G1. G2 will handle this better.

ezra

Joined: 2003-06-24
Posts: 7

Posted: Tue, 2003-06-24 15:48

Thanks a lot.

(If I can't code, might as well give good feedback, ay?)

ezra Joined: 2003-06-24 Posts: 7	Posted: Tue, 2003-06-24 02:14
	First off... I'm using the latest stuff as of now: Gallery 1.3.4 and GR 1.0.1 on a RH 9 box connecting to a Linux/Apache server. When I create a new album in GR with the "New Album" button, it consistently (except for the first time) fails to place the new album in the right place if I want it placed at the root of the tree. (That's the most descriptive term I can think of for the highest level in the hierarchy of albums.) Every where else is fine. The above is the real bug that I have found. Something else that I noticed is that if GR is logged in, and I go to my gallery web page and log in, the main page has the appearance of a user who is not logged in, but if I view inside an album, all of the other pages have the optoions that come with being logged in. (All this applies to an administrator account logging in). Right now, GR has locked up upon loading, that's a first, I've been using it for an hour or so tonight. Maybe a good feature idea would be some kind of abort option/button. I think GR needs a 'refresh' button to refresh its data on the albums in case I moved an album using the web-interface since GR's data was last sent. Or, maybe lock each other out: if GR is logged in, then you can't log in from the web and vice versa. All of this is said with tons of humility, I am a newbie, and I know it, and I totally lappreciate this software and the gallery-people. Thanks
	XUser login Username: * Password: * Create new account Request new password
paour Joined: 2002-08-14 Posts: 1479	Posted: Tue, 2003-06-24 02:30
	That's a lot of feedback Creating a top-level album: this is fixed in GR 1.1b4 (not yet publicly available). I agree GR needs an abort button. Refresh can be achieved by clicking 'Log out' and then 'Log in'. Currently, there is no locking between GR and Gallery. Similarly, if you have 2 concurrent web browser sessions of the same album, you can get a situation where changes made in one session cancel or overwrite changes made in the other. This is a design flaw of G1. G2 will handle this better.

ezra Joined: 2003-06-24 Posts: 7	Posted: Tue, 2003-06-24 15:48
	Thanks a lot. (If I can't code, might as well give good feedback, ay?)

GR fails to place new albums in the correct place.

XUser login