Affects Version/s: 7.3.X
Fix Version/s: 7.3.X
When publishing Asset Vocabularies, the visibility type is not taken into account. The visibility type of the published asset vocabulary will always be Public even if the staged Asset Vocabulary's visibility type was Internal.
Note that this issue is not reproducible in master. The issue was fixed in master with
LPS-139945 (specifically, this commit). However, we cannot backport LPS-139945 as it is a Story ticket. So we must create a unique fix in 7.3.x for this issue.
Steps to Reproduce
1. Navigate to Global Menu > (Applications) Asset Libraries
2. Create a new Asset Library named ‘AL1’
3. Select ‘AL1’ (click on title) and select Categories
4. Add a new Vocabulary from left menu named ‘V1’ and set Visibility to ‘Internal’
5. Navigate back to AL1 and select ‘Staging’ and select ‘Local Live’
6. (Note that after the Initial Publication is successful, you are on ‘Staging’)
7. Navigate back to AL1 and notice the visibility on V1 on staging is public (no internal icon)
8. Navigate to live (bar at top) and select ‘Categories’. Note the visibility on V1 is internal (internal icon).
9. Navigate back to staging (bar at top) and select ‘Categories’
10. Add new Vocabulary from left menu named ‘V2’ and set Visibility to ‘Internal’
11. Publish to Live (bar at top) and note the visibility on V2 on staging is internal (internal icon).
12. Navigate to live (bar at top) and select ‘Categories’. Note the visibility on V2 is public (no internal icon).
Expected Result: The visibility of V1 and V2 would remain internal in Staging and Live, respectively.
Actual Result: The visibility of V1 becomes public in Staging, and the visibility of V2 becomes public in Live.