8000 [ExperienceFragment] "Edit in New Tab" action does not work · Issue #269 · adobe/aem-guides-wknd · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[ExperienceFragment] "Edit in New Tab" action does not work #269

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
8000
bpauli opened this issue Jul 27, 2021 · 0 comments · Fixed by #270
Closed

[ExperienceFragment] "Edit in New Tab" action does not work #269

bpauli opened this issue Jul 27, 2021 · 0 comments · Fixed by #270
Assignees
Labels
bug Something isn't working

Comments

@bpauli
Copy link
Contributor
bpauli commented Jul 27, 2021

Steps to reproduce :

  1. Open the "About Us" page in Edit mode content/wknd/language-masters/en/about-us.html
  2. Try to open one of the Experience Fragments in edit mode from the Component edit bar option "Edit in New Tab"

Expected Behavior: The edit button should open the experience fragment in the experience fragment editor.

Experienced Behavior: It displays the error "The experience fragment doesn't have an associated variation"

Background: This issue was fixed in Core Component 2.8.0 adobe/aem-core-wcm-components#815 But as the proxy component of the experience fragment comes with an outdated editConfig node the fix doesn't apply.

Solution: As the editConfig is now inherited from the parent component there is now need to specify the editConfig in the proxy component anymore.

bpauli added a commit that referenced this issue Jul 27, 2021
@davidjgonzalez davidjgonzalez added the bug Something isn't working label Aug 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0