Database update error regarding already existing configurations

Created on 22 February 2022, over 2 years ago
Updated 28 January 2023, over 1 year ago

Problem/Motivation

>  [error]  Configuration objects (core.entity_form_display.message.private_message_notification.default, core.entity_view_display.message.private_message_notification.default, core.entity_view_display.message.private_message_notification.mail_body, core.entity_view_display.message.private_message_notification.mail_subject, field.field.message.private_message_notification.field_message_pm_thread, field.field.message.private_message_notification.field_message_private_message, field.storage.message.field_message_pm_thread, field.storage.message.field_message_private_message) provided by private_message_notify already exist in active configuration 
>  [error]  Update failed: private_message_update_8007 

Steps to reproduce

Update private_message module from 2.0-beta17 to 3.0.0-beta2.

Proposed resolution

Before enabling the private_message_notify module, configurations, that migrated to private_message_notify, should be deleted. Also need to find the best solution how to save data that was changed in configurations for existing sites.

Remaining tasks

N/A

User interface changes

N/A

API changes

N/A

Data model changes

N/A

πŸ› Bug report
Status

Fixed

Version

3.0

Component

Code

Created by

πŸ‡ΊπŸ‡¦Ukraine Ressinel πŸ‡ΊπŸ‡¦ Rivne

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.

Production build 0.69.0 2024