fix_roundcube_collected_addresses.sql
Description
After upgrading YetiForce CRM to version 7.2.1, the Roundcube webmail module's address autocomplete stops working. When composing a new message, no contacts are suggested in the "To" field — the suggestion list is always empty.
Root Cause
The Roundcube library bundled with YetiForce 7.2.1 expects a type column in the roundcube_collected_addresses and roundcube_contacts tables. This column is missing after an in-place upgrade because the database migration did not add it.
The affected query in rcube_addresses::list_records() and search() is:
WHERE `user_id` = ? AND `type` = ?
When the type column does not exist, the query fails silently and returns an empty result set, causing ksearch_query_results([], ...) to be returned to the browser with no suggestions.
Affected Versions
- YetiForce CRM 7.2.1 (upgraded from earlier versions)
- Roundcube bundled with YetiForce (
custom/roundcube)
Fix
A migration script has been provided that safely adds the missing type column to both affected tables. It is idempotent (safe to run multiple times) and uses DATABASE() so it works regardless of the database name.
Run:
mysql -u root YOUR_DATABASE_NAME < fix_roundcube_collected_addresses.sql
See the attached SQL migration file for details.
fix_roundcube_collected_addresses.sql
Description
After upgrading YetiForce CRM to version 7.2.1, the Roundcube webmail module's address autocomplete stops working. When composing a new message, no contacts are suggested in the "To" field — the suggestion list is always empty.
Root Cause
The Roundcube library bundled with YetiForce 7.2.1 expects a
typecolumn in theroundcube_collected_addressesandroundcube_contactstables. This column is missing after an in-place upgrade because the database migration did not add it.The affected query in
rcube_addresses::list_records()andsearch()is:When the
typecolumn does not exist, the query fails silently and returns an empty result set, causingksearch_query_results([], ...)to be returned to the browser with no suggestions.Affected Versions
custom/roundcube)Fix
A migration script has been provided that safely adds the missing
typecolumn to both affected tables. It is idempotent (safe to run multiple times) and usesDATABASE()so it works regardless of the database name.Run:
mysql -u root YOUR_DATABASE_NAME < fix_roundcube_collected_addresses.sqlSee the attached SQL migration file for details.