Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de 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)

Abierto
  • ¿Algo no está bien?
#7,901 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java, postgresql
Área
api, backend, databases

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Java
Estrellas
278
Forks
97
Merge medio
19 h 30 min
PR fusionados (30 d)
242

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de eclipse-dirigible/dirigible

Todos los issues de eclipse-dirigible/dirigible

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.