>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3592401. --> Reported by: [ckng](https://www.drupal.org/user/16307) Related to !1 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The 1.x implementation hooks into <code>kernel.request</code> to detect archived<br> content, which has several issues:</p> <ul> <li>It manually parses the request URI to extract the node ID, which is<br> fragile and bypasses Drupal's routing system.</li> <li>It only triggers on moderated nodes in the configured archived state &mdash;<br> non-moderated unpublished nodes are silently ignored.</li> <li>It also incorrectly serves a 410 for any unpublished node regardless of<br> moderation state, including drafts that may be published later.</li> <li>It throws a <code>GoneHttpException</code> directly without rendering a response<br> body, so the 410 page is a blank response.</li> <li>There is no way to configure a custom 410 page; the response body is<br> always empty.</li> <li>Config schema is missing entirely, causing schema validation errors.</li> <li>The install config key (<code>site_410</code>) does not match what the settings<br> form reads and writes (<code>page.410</code>), so the configured value is never<br> saved correctly.</li> <li>The <code>moderation_state</code> setting is not exposed in the settings UI,<br> requiring manual config management to change it.</li> <li><code>core_version_requirement</code> is <code>^8 || ^9</code>, blocking installation on<br> Drupal 10 and 11.</li> </ul> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Install the module on a Drupal site with Content Moderation enabled.</li> <li>Create a node with moderation state set to "archived" and unpublish<br> it.</li> <li>Visit the node as an anonymous user &mdash; the 410 response has no body.</li> <li>Create an unpublished node on a content type <em>without</em> a moderation<br> workflow &mdash; anonymous users receive a 403 instead of 410.</li> <li>Create a node in "Draft" state &mdash; anonymous users incorrectly receive a<br> 410 instead of 403, signalling permanent removal to search engines.</li> <li>Configure a custom 410 page path in the settings form and save &mdash; the<br> value is not persisted due to the config key mismatch.</li> <li>Attempt to install on Drupal 10 or 11 &mdash; blocked by<br> <code>core_version_requirement</code>.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li>Switch from <code>kernel.request</code> to <code>kernel.exception</code> event subscriber,<br> intercepting <code>AccessDeniedHttpException</code> on node routes &mdash; this reuses<br> Drupal's routing and access system rather than reimplementing it.</li> <li>Fix the 410 trigger logic: serve 410 only for moderated nodes in the<br> configured archived state, or non-moderated unpublished nodes. Draft<br> and other non-archived moderated nodes correctly fall through to 403.</li> <li>Render the 410 response via a subrequest so the response body is<br> populated, with cacheability metadata correctly propagated from the<br> exception and the error page. Mirrors the pattern used by core's<br> <code>CustomPageExceptionHtmlSubscriber</code>.</li> <li>Add support for a configurable custom 410 page path, with access<br> checking before the subrequest is made.</li> <li>Add a built-in fallback 410 controller and route (<code>/system/410</code>) for<br> when no custom path is configured, mirroring core's<br> <code>system.404</code> pattern.</li> <li>Add a <code>page__410</code> theme suggestion via OOP<br> <code>hook_theme_suggestions_page_alter()</code>, allowing themes to provide a<br> <code>page--410.html.twig</code> template.</li> <li>Expose the <code>moderation_state</code> setting as a select field in the settings<br> UI, populated from all content moderation workflows on the site.</li> <li>Add an optional 410 logging setting, writing notices to a dedicated<br> <code>archived_410</code> log channel to distinguish module-served 410s from the<br> core-logged 403 that precedes them.</li> <li>Add config schema (<code>config/schema/archived_410.schema.yml</code>) and fix the<br> install config key to match the schema.</li> <li>Update <code>core_version_requirement</code> to <code>^10 || ^11</code>.</li> <li>Add full Drupal coding standards docblocks and fix all PHPCS<br> violations.</li> <li>Rewrite README to the official drupal.org standard format.</li> </ul> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li><del>Review and test on Drupal 10 and 11.</del></li> <li><del>Add a Twig template for the built-in 410 page (<code>archived_410</code> theme hook).</del></li> <li>Write automated tests (kernel test for the event subscriber).</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>The admin settings page at<br> <strong>Administration &raquo; Configuration &raquo; System &raquo; Archived 410</strong><br> (<code>/admin/config/system/archived-410</code>) is expanded with three fields:</p> <ul> <li><strong>Archived moderation state</strong> &mdash; select populated from all content<br> moderation workflows on the site (previously only configurable via<br> config management).</li> <li><strong>Default 410 (gone) page</strong> &mdash; internal path to a custom 410 page body;<br> leave blank to use the built-in generic response.</li> <li><strong>Log 410 responses</strong> &mdash; checkbox to enable per-request notices in the<br> <code>archived_410</code> dblog channel.</li> </ul> <h3 id="summary-api-changes">API changes</h3> <p>The event subscriber now listens on <code>KernelEvents::EXCEPTION</code> (priority 50)<br> instead of <code>KernelEvents::REQUEST</code> (priority 34). The method is renamed from<br> <code>onRequestArchivedContent()</code> to <code>onException()</code>. Code that referenced the<br> old event or method directly will need updating.</p> <p>The following injected services have changed:</p> <ul> <li>Removed: <code>EntityTypeManagerInterface</code>, <code>BareHtmlPageRendererInterface</code>,<br> <code>TranslationInterface</code>, <code>RequestStack</code></li> <li>Added: <code>RouteMatchInterface</code>, <code>HttpKernelInterface</code>,<br> <code>AccessManagerInterface</code>, <code>UrlMatcherInterface</code>,<br> <code>RedirectDestinationInterface</code>, <code>LoggerInterface</code> (via dedicated<br> <code>logger.channel.archived_410</code> service)</li> </ul> <h3 id="summary-data-model-changes">Data model changes</h3> <p>The configuration object <code>archived_410.settings</code> gains three keys:</p> <ul> <li><code>moderation_state</code> (string) &mdash; the archived state name; defaults to<br> <code>archived</code>.</li> <li><code>page.410</code> (string) &mdash; the custom 410 page path; empty by default.</li> <li><code>enable_logging</code> (boolean) &mdash; whether to log 410 responses; defaults to<br> <code>false</code>.</li> </ul> <p>The flat <code>site_410</code> key used in 1.x was never correctly persisted and is<br> removed. A config schema file is added for the first time.</p>