The new condition added for google tag code insertion does not work

Created on 15 June 2020, over 4 years ago
Updated 9 August 2023, over 1 year ago

Currently the webform condition comes with missing context and it throws MissingValueContextException So, all the remaining condition checks does not work.

💬 Support request
Status

Closed: duplicate

Version

2.0

Component

Code

Created by

🇮🇳India rakshith.thotada

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇮🇳India shabana.navas

    I'm seeing this now on the latest 2.0 version. I'm continuously getting the `MissingValueContextException` exception for the Group and Webform modules even when not setting the condition at all for these modules. I had to downgrade to the 8.x version in order for this module to work.

  • 🇮🇳India smitghelani Surat, Gujarat

    Created patch for added condition to avoid missing value exception for web-form submission.

  • Assigned to nginex
  • Status changed to Needs work over 1 year ago
  • 🇺🇦Ukraine nginex

    This is something that can be reproduced.

    Just save a google tag container entity and see there there are bunch of conditions saved to the config entity, but ideally it should save only configured conditions. Default (untouched) conditions should not be stored in the config. The issue is happening when calling $entity->getInsertionConditions() and there are checks for default (untouched) conditions.

    There reason is quite clear (negate is saved in wrong format), the way how conditions are saved is not ok. I know how to fix it.

  • Issue was unassigned.
  • Status changed to Closed: duplicate over 1 year ago
Production build 0.71.5 2024