Contrib.social

Wrong field encoding type in vwebform_submission_log

Open on Drupal.org →
Created on 25 May 2022, over 2 years ago
Updated 15 October 2024, 3 months ago

Problem/Motivation

When using webform in non ascii language the insertion of a new log into webform_submission_log generate an error.

the "operation" is "email planifié"
operation is ascii_general_ci

generate a :
Drupal\Core\Entity\EntityStorageException : SQLSTATE[HY000]: General error: 1366 Incorrect string value: '\xC3\xA9' for column 'operation' at row 1: .................... web/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php).

Steps to reproduce

Create a scheduled mail handler & try to creaate a submission

Proposed resolution

Quick and dirty : Rename "email planifié" to "email planifie"
Better: Either control the validity of the passed string or change the table field encoding

🐛 Bug report
Status

Fixed

Version

6.1

Component

Code

Created by

🇨🇭Switzerland mkalbere

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.

  • Comment 3 months ago →
    🇬🇧United Kingdom em-fast1

    Hi,

    We're getting this error on 6.2.7:

    The following updates are pending:

    webform_submission_log module :
    8001 - Issue #3282363: Wrong field encoding type in vwebform_submission_log.

    Do you wish to run all pending updates? (y/n): y
    Cannot change the definition of field 'webform_submission_log.operation': field doesn't [error]
    exist.
    Performing webform_submission_log_update_8001 [ok]
    Failed: Cannot change the definition of field 'webform_submission_log.operation': field [error]
    doesn't exist.
    Cache rebuild complete. [ok]
    Finished performing updates.

    Do I need to create the field 'webform_submission_log.operation' ? webform was installed with composer. I see the dev version is older than 6.2.7 - so moving to dev shouldn't help, right? We are using core 10.3 - would upgrading to 6.3 resolve this, and can 6.3 be used well enough currently? thanks

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024