pourquoi / ckeditor5-simple-upload

33 stars 22 forks source link

plugincollection-plugin-name-conflict: Two plugins with the same #17

Open keatwei opened 5 years ago

keatwei commented 5 years ago

Having this warning on ckeditor5-build-classic v12.3.1

plugincollection-plugin-name-conflict: Two plugins with the same name were loaded. Read more: https://ckeditor.com/docs/ckeditor5/latest/framework/guides/support/error-codes.html#error-plugincollection-plugin-name-conflict {pluginName: "PendingActions", plugin1: ƒ, plugin2: ƒ}

plugincollection-plugin-name-conflict: Two plugins with the same name were loaded. Read more: https://ckeditor.com/docs/ckeditor5/latest/framework/guides/support/error-codes.html#error-plugincollection-plugin-name-conflict {pluginName: "FileRepository", plugin1: ƒ, plugin2: ƒ}

0xecute commented 5 years ago

Same error for me.

ratribiana commented 5 years ago

Same for me. I use it in Vue Js PLUS toolbarview-item-unavailable: The requested toolbar item is unavailable. Read more: https://ckeditor.com/docs/ckeditor5/latest/framework/guides/support/error-codes.html#error-toolbarview-item-unavailable {name: "imageUpload"}

pourquoi commented 5 years ago

I've updated the dependencies, it should fix most of the errors. (remove your ckeditor classic node_modules folder and reinstall)

minasm commented 5 years ago

@keatwei did you manage to sort this? I updated and still get the same error. Still getting Uncaught (in promise) CKEditorError: plugincollection-plugin-name-conflict: Two plugins with the same name were loaded. error

ratribiana commented 5 years ago

These are what I did. I updated all the packages related to ckeditor5 and added @ckeditor/ckeditor5-ui@latest

When I updated all the packages related to ck5editor I encounred this new multiple errors plugincollection-plugin-name-conflict through duplicate.....

https://github.com/ckeditor/ckeditor5/issues/1505

so I deleted the node_modules and package.lock and npm install again. I delete the cache of node_modules as well before hitting the npm install again

Most probably, the cause of the errors is if you have newer version of some plugins and also have older version, it will return an error since it seems you are using both the new and old version or you can't use newer version of plugins with older version of core plugins