From d10960922eaed83b17182fc5872db6d881f8a52f Mon Sep 17 00:00:00 2001
From: =?utf8?q?Tim=20D=C3=BCsterhus?= <duesterhus@woltlab.com>
Date: Mon, 8 May 2023 16:13:52 +0200
Subject: [PATCH] Enforce the selection of a landing page for WoltLab Suite
 Core in applicationManagement

This is enforced in the template only, because the PHP logic already needs to
handle a NULL landing page, as the global landing page could be deleted or
uninstalled. It will implicitly fall back to the ArticleList then.

Resolves #4843
---
 .../install/files/acp/templates/applicationManagement.tpl    | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/wcfsetup/install/files/acp/templates/applicationManagement.tpl b/wcfsetup/install/files/acp/templates/applicationManagement.tpl
index 2f53269816..6037473332 100644
--- a/wcfsetup/install/files/acp/templates/applicationManagement.tpl
+++ b/wcfsetup/install/files/acp/templates/applicationManagement.tpl
@@ -98,8 +98,9 @@
 								<small>{$application->getPageURL()}</small>
 							</td>
 							<td class="columnText columnLandingPageID">
-								<select name="landingPageID[{$application->packageID}]">
-									<option value="0">{lang}wcf.acp.application.landingPage.default{/lang}</option>
+								<select name="landingPageID[{$application->packageID}]" required>
+									<option value="">{lang}wcf.global.noSelection{/lang}</option>
+									<option value="0"{if $application->getAbbreviation() !== 'wcf'}{if $application->landingPageID === null} selected{/if}{else} disabled{/if}>{lang}wcf.acp.application.landingPage.default{/lang}</option>
 									
 									{foreach from=$pageNodeList item=pageNode}
 										{if !$pageNode->isDisabled && !$pageNode->requireObjectID && !$pageNode->excludeFromLandingPage}
-- 
2.20.1