- Issue created by @zenimagine
- π·π΄Romania claudiu.cristea Arad π·π΄
A notable change is the member selector, see https://www.drupal.org/project/private_message/releases/4.0.0-alpha1 β
There's no need for upgrade path but the change of member selector might need some work, such as using a module like https://www.drupal.org/project/tagify β to get nice autoselect & chips
- π«π·France zenimagine
Ok thanks for the answer. Currently version 3.0.6 is installed on my website. Can I update to version 4.0.0-alpha2 without breaking the website, with :
composer require 'drupal/private_message:^4.0@alpha'
drush updb
drush cr
- π«π·France zenimagine
Sorry to open the question but I don't have an answer to my comment #3
- π·π΄Romania claudiu.cristea Arad π·π΄
I saw no question mark in #3 so I assumed itβa affirmative statement.
Yes, try that but make sure you understand the changes made to user selector and potential needed work
- π³π±Netherlands eelkeblok Netherlands π³π±
Part of the confusion might be π 3.0.6 was released from the 4.0.x branch Active .
- π·π΄Romania claudiu.cristea Arad π·π΄
Wow, @eelkeblok, thank you for catching that. It was a terrible mistake on my side. Created 3.0.7, this time out of 3.0.x
- π³π±Netherlands eelkeblok Netherlands π³π±
@zenimagine To answer your question, I'd say it should be fine to update to 4.0, since you inadvertently were on 4 already, having installed 3.0.6. Can you set this issue to "Fixed" if your questions are answered?
@claudiu.cristea Yeah, I'm a big fan of visual Git clients, basically for reasons such as this. It becomes trivially obvious when you are always confronted with the commit graph, whereas this is a very easy mistake to make when just coming at it from the command line (not saying it is impossible to happen, of course, one can "miss-click" as well π).