[Tickets #9838] Re: Groups will not update
bugs at horde.org
bugs at horde.org
Tue Apr 19 17:35:11 UTC 2011
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/9838
------------------------------------------------------------------------------
Ticket | 9838
Updated By | mailroom at bijurdelimon.com
Summary | Groups will not update
Queue | Horde Groupware Webmail Edition
Version | 1.2.9
Type | Bug
State | Feedback
Priority | 2. Medium
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
mailroom at bijurdelimon.com (2011-04-19 17:35) wrote:
> Unfortunately the SQL group driver doesn't log any queries, but:
>
>> Apr 08 12:43:17 HORDE [debug] [horde] SQL query by
>> Horde_History::getHistory(): SELECT * FROM horde_histories WHERE
>> object_uid = ?, values: horde:group:3 [pid 12320 on line 244 of
>> "M:xlibHordeHistory.php"]
>> Apr 08 12:43:17 HORDE [debug] [horde] SQL query by
>> Horde_History::log(): INSERT INTO horde_histories (history_id,
>> object_uid, history_ts, history_who, history_desc, history_action,
>> history_extra) VALUES (?, ?, ?, ?, ?, ?, ?), values:
>> 2189,horde:group:3,1302280997,user at user.com,,add, [pid 12320 on line
>> 217 of "M:xlibHordeHistory.php"]
>
> These queries is the history backend logging the successful adding
> of groups to the backend. That code is only reached if there was no
> error adding groups. That means that your groups must have been
> added somewhere. Since you seem to be able to *list* groups though,
> I can only imagine that you use a split write/read database setup,
> and the writes are not synchronized to the slave database.
We are using a single dedicated MYSQL installation. Checking the
Groups Database Tables, the entries are not added or removed
respectively when the admin action is performed
More information about the bugs
mailing list