rebuild roundcube cache

Michael Stuber mistub at gmx.net
Wed May 28 11:05:52 CEST 2014


Withdrawal. Everything is ok! After:

UPDATE kolab_folders SET ctag=NULL where type='contact';

... everything is working like a charm! Thx again.
I still wonder if there's a best practice for emptying the cache?

Best regards
Michael


Am 26.05.2014 22:09, schrieb mistub:
> Hi Thomas
>
> After:
>
> UPDATE kolab_folders SET ctag=NULL where type='contact';
>
> all contacts are showing up again, great thx! But now a formerly 
> existing mailbox in roundcube is emtpy (imap mailbox complete). I'm a 
> bit confused. Is there a possibility to emtpy the whole cache and 
> start indexing all over again for a single user? Is there a best 
> practice for this case?
>
> Best regards
> Michael
>
>
> Am 26.05.2014 08:32, schrieb Thomas Brüderli:
>> Michael Stuber wrote:
>>> Hi all
>>>
>>> Kolab 3.1 on centos
>>>
>>> After a:
>>> mysql --password=pw roundcube -e "truncate table
>>> kolab_cache_contact;truncate table cache_index;truncate table
>>> cache_messages;"
>>>
>>> no more contacts are showing up in roundcube's address books ( though
>>> mails are still in cyrus mailbox). How can I rebuild the roundcube 
>>> cache?
>> Hello Michael
>>
>> The data for determining whether the cache needs an update is stored in
>> the folab_folders table. You should also remove the entries for contact
>> folders from there or clear the ctag value of them:
>>
>>    UPDATE kolab_folders SET ctag=NULL where type='contact';
>>
>> Kind regards,
>> Thomas
>> _______________________________________________
>> users mailing list
>> users at lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users
>
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users



More information about the users mailing list