- Issue created by @hartsak
- 🇫🇮Finland heikkiy Oulu
Hi @hartsak.
Thank you for the message. Yes, the old implementation for the settings was a bit confusing and we also mixed them a bit when we were trying to figure out how to support both v1 and v2. Sorry for the bad UX that originally caused this issue.
I think in the process we initially thought that people by default have been using v1 and we didn't want to suddenly switch the default to v2 without them acknowleding any other change they might need to do for example in the Cookie information template.
The change should be still be visible in the config that you see the correct v1 or v2 version so the change should be pretty easy to catch.
I am trying to think if you should in the future enforce v1 or v2 if both have been selected before.
- Merge request !22Issue 3377306 Change GCM v2 to be default if the setting has been enabled before. → (Merged) created by heikkiy
- Merge request !23Issue 3377306 Change GCM v2 to be default if the setting has been enabled before. → (Closed) created by heikkiy
- 🇫🇮Finland heikkiy Oulu
I think this change could be done for both the new 2.2.x and previous 2.1.x branches. I will make a MR for both.
Then we could release 2.1.5 and 2.2.1 with the small backward compatibility fix.
- Merge request !25Issue 3377306 Change GCM v2 to be default if the setting has been enabled before. → (Merged) created by heikkiy
- 🇫🇮Finland heikkiy Oulu
Merged to both 2.1.x and 2.2.x. Credited the fix to you.
Automatically closed - issue fixed for 2 weeks with no activity.