- Koha-bugs - lists.koha-community.org

[Bug 43639] New: Cannot use ElasticsearchMARCFormat because of too many fields
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '26

25 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43639 Bug ID: 43639 Summary: Cannot use ElasticsearchMARCFormat because of too many fields Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- This was in KTD with ES9. Set preference ElasticsearchMARCFormat to searchable array. Reindex Perform any search. Boom: [2026/09/25 16:43:57] [WARN] [Request] ** [http://es:9200]-[400] [query_shard_exception] failed to create query: field expansion matches too many fields, limit: 1024, got: 1060, with: {"index":"koha_kohadev_biblios","index_uuid":"XUtjIIh2TXWiFwf0NaAgqQ"}, [query_shard_exception] failed to create query: field expansion matches too many fields, limit: 1024, got: 1174, with: {"index_uuid":"XUtjIIh2TXWiFwf0NaAgqQ","index":"koha_kohadev_biblios"}, [query_shard_exception] failed to create query: field expansion matches too many fields, limit: 1024, got: 1069, with: {"index_uuid":"XUtjIIh2TXWiFwf0NaAgqQ","index":"koha_kohadev_biblios"}, [query_shard_exception] failed to create query: field expansion matches too many fields, limit: 1024, got: 1046, with: {"index":"koha_kohadev_biblios","index_uuid":"XUtjIIh2TXWiFwf0NaAgqQ"}, [query_shard_exception] failed to create query: field expansion matches too many fields, limit: 1024, got: 1066, with: {"index_uuid":"XUtjIIh2TXWiFwf0NaAgqQ","index":"koha_kohadev_biblios"}, called from sub Search::Elasticsearch::Role::Cxn::process_response at /kohadevbox/koha/Koha/SearchEngine/Elasticsearch.pm line 56. With vars: {'body' => {'error' => {'type' => 'search_phase_execution_exception','root_cause' => [{'index_uuid' => 'XUtjIIh2TXWiFwf0NaAgqQ','index' => 'koha_kohadev_biblios','type' => 'query_shard_exception','reason' => 'failed to create query: field expansion matches too many fields, limit: 1024, got: 1060'},{'type' => 'query_shard_exception','reason' => 'failed to create query: field expansion matches too many fields, limit: 1024, got: 1174','index_uuid' => 'XUtjIIh2TXWiFwf0NaAgqQ','index' => 'koha_kohadev_biblios'},{'index' => 'koha_kohadev_biblios','index_uuid' => 'XUtjIIh2TXWiFwf0NaAgqQ','reason' => 'failed to create query: field expansion matches too many fields, limit: 1024, got: 1069','type' => 'query_shard_exception'},{'type' => 'query_shard_exception','reason' => 'failed to create query: field expansion matches too many fields, limit: 1024, got: 1046','index' => 'koha_kohadev_biblios','index_uuid' => 'XUtjIIh2TXWiFwf0NaAgqQ'},{'type' => 'query_shard_exception','reason' => 'failed to create query: field expansion matches too many fields, limit: 1024, got: 1066','index_uuid' => 'XUtjIIh2TXWiFwf0NaAgqQ','index' => 'koha_kohadev_biblios'}],'reason' => 'all shards failed','grouped' => bless( do{\(my $o = 1)}, 'JSON::PP::Boolean' ),'failed_shards' => [{'index' => 'koha_kohadev_biblios','node' => 'j0qWhv_aT_m6BJl0W0eyRA','shard' => 0,'reason' => {'index_uuid' => 'XUtjIIh2TXWiFwf0NaAgqQ','index' => 'koha_kohadev_biblios','reason' => 'failed to create query: field expansion matches too many fields, limit: 1024, got: 1060','caused_by' => {'reason' => 'field expansion matches too many fields, limit: 1024, got: 1060','type' => 'illegal_argument_exception'},'type' => 'query_shard_exception'}},{'reason' => {'index' => 'koha_kohadev_biblios','index_uuid' => 'XUtjIIh2TXWiFwf0NaAgqQ','type' => 'query_shard_exception','caused_by' => {'reason' => 'field expansion matches too many fields, limit: 1024, got: 1174','type' => 'illegal_argument_exception'},'reason' => 'failed to create query: field expansion matches too many fields, limit: 1024, got: 1174'},'shard' => 1,'node' => 'j0qWhv_aT_m6BJl0W0eyRA','index' => 'koha_kohadev_biblios'},{'index' => 'koha_kohadev_biblios','node' => 'j0qWhv_aT_m6BJl0W0eyRA','reason' => {'type' => 'query_shard_exception','caused_by' => {'type' => 'illegal_argument_exception','reason' => 'field expansion matches too many fields, limit: 1024, got: 1069'},'reason' => 'failed to create query: field expansion matches too many fields, limit: 1024, got: 1069','index_uuid' => 'XUtjIIh2TXWiFwf0NaAgqQ','index' => 'koha_kohadev_biblios'},'shard' => 2},{'index' => 'koha_kohadev_biblios','shard' => 3,'reason' => {'type' => 'query_shard_exception','reason' => 'failed to create query: field expansion matches too many fields, limit: 1024, got: 1046','caused_by' => {'type' => 'illegal_argument_exception','reason' => 'field expansion matches too many fields, limit: 1024, got: 1046'},'index_uuid' => 'XUtjIIh2TXWiFwf0NaAgqQ','index' => 'koha_kohadev_biblios'},'node' => 'j0qWhv_aT_m6BJl0W0eyRA'},{'index' => 'koha_kohadev_biblios','shard' => 4,'reason' => {'type' => 'query_shard_exception','reason' => 'failed to create query: field expansion matches too many fields, limit: 1024, got: 1066','caused_by' => {'type' => 'illegal_argument_exception','reason' => 'field expansion matches too many fields, limit: 1024, got: 1066'},'index' => 'koha_kohadev_biblios','index_uuid' => 'XUtjIIh2TXWiFwf0NaAgqQ'},'node' => 'j0qWhv_aT_m6BJl0W0eyRA'}],'phase' => 'query'},'status' => 400},'request' => {'path' => '/koha_kohadev_biblios/_search','body' => {'size' => '20','aggregations' => {'holdingbranch' => {'terms' => {'size' => '20','field' => 'holdingbranch__facet'}},'su-geo' => {'terms' => {'field' => 'su-geo__facet','size' => '20'}},'homebranch' => {'terms' => {'size' => '20','field' => 'homebranch__facet'}},'author' => {'terms' => {'field' => 'author__facet','size' => '20'}},'ccode' => {'terms' => {'field' => 'ccode__facet','size' => '20'}},'itype' => {'terms' => {'size' => '20','field' => 'itype__facet'}},'subject' => {'terms' => {'size' => '20','field' => 'subject__facet'}},'ln' => {'terms' => {'size' => '20','field' => 'ln__facet'}},'title-series' => {'terms' => {'size' => '20','field' => 'title-series__facet'}},'location' => {'terms' => {'size' => '20','field' => 'location__facet'}}},'from' => 0,'sort' => [{'_score' => {'order' => 'desc'}},{'local-number__sort' => {'order' => 'desc'}}],'query' => {'bool' => {'must' => [{'query_string' => {'fields' => ['record-source','identifier-other','other-control-number','lc-card-number','personal-name','local-number','koha-auth-number','arp','date-entered-on-file','number-natl-biblio','musical-presentation','date-of-publication','host-item','cn-suffix','location','date-of-acquisition','report-number','author-personal-bibliography','nlm-call-number','title-abbreviated','conference-name','stack','subject','publisher','note','title-key','geographic-class','issues','replacementprice','acqsource','cn-bib-sort','bio','cn-class','control-number-identifier','udc-classification','ln-subtitle','title-other-variant','interest-grade-level','rtype','number-legal-deposit','ff7-01-02','map-scale','identifier-publisher-for-music','reading-grade-level','index-term-genre','ta','restricted','geolocation_lon','curriculum','cn-sort','lexile-number','totalissues','title-uniform','withdrawn','geolocation_lat','pl','copynumber','ln','homebranch','isbn','reserves','number-local-acquisition','host-item-number','lc-call-number','name','name-geographic','author-name-corporate','title-series','title-cover','cross-reference','record-control-number','music-key','itemtype','holdingbranch','cn-prefix','biblioitemnumber','extent','issn-all','identifier-standard','local-classification','language-original','microform-generation','llength','copydate','nal-call-number','ff8-23','ctype','number-db','related-periodical','barcode','fingerprint-identifier','provider','title-no-punctuation','arl','replacementpricedate','dewey-classification','bnb-card-number','ccode','cn-item','materials-specified','bib-level','number-govt-pub','su-geo','ff7-01','ff7-00','datelastseen','code-institution','ff7-02','renewals','title','author-name-personal','itemnumber','bgf-number','lf','dissertation-information','abstract','title-collective','damaged','classification-source','lost','subject-name-personal','coded-location-qualifier','author','coden','indexed-by','editor','ln-audio','price','itype','title-former','corporate-name','author-title','uri','ff8-29','material-type','stock-number','interest-age-level','issn','thematic-number','index-term-uncontrolled','isbn-all','current-publication-frequency','notforloan','code-geographic','title-expanded','author-in-order','not-onloan-count','datelastborrowed','date-time-last-modified','name-and-title','cn-bib-source','title-later','control-number','marc_data_array.*'],'lenient' => bless( do{\(my $o = 1)}, 'JSON::PP::Boolean' ),'type' => 'cross_fields','analyze_wildcard' => $VAR1->{'request'}{'body'}{'query'}{'bool'}{'must'}[0]{'query_string'}{'lenient'},'fuzziness' => 'auto','query' => '(cat*)','default_operator' => 'AND'}}]}}},'mime_type' => 'application/json','qs' => {'track_total_hits' => 'true'},'serialize' => 'std','ignore' => [],'method' => 'GET'},'status_code' => 400} -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 42881] New: Improve Elasticsearch Indexing performance
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '26

25 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42881 Bug ID: 42881 Summary: Improve Elasticsearch Indexing performance Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- An epic bug to collect elasticsearch (re)indexing performance improvements -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 43123] New: Hold placement workflow: Vue modernisation (epic)
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '26

25 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43123 Bug ID: 43123 Summary: Hold placement workflow: Vue modernisation (epic) Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Target Milestone: --- This is a tracking bug for a project to replace the staff interface hold placement workflow (reserve/request.pl, reserve/request.tt, js/holds.js) with a set of REST API endpoints and a Vue 3 single page application, addressing severe performance problems in the current implementation. Problem reserve/request.pl (roughly 820 lines) pre-computes holdability for every item on a record, across every policy dimension, in a single synchronous request, then renders the results through a 1600 line Template Toolkit page with jQuery interactivity (js/holds.js, roughly 1300 lines). For a 100 item biblio this produces on the order of 1800 to 2700 SQL queries in a single page load. Confirmed cost centres include: - The same item set is fetched independently by CanBookBeReserved, GetMaxPatronHoldsForRecord, request.pl's own item loop, and (when onshelfholds=2) ItemsAnyAvailableAndNotRestricted. - FixPriority (C4::Reserves) issues one UPDATE per queued hold on every create, cancel or fill. A title with 50 queued holds means 50 UPDATE statements per state change. - Club holds check each enrolled patron's hold count and balance individually, with no batching. - Pickup location computation (Koha::Biblio::pickup_locations) iterates every item and resolves branch and transfer limit rules per item. Some mitigation already exists (CanItemBeReserved and get_effective_rule_value now cache via Koha::Cache::Memory::Lite, and Koha::Biblio::pickup_locations has a per-item-shape cache), but these reduce repeat lookups within a request rather than changing the underlying O(N) shape of the computation. Proposed direction - New availability classes, Koha::Item::Availability::Hold and Koha::Biblio::Availability::Hold, load context for a (patron, biblio) pair once, then evaluate holdability for every item from memory. These follow the pattern already established by bug 41728 (Koha::Item::Availability::Checkin) and its shared Koha::Result::Availability base class, rather than inventing a bespoke schema. - Patron level pre-flight eligibility reuses the existing Koha::Patron->can_place_holds method (already in main), exposed via a new GET endpoint rather than new backend logic. - New REST endpoints expose holdability at the biblio, item, batch and patron level, so the UI asks only for what the current screen needs instead of pre-computing everything up front. - A new Vue 3 single page application replaces reserve/request.tt and js/holds.js, following the existing ERM / Preservation / Acquisitions module pattern, gated behind a new UseNewHoldsInterface system preference (default off) until feature parity is confirmed. - reserve/request.pl remains the default and fully functional throughout the migration. - Separately, Koha's Circulation Holds queue picking list report (circ/view_holdsqueue.pl) is being made API driven by bug 42503. That bug is not a Vue conversion. Once it lands, this epic includes a small follow on to render that page with Vue against the endpoint it introduces, without duplicating its REST work. This bug tracks the overall initiative. Individual patches are delivered against the bugs it depends on, listed below, each independently testable and each landing without changing default behaviour until the bug that flips the feature flag. This bug is not expected to carry a patch itself. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 42509] New: Use API to retrieve and update patrons via Batch patron deletion and anonymization tool
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '26

25 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42509 Bug ID: 42509 Summary: Use API to retrieve and update patrons via Batch patron deletion and anonymization tool Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The Batch patron deletion and anonymization tool (cleanborrowers.pl) can be slow for larger systems. It should be updated to use the API. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 42444] New: Update waitingreserves.pl to use API to fetch data
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '26

25 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42444 Bug ID: 42444 Summary: Update waitingreserves.pl to use API to fetch data Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com The Holds Awaiting Pickup page is a pain point for larger systems with many holds. We should update how it fetches, displays, and interacts with data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 86

[Bug 42443] New: Update transferstoreceive.pl to use the API to fetch transfer information
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '26

25 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42443 Bug ID: 42443 Summary: Update transferstoreceive.pl to use the API to fetch transfer information Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com The Transfers to Receive page is a pain point for larger systems with many transfers. We should update it to fetch data via API. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 59

[Bug 43616] New: Add core support for scheduled/automated patron import (RFC)
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '26

25 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43616 Bug ID: 43616 Summary: Add core support for scheduled/automated patron import (RFC) Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- This bug proposes adding native support to Koha core for scheduled, unattended patron imports -- something core currently lacks entirely. Today, Koha's patron import tooling (tools/import_borrowers.pl, misc/import_patrons.pl, Koha::Patrons::Import) is manual-trigger only. There is no way to configure a remote source and have Koha fetch and import an updated patron file on a schedule without a human clicking "import" or a hand-rolled external script. In practice, this gap has been filled by third-party plugins -- most notably koha-plugin-patrons-importer-advanced, which has real production customers depending on scheduled SFTP-sourced patron imports, including requests to run more than once per day. That plugin work highlighted exactly what's missing from core. This RFC proposes closing the gap with the same pattern Koha already uses for a very similar problem: bug 43603 (scheduled article request scan import), which polls a configured Koha::File::Transport (bug 35761) for new files and imports them, with a DB-backed idempotency log so repeated/frequent polling is safe. Proposed for core: - New tables patron_import_accounts and patron_import_log, mirroring the article_request_scan_accounts / article_request_scan_log pattern from bug 43603 (an account references a Koha::File::Transport, a matchpoint, defaults/preserve-fields, and an active flag; the log table records per-file processed/error status keyed by account and filename for idempotency). - A new admin config page, admin/patron_import_accounts.pl, modeled on admin/article_request_scan_accounts.pl, for configuring named import sources. - A new cronjob, misc/cronjobs/patron_imports.pl, modeled on misc/cronjobs/article_request_scans.pl, that polls active accounts, fetches new files via their configured file transport, and imports them via the existing Koha::Patrons::Import engine (no changes needed to the import engine itself -- this only adds scheduling/fetch infrastructure around it). This is Phase B of a small roadmap; a follow-up bug (Phase C) would apply the same pattern to scheduled patron photo import. This bug's scope is Phase B only: scheduled patron record import. No patch is attached yet. This bug is filed to open discussion on the design (in particular, whether the article-request-scan pattern from bug 43603 is the right one to reuse here) before implementation begins. Depends on: bug 35761 (Koha::File::Transport) See also: bug 43603 (article request scan import -- the precedent this design follows) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 12146] Add new ISO code column to currency sample files
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '26

25 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12146 --- Comment #15 from Martin Renvoize (ashimema) <martin.renvoize(a)openfifth.co.uk> --- Revised series (4 patches now): - Added the common currency symbol/abbreviation for each generated ISO 4217 entry (not just the four originally curated ones). - Added a 4th patch: pl-PL, ru-RU, nb-NO and uk-UA's localization/ custom.sql each insert their own region currency (PLN/UAH/RUB/NOK). Since those codes are now also in the base optional set, a locale install that selects both would hit a primary key collision on the plain INSERT and silently lose the locale's rate/symbol/active override. Switched those to INSERT ... ON DUPLICATE KEY UPDATE and set isocode on them too. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12146] Add new ISO code column to currency sample files
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '26

25 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12146 --- Comment #14 from Martin Renvoize (ashimema) <martin.renvoize(a)openfifth.co.uk> --- Created attachment 206840 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206840&action=e… Bug 12146: Set isocode on locale-specific sample currencies, and avoid collisions with the base currency set pl-PL, ru-RU, nb-NO, and uk-UA's localization/custom.sql each insert their own region-specific currencies (PLN, UAH, RUB, NOK) on top of whatever sample data set the installer user selected. Since the previous commit in this series added every active ISO 4217 code (including these four) to the base "Some basic currencies" optional dataset, an installer run in one of these locales that also selects that optional dataset would now hit a primary key collision: the locale file's plain INSERT would fail silently (load_sql just warns and moves on), leaving the generic blank-symbol/inactive row from the base set in place instead of the locale's own rate/symbol/active values. Switch these INSERTs to INSERT ... ON DUPLICATE KEY UPDATE so they correctly override the base set's entry for the same currency regardless of load order, and set isocode on each of them - the original ask of this bug, just never delivered for anything beyond the English dataset. Test plan: 1) Load installer/data/mysql/en/optional/parameters.yml, then run one of these localization/*/custom.sql files against the same database and confirm no errors and the currency ends up active with its locale-specific rate/symbol (e.g. for pl-PL: SELECT * FROM currency WHERE currency = 'PLN' should show isocode='PLN', symbol='zł', active=1) 2) Run a fresh web installer choosing the pl-PL (or ru-RU/nb-NO/uk-UA) language and the "Some basic currencies..." optional dataset, confirm the locale's currency ends up active with the right symbol -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12146] Add new ISO code column to currency sample files
by bugzilla-daemon＠bugs.koha-community.org 25 Sep '26

25 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12146 --- Comment #13 from Martin Renvoize (ashimema) <martin.renvoize(a)openfifth.co.uk> --- Created attachment 206839 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206839&action=e… Bug 12146: Add full ISO 4217 currency list to sample currency data The "Some basic currencies" optional sample dataset (installer/data/mysql/en/optional/parameters.yml) only offered four currencies (USD, GBP, CAD, EUR) and never populated currency.isocode, so every sample currency's ISO code was blank after install. Keep the existing curated set as-is (USD active by default, GBP/CAD/ EUR with their existing rates and symbols) and add the remaining active ISO 4217 currency codes as inactive options, each with isocode set to its own code and its common currency symbol/abbreviation (sourced from Wikipedia's "List of circulating currencies", with a handful of targeted lookups for entries missing there). A number of currencies legitimately share the same symbol (e.g. "$" is used by over twenty of them) - that's harmless here since only the single active currency's symbol is ever used for price formatting; the rest are purely informational in the admin currency list. Precious-metal and special codes (XAU, XAG, XPD, XPT, XTS, XXX, XDR, XBA-XBD, XSU, XUA) are excluded as they don't represent real acquisitions currencies. rate is set to a neutral 1.0 placeholder for the generated entries, since a static sample file can't hold meaningful live exchange rates for 150+ currencies. Relies on the earlier commit in this series resizing currency.isocode to CHAR(3), so every isocode value here is guaranteed to fit. Test plan: 1) Run a fresh web installer, select "Some basic currencies..." under Optional data at the Default Settings step 2) Go to Administration > Currencies & Exchange rates 3) Confirm ~154 currencies are listed, each with a 3-letter ISO code and a currency symbol, and only USD is active -- You are receiving this mail because: You are watching all bug changes.

1 0