We have moved to GitHub Issues
Created by Jeremy Pyne 14 Jun 2016, 17:59:48 Updated by Sebastiaan Janssen 11 Aug 2016, 08:29:31
The markdown.editor.js plugin that attaches ui elements for markdown editors locates and attaches controls by ID. It searches the global document for a matching ID not the scope of the Umbraco.PropertyEditors.MarkdownEditorController view as it should. This means that developers trying to use this property in any sort of repeating fashion will not get valid Markdown editors and multiple menu mars will be attached to the first one.
This does not affect normal documents with Markdown Editors as they would all have unique Alias's and thus the Id's would conflict.
This change simply passes the $element scope to the markdown.editor.js and changed the getEmementById to use a scoped jQuery find instead.
@madsrasmussen and I have been through your PR and unfortunately modifying anything in the
lib folder is not an option as it is external libraries. It should however be possible to achieve a similar solution by using the postfix option already built into the markdown plugin.
When we tried to replicate the issue it however seems like the current version of the Nested Content plugin does not have this problem due to using
ng-if to only show one active item at a time. I'm closing the PR for now and encourage you to upgrade to the latest version of Nested Content to avoid the issue.
If you encounter any further issues with this that can't be fixed by using latest versions, could you please submit a new issue with updated instructions on how to replicate exactly that scenario. Then we will look into getting the editors scoped using the postfix option instead.
Best, Claus / Mads
Difficulty: Very Easy
Backwards Compatible: True
Fix Submitted: Pull request
Affected versions: 7.4.3
Due in version: