remove erroneous autocomplete

[antonello74]

Hi,

I have a Open Collaboration Suite Zimbra version 6.0.5.

I have create a contact on server, but i have wrong in last name. Now i have set correct last name,but in my web browser (mozilla 3) i see every bad lastname ?

Why?

I read some thread, without find a solution.

I have to delete in autcomplete bad contact, why my browser show bad contact if I update on server this contact?

Where read my browser old contact?
I have delete old contact in my contact, but i see every old contact?

My web browser don' t see update done on server?

Thanks in advance for your answer.

I want do upgrade my version to 6.0.6 , What do you say?

Regards
Antonello.

[mmorse]

Bug 40081 - Unable to get rid of emailed contact fixed in 6.0.6.1 - we no longer search mysql.zimbra.mailbox_metadata.section.CONTACT_RANK INGS (since the user can't modify it) and rely on GAL/AddressBooks (including "Emailed Contacts" folder) we just use that aforementioned table for ranking purposes of the results order.

[antonello74]

Thanks, for your answer.

Then i have to install version 6.0.6 but where i find version 6.0.6.1 ?

I have download version 6.0.6.

Thanks in advance for your answer.

Regards
Antonello.

[phoenix]

Originally Posted by antonello74

Then i have to install version 6.0.6 but where i find version 6.0.6.1 ?

Have a look in the forums for the release Announcement or download it from the normal Download page.

[antonello74]

OK,

I'm downloading version 6.0.6.1

After that I installed IT, don't have problem with autocomplete.

I say you if autocomplete work.

Thanks in advance.

Best Regard.
Antonello.

[pbrunnen]

Hello all,

We upgraded a customer to 6.0.7_GA_2476 last weekend and we are seeing the same behavior. Could the 6.0.6.1 patch have not made it into the 6.0.7 release?

[phoenix]

Originally Posted by pbrunnen

Could the 6.0.6.1 patch have not made it into the 6.0.7 release?

No, that's not likely.

[chauvetp]

We defintely had this problem pre-6.0.6.1 but have not had the problem since on 6.0.7. That's not to say its not possible, but we had a lot of users with the issue all of which were fine with it after 6.0.6.1 here.