Error shown when using the page include macro in Confluence: "Unable to render {include} The included page could not be found."
プラットフォームについて: Data Center - この記事は、Data Center プラットフォームのアトラシアン製品に適用されます。
このナレッジベース記事は製品の Data Center バージョン用に作成されています。Data Center 固有ではない機能の Data Center ナレッジベースは、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。
*Fisheye および Crucible は除く
問題
- When a page contains the Include Page Macro
- When the Include Page Macro includes a page from another space
診断
- Try to login with an Administrator account (member of confluence-administrators group), make sure that you have the permission to view both the page that has the Include Page Macro, as well as the page that is being included.
- Make sure the Page to Include parameter is correct, with this convention: spaceKey:PageName
If you checked both of these, and still the problem persists, proceed to the resolution.
原因
- This error is typically caused by permissions.
- Versions prior to Confluence 6.14 may be caused by this bug: CONFSERVER-36851 'Unable to render include The included page could not be found.' message displayed for include-page macros after upgrading Confluence
If the error message is no longer displayed when you are logged in with the Administrator account, it is likely that the error is shown as a result of permissions. That is, the user seeing the error does not have permission to see the included page content. From that user's POV, the content does not exist, so the message is correct.
Currently there is no way to suppress the error message. There is a feature request for this ability: CONFSERVER-5436 Add capability to turn off include error message and make note of this in Conf user guide/admin guide docs
ソリューション
- Update page permissions to ensure the user has permissions to the page that is included.
- If affected by CONFSERVER-36851 'Unable to render include The included page could not be found.' message displayed for include-page macros after upgrading Confluence, follow the workaround from the bug, or upgrade Confluence.