We have moved to GitHub Issues
Created by Claus Jensen 11 Apr 2016, 09:57:57 Updated by Morten Christensen 02 Jun 2016, 08:30:04
Relates to: COU-323
Member groups and public access entries are deployed but it seems like they either aren't resolved correctly or not getting assigned to content on the destination. Need to look into what is happening here.
Some related notes on COU-290.
'''Suggestion for tests:'''
Deploy a content node with public access on 7.4.3 and ensure the public access entry is transferred. Note that member groups are transferred by git on uaas, so keep your environments in sync.
Deploy a content node with public access on 7.2.8 (where it's using access.config) and ensure that the access.config is transferred and translated correctly to the new node IDs on the destination.
Test on both UAAS site and local Courier sites.
Minor detail - the Access Entry listed when transferring content is kinda floating by itself. See attached screenshot.
Moved to rework for now. Waiting with the 7.2.8 until the update part has been fixed.
Fixes for multiple member groups in access entries, fixed removal of public access, and also fixed the missing header in the deploy dialog.
Works perfectly. Tried all the same scenarios and everything works as expected. Well done :)
Backwards Compatible: True
Affected versions: 2.52.3, 2.52.4
Due in version: 2.52.5
Sprint: Sprint 33
Story Points: 2.5