Problem/Motivation

The webform tabs

  • View: /webform/my-webform
  • Test: /webform/my-webform/test

are currently rendered in admin theme.

But typically you'll want to use the webform in the frontend, so for styling purpose and realistic preview it would make sense to render these two routes in the frontend theme and not the admin theme.

Of course, webform submission, settings, etc. should be kept in the admin theme.

My personal opinion is that this should generally use the frontend theme, but if this should be configurable, I think a setting would make sense at /admin/structure/webform/config/advanced.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

anybody created an issue. See original summary.

cilefen’s picture

Category: Bug report » Feature request
liam morland’s picture

Status: Active » Postponed (maintainer needs more info)

Are you sure you don't have something else that is changing the theme on your site? I just checked a simple site and the view and test where both in the front-end theme. Build, etc. are in the admin theme.

anybody’s picture

Thanks for the feedback and check @liam morland. Well nothing I know about at least. That's really strange.
Have you enabled "Use the administration theme when editing or creating content" at /admin/appearance

Perhaps that makes the difference? I'll also ask @thomas.frobieter if he has any idea why that happens in our case maybe, but I wouldn't have created this issue if I saw a custom reason. =/

liam morland’s picture

Yes, I have "Use the administration theme when editing or creating content" enabled.

liam morland’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

No reply in two months; presuming fixed.

anybody’s picture

This is still an issue for us, but only happens if the URL starts with /webform/ - so it seems to be handled as admin path somehow.

The workaround is simply using a custom URL without /webform/ in the URL. If anyone has an idea why it's treated as admin path, that would be helpful.

Still this can be kept closed, as we have a clear and feasible workaround.