You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jmalatia CKEditor 4 Vue integration won't load CKEDITOR namespace if you do it yourself. That means that you could still use CDN script externally to have access to the CKEDITOR object, so you can add an external plugin before the editor instance will be initialized. Please, take a look at https://codepen.io/jacekbogdanski/pen/vYGjLxe where I'm using standard editor preset without editorplaceholder plugin, but I can still load it using CKEDITOR.plugins.addExternal.
However, I think it's a good idea to introduce some method which would allow us to access CKEDITOR namespace before initializing editors for use cases like the above. I will create a separate ticket for that (#61).
@jacekbogdanski We are using this in a vue SPA with single file components and ckeditor.component so the codepen will not work for us. But the new ticket #61 you opened is exactly what we need. Thanks.
There is no way we can see to configure the path for a local custom plugin when using ckeditor from cdn.
Without vue, the normal process would be:
Then in config.js:
Seems like ckeditor4-vue needs something like a
pluginAddExternal
prop added to the component and then invoked in it's code before it calls replace?The text was updated successfully, but these errors were encountered: