Hide Revision Field tries to run automatic entity updates for unrelated entities; error can surface in Update aborted by: hide_revision_field_update_8201 and 8202

Created on 12 April 2024, 3 months ago
Updated 19 April 2024, 2 months ago

Problem/Motivation

Acknowledging that we are five years late running these updates, we are hitting these errors:

> [notice] Update started: hide_revision_field_update_8201
> [error] The SQL storage cannot change the schema for an existing field (word in search_api_synonym entity) with data.
> [error] Update failed: hide_revision_field_update_8201
[error] Update aborted by: hide_revision_field_update_8201

Although several intermediate errors were not actually related to Hide Revision Field, but it looks like similar things may have been fixed in #2999401: v2.0 is incompatible with Field Group module β†’ and #3008217: Error by update.php β†’

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States mlncn Minneapolis, MN, USA

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

Comments & Activities

  • Issue created by @mlncn
  • πŸ‡ΊπŸ‡ΈUnited States mlncn Minneapolis, MN, USA

    in function hide_revision_field_apply_updates() Hide Revision Field seems to be processing fields that it is none of its business to process? It loads every field of every type of entity.

  • ivnish Poland

    This code looks buggy. I think it will be easier and faster uninstall module and install again :)

  • πŸ‡ΊπŸ‡ΈUnited States mlncn Minneapolis, MN, USA

    All right if acbramley had been listened to four years ago β†’ i'd have avoided a few days of intermittent Drupal upgrade pain:

    I'd highly recommend you revert this and instead specifically install the fields that this module is interacting with. What's currently committed is basically what was removed from core - automatic entity updates. This could cause issues on sites with other definitions that are out of whack and could in extreme cases lead to data loss.

    Surprised this did not bite more people able to find there way to this issue queue.

Production build 0.69.0 2024