[MGNLPN-761] Preview as visitor doesn't work with SPA projects Created: 08/Sep/23 Updated: 23/Oct/23 Resolved: 03/Oct/23 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.10 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Alberto Cordero | Assignee: | Rishab Dhar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | 1h | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Attachments: |
|
|||||||||||||||||||||||||
| Sub-Tasks: |
|
|||||||||||||||||||||||||
| Template: | ||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
|||||||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
|||||||||||||||||||||||||
| Date of First Response: | ||||||||||||||||||||||||||
| Epic Link: | SPA Maintenance | |||||||||||||||||||||||||
| Sprint: | DevX 47 | |||||||||||||||||||||||||
| Story Points: | 2 | |||||||||||||||||||||||||
| Team: | ||||||||||||||||||||||||||
| Work Started: | ||||||||||||||||||||||||||
| Approved: |
Yes
|
| Description |
|
When you use Preview as visitor with Personas with a trait inside, p13n didn't work. You need to specify the trait in the preview as visitor app.
Attached gif can show the use case.
Steps to reproduce the issue:
https://magnolia-cms.slack.com/archives/CDF2T239Q/p1694163306718099
Regards |
| Comments |
| Comment by Christopher Zimmermann [ 13/Sep/23 ] |
|
oanh.thai I see you moved to Selected. Do yoou think any discovery is necessary? If not - could you add a Storypoint estimate and any comments about how this could be addressed? |
| Comment by Oanh Thai Hoang [ 14/Sep/23 ] |
|
czimmermann : It needs discovery |
| Comment by Oanh Thai Hoang [ 15/Sep/23 ] |
|
Hi acordero . Just a quick suggestion for you.
You can set permission Read-only in workspace Personal for anonymous role. See below:
|
| Comment by Alberto Cordero [ 15/Sep/23 ] |
|
Hi oanh.thai , It works, thank you |
| Comment by Christopher Zimmermann [ 15/Sep/23 ] |
|
The reason it still seems like a bug to me is I think this personalization feature should work in headless mode without additional configuration. (What would the documentation say - that they should give read writes to Anonomous?) Is there something we can do to make this work by default? Can we set a read-only by default on a role? The author is logged in.. so maybe they can have access to Personas? Or can the reading of the personas be made in the context of System user instead of logged in user?(So that personoas would not be available to anonymouos- but so that the persona information could be used in the processing of the content request) Similar to recent change for component inheritance.
|