Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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)

オープン
  • 何か問題がありますか？
#7,901 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
78/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
java, postgresql
領域
api, backend, databases

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Java
スター
278
フォーク
97
平均マージ
19時間 30分
マージ済み PR（30日）
242

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

eclipse-dirigible/dirigible のほかの issue

eclipse-dirigible/dirigible の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。