Using the latest version from git as of this morning, I am not able to delete photos or albums. It prompts with "are you sure..." and then nothing happens. No error is output using E_ALL.
I'm also having an issue where I can't delete albums or images. However, once I click on the "delete photos" (both with the trash can image or the "Delete this photo" link), I have this running circle which say "Loading" and I never get the "are you sure..." that is documented in previous post. The logs are not showing anything except the access to a link:
Posts: 3
Hi,
I'm also having an issue where I can't delete albums or images. However, once I click on the "delete photos" (both with the trash can image or the "Delete this photo" link), I have this running circle which say "Loading" and I never get the "are you sure..." that is documented in previous post. The logs are not showing anything except the access to a link:
[22/Jun/2009:14:02:49 -0700] "GET /gallery3/index.php/quick/form_delete/3?csrf=8e454ea5d29e3dca71534053bc8ed6de&page_type=album HTTP/1.0" 200 466
So, it goes to the server once I click a link but nothing more. I've tried it from Firefox on Linux and from IE8 on Vista.
I've done the git pull as of today (June 22 2009).
Hopefully there is a fix or it will be corrected rapidly. Anyone?
Thank you.
ehfortin
Posts: 56
I have got the same issue as ehfortin with the git of today (22-6)... The running circle just keeps running
Posts: 24
I have got the same issue with the git of today (24-6)... The running circle just keeps running
Any clues ?
/var/log doesn't show anything when trying to delete something
_________________
Gil
My Gallery http://mesphotos.fontismedia.com/
Posts: 7994
Oops, this is a regression. Filed http://sourceforge.net/apps/trac/gallery/ticket/459 for it.
Update: fixed in the latest code.
---
Problems? Check gallery3/var/logs
bugs/feature req's | upgrade to the latest code | use git | help! vote!
Posts: 61
I had the same problem as of last night and I confirm that it was fixed in using the latest code.
Posts: 56
I can confirm as well that it was fixed in the latest code... Thanks Bharat!