DB upgrade to private_message 3.x beta 2 from private_message 2.x beta 18 fails because configuration obects of message notify already exists

Created on 28 January 2023, almost 2 years ago
Updated 28 April 2023, over 1 year ago

Problem/Motivation

When you have installed private_message 2.x beta 18 and upgrade to private_message 3.x beta 2 you receive following error when performing drush updb and let db update 8007 - Enable notifications submodule fire:

[notice] Update started: private_message_update_8007
>  [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, message.template.private_message_notification) provided by private_message_notify already exist in active configuration 
>  [error]  Update failed: private_message_update_8007 
 [error]  Update aborted by: private_message_update_8007 
 [error]  Finished performing updates. 

The message notify module is required as dependency of message 2beta18.

Proposed resolution

Make notification via email etc optional in general. E.g. my site has it's own notification workflow based on message module, which doesn't make use of message notify. But I have to install it as an dependency.

🐛 Bug report
Status

Closed: duplicate

Version

3.0

Component

Code

Created by

🇩🇪Germany dercheffe Sersheim, Germany

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

Comments & Activities

Production build 0.71.5 2024