[Tickets #8609] Re: Can't delete faces

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8609
------------------------------------------------------------------------------
  Ticket             | 8609
  Updated By         | tx4587 at crawford.homeunix.net
  Summary            | Can't delete faces
  Queue              | Ansel
  Version            | FRAMEWORK_3
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


tx4587 at crawford.homeunix.net (2009-09-29 11:32) wrote:

Well your steps are what I did, here is some more detail I'm using  
version 1.0.1-cvs. I'm also using postgres 8.4.1, and when setting the  
logging for horde to debug the only result I get when clicking on the  
trash icon is the following:

=====
Sep 29 08:26:37 HORDE [debug] [horde] SQL connection setup for Alarms,  
query = "SET datestyle TO 'iso'" [pid 15412 on line 414 of  
"/var/www/html/horde-webmail-1.2.4/lib/Horde/Alarm/sql.php"]
Sep 29 08:26:37 HORDE [debug] [ansel] Hook _horde_hook_share_init in  
application horde not called. [pid 15412 on line 1713 of  
"/var/www/html/horde-webmail-1.2.4/lib/Horde.php"]
Sep 29 08:26:37 HORDE [debug] [ansel] Max memory usage: 3670016 bytes  
[pid 15412 on line 339 of  
"/var/www/html/horde-webmail-1.2.4/lib/Horde/Registry.php"]
=====

Which doesn't seem to say much to me at least.

> I am unable to reproduce this. This is what I did to try:
>
> 1. Click on "Faces" menu item.
> 2. lick on one of the displayed faces, which brings up the Image  
> view for the image containing the face
> 3. Click "Edit Faces" in the faces widget
> 4. Click the trash can icon next to the face.
> 5. Return to the "Faces" page.
>
> The image of the face originally clicked on is no longer displayed for me.
>
>
> Please check your log files for any relevant errors, or clarify the  
> steps needed to reproduce if not what I outlined above.
>
> Thanks.