Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I just tried group rc3 with the latest version of groupmedia and it works fine. I will continue researching. Have you noticed any problems? Could you please report them here?
ok, I found the usage of group_membership.roles.permissions in the view of the media overview. Will change it to the one that Group maintainer suggests
Sure ;) that was only the first commit, I will also add the update for views config to change the cache context while upgrade from alpha3 to a new version today.
I also meant that there should be a way for those who are still using group versions less than rc3 to interact with your module. So a smart way to determine which version and the proper permissions would be nice.
I just also found that the cache context in alpha3 is taken from group views access plugin. As it is changed in group it is automatically changed in the view itself. So apparently there is no need to run any updates, because the values from yaml file are also ignored when the view is inserted/updated. Also the clean install of groupmedia alpha3 worked with group rc3, because the view calculates the cache metadata on the fly with View::calculateCacheMetadata() method.
I think we should wait a bit with this change, because it has no influence at the module now. I did a clean install (with old context in yaml file of the view) and tried to export the view again and it already had the correct cache context because it was recalculated by the method above.
Comments
Comment #2
a.dmitriiev commentedThank you for the report. I will try to check this issue asap.
Comment #3
a.dmitriiev commentedI just tried group rc3 with the latest version of groupmedia and it works fine. I will continue researching. Have you noticed any problems? Could you please report them here?
Comment #4
a.dmitriiev commentedok, I found the usage of group_membership.roles.permissions in the view of the media overview. Will change it to the one that Group maintainer suggests
Comment #6
socialnicheguru commentedBut please check the version of the group module used.
After rc3 it is one way and before that it is another.
Comment #7
a.dmitriiev commentedSure ;) that was only the first commit, I will also add the update for views config to change the cache context while upgrade from alpha3 to a new version today.
Comment #8
socialnicheguru commentedI also meant that there should be a way for those who are still using group versions less than rc3 to interact with your module. So a smart way to determine which version and the proper permissions would be nice.
Comment #9
a.dmitriiev commentedI just also found that the cache context in alpha3 is taken from group views access plugin. As it is changed in group it is automatically changed in the view itself. So apparently there is no need to run any updates, because the values from yaml file are also ignored when the view is inserted/updated. Also the clean install of groupmedia alpha3 worked with group rc3, because the view calculates the cache metadata on the fly with View::calculateCacheMetadata() method.
I think we should wait a bit with this change, because it has no influence at the module now. I did a clean install (with old context in yaml file of the view) and tried to export the view again and it already had the correct cache context because it was recalculated by the method above.
Comment #11
a.dmitriiev commentedAccording to the related issue https://www.drupal.org/project/groupmedia/issues/3078864 I was wrong, so alpha4 has update path to recalculate the contexts of the view.
New version will be released in 5 minutes.
Comment #12
a.dmitriiev commented