- Issue created by @damondt
- 🇺🇸United States damondt
@cilefen It's not rendered twice on the page, where I encountered this and in the related issues where this is mentioned the only step to reproduce is that it go through the render process, being output on a page isn't a requirement to reproduce.
- Status changed to Postponed
8 months ago 7:33am 30 March 2024 - 🇮🇳India naveenvalecha New Delhi
@damondt,
I tried to replicate it on standard profile with olivero as frontend theme and claro as backend theme. I am not able to reproduce it. Can you share the steps to reproduce it?
- 🇺🇸United States damondt
@naveenvalecha The issue description contains all steps to reproduce. To provide it more verbose and in list form:
- add a webform reference field to an entity bundle (ie content type)
- add an entity (ie node), select a webform for that reference field, and save the entity
- enable metatags for that entity type and set the meta description to a token that will render the webform (ie the default [node:summary])
- ensure that field is output for the view mode you will view the entity in (ie default) and view the entity
- Status changed to Active
8 months ago 8:59pm 2 April 2024 - 🇺🇸United States damondt
The issue tag "needs tests" is for when code has been written but it needs tests, removing tag and changing back to "active".
- 🇮🇳India naveenvalecha New Delhi
@damondt I'm not able to reproduce with the above steps. Can you add a failed tests to confirm it?
- 🇺🇸United States jrockowitz Brooklyn, NY
Conceptual this issue is starting to make sense because if a webform is rendered twice, you would get duplicate submissions.
- 🇺🇸United States jrockowitz Brooklyn, NY
Marking this critical because if this issue impacts a site, it is a critical issue.
- 🇺🇸United States damondt
Update: it appears having confirmation type of inline may be requirement to reproduce