Hi @prudloff
We're currently investigating possible options to address this issue - we'll share an update once we know more.
Hi @mcortesd19
Thank you for reporting the issue - we're looking into it.
Thanks for reporting the issue - we'll look into it in upcoming iteration.
Closing this issue for the time being as we were not able to reproduce it.
The solution suggested by @salmonek should resolve the issue. We don't plan to cover this edge case in the module itself for the time being, unless there will be more requests from the community.
Patch from this issue has been already merged into the codebase, we've missed this one :)
An official fullscreen plugin for CKEditor 5 is about to be released, so we're starting to work on the migration.
Thanks for reporting the issue @bronismateusz - we're looking into it.
Closing for now as we were unable to reproduce the issue. @phjou we'll be happy to take another look at this after you provide the information requested by @salmonek.
Closing for the time being as we are unable to resolve the issue until it's addressed in CKEditor core.
Hi weseze!
Official CKE5 full screen plugin is planned for Q1, so should be out soon. Once it's available, we'll include it in this module.
This will be resolved by the solution for this ticket 🐛 To-do document list not working Active
Hi mkalkbrenner,
Including the Premium Features module as a dependency is a design decision we've made because we want to be able to enable some of the premium functionalities for free in Plugin Pack exclusively for Drupal users. Currently, removing Premium Features from dependencies would break features like WProofreader or Fullscreen mode.
As a workaround, you might choose to clone the module's repository using Git instead of installing it with Composer if you really want to avoid certain dependencies. This will likely break some functionalities of the module, although that might not be a problem if you just want to use fonts, as you mentioned in your example.
Unfortunately, we don't know about any contrib module that implements this functionality.
Closing as we couldn't reproduce the issue
Keeping postponed as we're not able to resolve it as long as we support Drupal 10.2
Closing as we could not reproduce the issue.
Closing as the patch was designed for very specific use case and we do not plan to add such functionality to the module officially at the moment.
Hi francismak
Thank you for reporting the issue - we'll try to address it in one of upcoming releases.
Hi anybody
Thank you for reaching out and sharing your suggestion - we are glad to hear that you enjoy Plugin Pack.
The goal of this module is to provide access to official plugins provided by CKEditor 5 and we do not plan to develop any custom functionalities in Plugin Pack directly. Because of that, unfortunately we won't be able to work on this functionality.
Closing as we were not able to reproduce the issue and got no required information about it.
Hi Andreas, the fix for this issue is likely to be included in the next release.
Hi nilesh.nitsan
Thanks for letting us know about the issue - we're looking into it.
Thanks for reaching out. This indeed might be a limitation of the plugin, but it seems the code that you wanted to include in the issue got removed. Please let us know what do you want to achieve and we'll look into it and try to see if we can help :)
Hi kopeboy!
Thanks for reaching out.
We consider current behaviour the expected one and we haven't had plans to change it so far, as giving flexibility to our users was our main motivator here. We appreciate the fact that adding custom CSS might be non-trivial for some users, but at the same time it's not something too complex for most Drupal admins in our opinion.
However, we are open to feedback and we'll keep the issue active for some time to see if there will be more demand for such change and we'll consider it based on that.
I've changed category to "Feature request" as it's functionality that we don't have implemented at the moment.
Just to summarise your request and make sure we are on the same page, it is about:
- adding possibility to configure number of columns on the color grid as mentioned in CKEditor 5 documentation
- adding a configuration option that would allow to hide/display "Document colors" section
If that's correct, we'll add it to our backlog and we'll try to include it in one of the future releases.
Closing as this issue was not related to the module itself.
We've decided not to include this change in the module as it seems to be quite use-case specific.
We'll be happy to reconsider in the future in case there would be more people requesting this feature.
At this time, we do not have plans to release an official CKBox integration for Drupal. However, if you are a customer and would like to explore integrating CKBox with Drupal, please contact us directly. We’d be happy to discuss your needs and see how we can assist you.
The main reason is convenience and saving time to be honest as vokiel is currently not involved in Drupal-related projects within the organization.
However, I was unaware that it's possible only for a single person to be able to edit the org node.
I don't necessarily want his access to be revoked, so please ignore the request if there is no other option.
Thanks
mdusza → created an issue.