Closed (fixed)
Project:
CKEditor 4 - WYSIWYG HTML editor
Version:
7.x-1.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Jul 2011 at 16:52 UTC
Updated:
30 Dec 2011 at 16:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
chriz001 commentedsubscribe
Comment #2
mkesicki commentedComment #3
wiifmSubscribe. Really keen to see this in for the 7.x version as well, it worked so well for the 6.x version
Comment #4
dczepierga commentedI add this feature in last DEV version, pls check this and write if u found any bugs or not, because i don't have enough time to test it...
Greetings
Comment #5
wiifmHi @dczepierga,
I have downloaded the latest 7.x-1.x-dev package (August 3rd), and there is no mention of features support in the code, so I went to the repo and I have seen your commit - http://drupalcode.org/project/ckeditor.git/commitdiff/074347d2820bb56be6...
I will wait for the dev package to be updated ;)
Thanks
Comment #6
dczepierga commentedDev package it's updated, so u could try to test it :)
Greetings
Comment #7
mkesicki commentedComment #8
mkesicki commentedComment #9
ultimateboy commentedThis isn't working as I'd hope.
I've created several new text formats and applied ckeditor profiles to those, upon creating a feature, the .features.ckeditor_profile.inc is created and all looks good. However, when I go to install the feature on a fresh site, the text formats are created as anticipated, but the feature is marked as overridden and the profiles are not created.
If I revert the feature, everything works as hoped, but that's definitely not ideal.
Comment #10
ultimateboy commentedI've attached a really simple feature with a custom text format and the ckeditor profile to show the issue.
Comment #11
mkesicki commented@ultimateboy for future, please don't open closed tickets. If there is new problem with some closed ticket just please create new one.
Please open new ticket (with correct version) of CKEditor module and link it here.
Comment #12
guillaumev commentedI noticed the same bug as well, and created a new issue here: http://drupal.org/node/1373138
I'm marking this issue as fixed...