Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

print: the tenant key DIRIGIBLE_PRINT_TEMPLATE_<ENTITY>_<LANG> does not select a tenant template - standard-custom stays unprinted, the newest shipped version prints (14.88.0, #7755)

Aperta
  • Qualcosa non va?
#7,901 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
78/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
java, postgresql
Ambito
api, backend, databases

Direzione di ricerca

Start with PrintTemplateSelection.get and trace how TenantConfigurationInitFilter.resolveInjectableForCurrentTenant populates the thread configuration, then inspect the DIRIGIBLE_PRINT_TEMPLATE_ handling in TenantConfigurationKeyPolicy. Reproduce through the SalesInvoice template-list and print endpoints, including the tenant configuration update. The work is done when standard-custom is active and renders for the migrated template while the shipped version remains selectable, with the BusinessIntents STA coverage verifying tenant selection.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

What happens

On 14.88.0 (PostgreSQL, Cognito, single tenant, DIRIGIBLE_MULTI_TENANT_MODE=false), the first boot migrated a customised legacy Templates/SalesInvoice/Print/en/standard.print. Two things are as documented:

  • it is kept as standard-custom (derived-from: standard@legacy);
  • GET /services/core/configurations/tenant lists DIRIGIBLE_PRINT_TEMPLATE_SALESINVOICE_EN = standard-custom.

But:

  • GET /services/print/SalesInvoice/templates?lang=en reports [email protected] as active, and standard-custom as not active;
  • POST /services/print/SalesInvoice?lang=en with no template parameter renders the shipped layout. Its byte size equals that of [email protected] (37 387), not that of template=standard-custom (37 308);
  • PUT /services/core/configurations/tenant {"key":"DIRIGIBLE_PRINT_TEMPLATE_SALESINVOICE_EN","value":"standard-custom"} answers 2xx, but the catalogue and the print stay on [email protected].

The same holds for all 16 migrated copies: 8 documents × en/bg, each with key=standard-custom and active=standard@<shipped>.

Expected (#7755 / PR #7763)

"Resolution: the template request parameter, then the configuration, then the newest shipped version". The migration's own selection (standard-custom) should print until the tenant picks the shipped version, and re-selecting standard-custom should be the rollback.

Where to look

PrintTemplateSelection.get reads Configuration.get(key) from the thread configuration that TenantConfigurationInitFilter fills (resolveInjectableForCurrentTenant, prefix DIRIGIBLE_PRINT_TEMPLATE_ in TenantConfigurationKeyPolicy). On this instance the stored value never reaches the resolution, for the list endpoint or for the render.

Evidence

BusinessIntents STA suite on solution-all 1.31.0 (Gaia/Rhea 14.88.0). Row the tenant key decides which SalesInvoice layout prints reported:
before=standard-custom shipped=37387 custom=37308 ; key=standard-custom [email protected] [email protected] ; [email protected] [email protected] [email protected]
(runs 39005114253 and 39009837889 of BusinessIntents/businessintents-aws, sta-suite.yaml).

Impact

Tenants already print the new shipped layout, which is harmless for us. However, no tenant can select a tenant template, so a customised layout cannot be chosen and the documented rollback does not work.

Lingua principale
Java
Stelle
278
Fork
97
Merge medio
18h 53m
PR unite (30g)
228

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di eclipse-dirigible/dirigible

Tutte le issue di eclipse-dirigible/dirigible

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.