Themes dependencies for theme engine are not checked before installing a theme

Is this still relevant for Drupal 10 or later?

Since we need more information to move forward with this issue, I am keeping the status at Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

I think what this actually needs is manual testing of whether it still happens. The IS includes all the info needed to perform manual testing, so PMNMI doesn't seem quite correct. Thanks!

Yes, I agree it needs manual testing. However, I chose PMNMI because, for me, the issue summary does not explain how to manually test this so I was not able to do so. Therefor, I choose to ask if it was still valid.

I am changing that status back to PMNMI as a way to ask for the steps to reproduce.

There isn’t a straightforward way to test this because additional theme engines beyond Twig aren’t really being used (at least in the open), and as far as I know, there aren’t any open-source themes that utilize a different engine. If you do want to try to reproduce this, you could add an empty page.tpl.php file to the Stark theme’s templates directory, then switch the theme engine to phptemplate with engine: phptemplate in the info.yml.

• If phptemplate is present, the page.tpl.php template should return empty.
• If phptemplate is not present, Drupal will fall back to the core page.html.twig template instead.

The fact that it was possible to install Stark even when the theme engine was missing is problematic because if that engine isn't actually available, Drupal ends up using the default Twig templates instead of the ones provided by the theme, which would result in a broken experience.

So should this be reopened or closed out?