That's a new one on me. I like it!
Autocomplete behaviour change between 9.0 and 10.1
-
liverpoolfcfan
- Elite member
- Posts: 1217
- Joined: Sat Sep 13, 2014 12:47 am
-
oetiker
- Outstanding Member
- Posts: 369
- Joined: Fri Mar 07, 2014 1:05 pm
- Location: Switzerland
- ZCS/ZD Version: Release 10.1.5.GA.4655.UBUNTU22_64
- Contact:
Re: Autocomplete behaviour change between 9.0 and 10.1
Hi
Answer from: July 4, 2025 9:23 PM
I like a lot about zimbra but this part not at all ...
Answer from: July 4, 2025 9:23 PM
I did escalate but nothing happens at all ... 3 Month later still no fix no plan no information ...Your case has resulted in a BUG, and you can check the status in the support portal using ZBUG-4975. When you log into your support account (in [https://support.zimbra.com] ), select Support > Bug Lookup. Here you can:
- See status and release version (if one has been assigned).
- Provide feedback, escalate, and ask for a status. If there isn't a status, the Zimbra Team will follow up with you.
I like a lot about zimbra but this part not at all ...
Re: Autocomplete behaviour change between 9.0 and 10.1
Does anyone have the patched .jar? Can we place it on publicly accessible storage without time restrictions, at least until the zbug is fixed?
-
andrey.ivanov
- Advanced member
- Posts: 57
- Joined: Wed Aug 08, 2018 8:44 am
Re: Autocomplete behaviour change between 9.0 and 10.1
Yes, i continue to maintain for our systems the patched jar according to the principles described in this thread (replacement of a single .class in the production/stock Network Edition jar).
You can compare my .jar with the stock .jar by "unzipping" the archive (with "jar xf filename.jar"). The only difference should be the file ContactAutoComplete.class contained in this archive.
I have uploaded the up-to-date file zimbrastore-patched-10.1.14.jar (to replace /opt/zimbra/lib/jars/zimbrastore.jar) here: https://filesender.renater.fr/?s=downlo ... 22350c3921
sha256sum of this file is b4a0ebe22479abe95d89a9cbd5c4ead0611d7f609cdb46402df2788290c5840e
You can compare my .jar with the stock .jar by "unzipping" the archive (with "jar xf filename.jar"). The only difference should be the file ContactAutoComplete.class contained in this archive.
I have uploaded the up-to-date file zimbrastore-patched-10.1.14.jar (to replace /opt/zimbra/lib/jars/zimbrastore.jar) here: https://filesender.renater.fr/?s=downlo ... 22350c3921
sha256sum of this file is b4a0ebe22479abe95d89a9cbd5c4ead0611d7f609cdb46402df2788290c5840e
Re: Autocomplete behaviour change between 9.0 and 10.1
Thanks adnrey for the jar and sorry for the late response but we were testing extensively.
We tested it, and our own jar with the same modification, in a multiserver installation with many domains, one of them having an External GAL configured.
We found your behaviour even in this case > while ALL accounts from external LDAP GAL are shown and appear in autocompletion.
It doesn't seems related to the jar, but to the presence of the jar on any mailstore of the isntallation, sepcifically on the mailstore where resides the account using the webmail, AND the mailstore where resides the galsync@ account.
Deploying the jar on each mailstore seems to solve the unwanted autocompletion.
We tested it, and our own jar with the same modification, in a multiserver installation with many domains, one of them having an External GAL configured.
We found your behaviour even in this case > while ALL accounts from external LDAP GAL are shown and appear in autocompletion.
It doesn't seems related to the jar, but to the presence of the jar on any mailstore of the isntallation, sepcifically on the mailstore where resides the account using the webmail, AND the mailstore where resides the galsync@ account.
Deploying the jar on each mailstore seems to solve the unwanted autocompletion.