#ckeditor4 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ckeditor4, aggregated by home.social.
-
Researching and testing moving @gamingonlinux.com from #CKEditor4 to #CKEditor5 and omg so complicated, everything is different. Having to totally rewrite the few custom bits we have, going to take a while <_<
-
Researching and testing moving @gamingonlinux.com from #CKEditor4 to #CKEditor5 and omg so complicated, everything is different. Having to totally rewrite the few custom bits we have, going to take a while <_<
-
Researching and testing moving @gamingonlinux.com from #CKEditor4 to #CKEditor5 and omg so complicated, everything is different. Having to totally rewrite the few custom bits we have, going to take a while <_<
-
Please vote for this #CKEditor5 feature: https://github.com/ckeditor/ckeditor5/issues/14206
As for upgrading #TYPO3 instances to #v12, this is really necessary to keep the previous behaviour of #CKEditor4 that only one #style can be assigned to an element instead of multiple. #CKEditor -
@danielsiepmann I have discussed this several times with my colleagues and everyone agrees that plugin development for #CKEditor5 is hell.
I don't know why #TYPO3 decided to keep using #CkEditor5, because I don't see any benefit. It seems very over-engineered (it has it's own debug console!) and all plugins from #CkEditor4 have to be completely rebuilt as there is no upgrade path. So it wouldn't matter if #TYPO3 had switched to another #RTE.
-
Please vote for this #CKEditor5 feature: https://github.com/ckeditor/ckeditor5/issues/14206
As for upgrading #TYPO3 instances to #v12, this is really necessary to keep the previous behaviour of #CKEditor4 that only one #style can be assigned to an element instead of multiple. #CKEditor -
Please vote for this #CKEditor5 feature: https://github.com/ckeditor/ckeditor5/issues/14206
As for upgrading #TYPO3 instances to #v12, this is really necessary to keep the previous behaviour of #CKEditor4 that only one #style can be assigned to an element instead of multiple. #CKEditor -
Please vote for this #CKEditor5 feature: https://github.com/ckeditor/ckeditor5/issues/14206
As for upgrading #TYPO3 instances to #v12, this is really necessary to keep the previous behaviour of #CKEditor4 that only one #style can be assigned to an element instead of multiple. #CKEditor -
Please vote for this #CKEditor5 feature: https://github.com/ckeditor/ckeditor5/issues/14206
As for upgrading #TYPO3 instances to #v12, this is really necessary to keep the previous behaviour of #CKEditor4 that only one #style can be assigned to an element instead of multiple. #CKEditor -
@danielsiepmann I have discussed this several times with my colleagues and everyone agrees that plugin development for #CKEditor5 is hell.
I don't know why #TYPO3 decided to keep using #CkEditor5, because I don't see any benefit. It seems very over-engineered (it has it's own debug console!) and all plugins from #CkEditor4 have to be completely rebuilt as there is no upgrade path. So it wouldn't matter if #TYPO3 had switched to another #RTE.
-
@danielsiepmann I have discussed this several times with my colleagues and everyone agrees that plugin development for #CKEditor5 is hell.
I don't know why #TYPO3 decided to keep using #CkEditor5, because I don't see any benefit. It seems very over-engineered (it has its own debug console!) and all plugins from #CkEditor4 have to be completely rebuilt as there is no upgrade path. So it wouldn't matter if #TYPO3 had switched to another #RTE.
-
@danielsiepmann I have discussed this several times with my colleagues and everyone agrees that plugin development for #CKEditor5 is hell.
I don't know why #TYPO3 decided to keep using #CkEditor5, because I don't see any benefit. It seems very over-engineered (it has it's own debug console!) and all plugins from #CkEditor4 have to be completely rebuilt as there is no upgrade path. So it wouldn't matter if #TYPO3 had switched to another #RTE.
-
@danielsiepmann I have discussed this several times with my colleagues and everyone agrees that plugin development for #CKEditor5 is hell.
I don't know why #TYPO3 decided to keep using #CkEditor5, because I don't see any benefit. It seems very over-engineered (it has it's own debug console!) and all plugins from #CkEditor4 have to be completely rebuilt as there is no upgrade path. So it wouldn't matter if #TYPO3 had switched to another #RTE.