COU-310 - Member groups/public access entries failing to get assigned to content on uaas deploy

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.

1 Attachments


Claus Jensen 12 May 2016, 08:20:50


'''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.

Morten Christensen 12 May 2016, 10:36:40

Minor detail - the Access Entry listed when transferring content is kinda floating by itself. See attached screenshot.

Morten Christensen 12 May 2016, 12:42:09

Moved to rework for now. Waiting with the 7.2.8 until the update part has been fixed.

Claus Jensen 13 May 2016, 11:51:21

Fixes for multiple member groups in access entries, fixed removal of public access, and also fixed the missing header in the deploy dialog.

Morten Christensen 19 May 2016, 08:43:03

Works perfectly. Tried all the same scenarios and everything works as expected. Well done :)

Priority: Normal

Type: Bug

State: Fixed




Backwards Compatible: True

Fix Submitted:

Affected versions: 2.52.3, 2.52.4

Due in version: 2.52.5

Sprint: Sprint 33

Story Points: 2.5