Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.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
Issue fork private_message-3265901
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
ressinelComment #4
ressinelThis is caused an issue for updating Open Social to the newest version. It would be great to get feedback from any of the
private_messagemaintainers regarding these changes. Because we are interested in solving this problem ASAP.Comment #5
navneet0693 commentedComment #6
ShumaS commentedIssue #3265901 by Ressinel: Database update error regarding already existing configurations
it is works for me, thanks.
Comment #7
jukka792 commentedDoes not work for me,
I have patched the module, tried with 3.0 beta2 and now with dev.
cleared caches but still when trying to enable the notify module shows this:
Unable to install Private Message Notify, 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 already exist in active configuration.
Comment #8
jan kellermann commented@jukka792 you have to restore the database before trying again. And we had to remove some old modules not compatible with D9 (like kint) because them break the update-process and in 2nd try the config items where gone away.
Good luck!
Comment #9
ressinelComment #12
artem_sylchukLooks good for me, thanks!
Comment #14
dioh commentedHello,
I got the same error and tried to apply the patch but the error persisted checking the patch I noticed that the error happens because the try section (https://git.drupalcode.org/issue/private_message-3265901/-/blob/fc720ca1...) uses a $configs var but it's undefined if you don't have the notify module (https://git.drupalcode.org/issue/private_message-3265901/-/blob/fc720ca1...)
To solve that problem I moved the $configs var block where the array is defined before the first if and it worked.