The ability to subscribe to email notifications for updated, added, etc. web content assets is present in a non-staged environment (the "subscribe" star); but in environments with staging enabled, users are unable to subscribe to changes made to the content, as the feature is no longer present.
This is due to the scopeGroupId being used during permission checks. The scopeGroupId points to the live site, which user's aren't granted to subscribe permission to. Instead, we may need to use the staging group or possibly something else entirely.
Issue seems related to
LPS-54837, which was fixed.
Steps to Reproduce
1. Create two sites ("Non-staged Site" and "Staged Site"), and enable staging for the Staged Site
2. Create a regular role "Basic Role" and give it the following permissions (in Define Permissions: Site Administration > Content > Web Content):
-Web Content: Access in Site Administration
-Web Content > Web Content: Subscribe
-Web Content > Web Content: View
-Web Content > Web Content Folder: Subscribe
-Site Settings > Site: View Site Administration Menu (This one is automatically added when saving the above permissions)
3. Create a user "Basic User," give him the Basic Role, and assign him to the two sites
4. Sign out, sign in as Basic User, and navigate (once on each site) to [Site_Administration] > Content > Web Content > "i"
Results of Testing
Expected Result: The "subscribe" star would be present in both sites for users to receive email subscriptions for web content changes
Actual Result: The "subscribe" star is present for the Basic User within the Non-staged site, but is missing within the Staged site
LPS-103282 Subscribe star not present in Remote Staging's live site
- Testing discovered
LPS-103412 Web Content not present for non-admin user with permission
LPS-103413 Omni-admin did not receive any emails when the content was modified in Remote's Staging's site