social 11.1.0-rc3

Known issue

There is currently a known issue upgrading from 11.0.x versions to 11.0.3, it happens due to the new template for 'Private message notification' submodule. We are currently investigating this issue.

New installations, or upgrading from 10.3.x installations are not affected by this issue.

Important update information

Changes required from private message module

Private message module had an issue that required a module installation while upgrading from Open Social 10 to Open Social 11, this is now fixed, but we had to remove the following class: modules/social_features/social_private_message/src/SocialPrivateMessageServiceProvider.php , now this is handled by a hook on modules/social_features/social_private_message/social_private_message.module: social_private_message_private_message_notify_exclude

If you were extending this class, please make sure to migrate your code before updating to 11.0.3.

We understand that this may cause some extra work, but this was very necessary to handle the upgrade path, and unfortunately could not be solved earlier.

More information here: https://github.com/goalgorilla/open_social/pull/2756/files

Upgrade path

Our previous upgrade path required the following steps:

Steps:

1. Backup your files and database before starting;
2. Uncomment deployment_identifier from your settings file, this will make sure that Drupal’s dependency injection container will be automatically invalidated and rebuilt when the Drupal core version changes;
3. Make sure you download and enable message notify module BEFORE updating to Open Social 11.0.0, since it’s a requirement for Private Message;
4. Make sure PHP version on social_template, composer.json file is set to "php": "^7.4"
5. Remove your root composer.lock file
6. Execute: composer require goalgorilla/open_social:~11.0.0 -W
7. Execute: composer require monolog/monolog:^2.3.5 -W
8. Enable variationcache module ( necessary for group updates );
9. Make sure to execute drush updb -y or /update.php and that all updates are executed;
10. Make sure to drush cr after the update is completed;

Since private message module now has an update, we don't require to perform step 3, since it's now fixed.
We also fixed the issue that required variationcache module to be enabled after the update on step 8, it now should handle all the updates without any issues.

Bug fixes

All included in https://www.drupal.org/project/social/releases/11.0.3