I’m trying to use the Manage Content Button as described on @bloomreach/ng-sdk - npm
It doesn’t say it can work for Experience Manager only.
But I can’t get it to work. I want a button to show so that the editors can edit the current visible document in the preview.
Is there a way to achieve this or is the Manage Content Button only to be used when one is using the Experience Manager?
You’re saying that you use the content editor only and not the Experience Manager (a.k.a. preview), so I’m wondering what the ask is. The Manage Content Button is rendering special markup in your site implementation which is then picked up by the preview, so it lives only there.
Are you maybe asking for a button in the content perspective to open the Experience Manager with the right side panel open on that document?
Yes we’re using the content editor only and not the Exp. manager.
And when using the content editor we still can open the preview.
In the preview can navigate to other pages. So what I’m asking for is a button
that opens the content editor for the url that is currently visible in the preview.
My coworkers who edit the site would benefit greatly it that was possible.
Now they have to lookup the page they want to edit.
I’ve already figured out how to see that you’re in preview mode.
I added a link to my page. Clicking it will activate the link to the same page in the content-editor.
I use target=“_parent” in the a tag. Thus I want to open the page in the active tab so that I remain in current browser tab with the cms. That is the most logic thing to do.
Unfortenately it does not work. The preview is an iframe in which our headless FE is served. Because it is headless is has an other domain (other portnumer). Opening the link in _parent is blocked because of cross-domain security.
The only thing I can do now is open the link in a new browser tab.
Of course this is not what one want because now I open a new browser tab with the cms while I already have a browser tab with the cms.
Is there a way to overcome this issue?
If not then I again ask for a feature request to solve above problem.
BTW: I believe that using _parent as target will render URL within navapp frame,most probably you will need to use _top for the target attribute.
Regarding feature request: you can file an issue in JIRA: https://issues.onehippo.com/projects/CMS/
I am not sure how much attention it will get because this functionality is explicitly removed in favor of “in-channel/inline” editing.
ALLOW-FROM origin Deprecated
This is an obsolete directive. Modern browsers that encounter response headers with this directive will ignore the header completely. The Content-Security-Policy HTTP header has a frame-ancestors directive which you should use instead.