Closed (fixed)
Project:
CKEditor 4 - WYSIWYG HTML editor
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
29 Nov 2011 at 17:03 UTC
Updated:
27 Jun 2013 at 07:21 UTC
Jump to comment: Most recent file
Comments
Comment #1
hctomAny news on this? Or can anyone confirm this problem?
Cheers
hctom
Comment #2
mkesicki commentedWe will check this ASAP. Please be patient. Maybe some else can confirm this issue. Thank you for report this.
Please try latest DEV version and check if the problem exists there
Comment #3
Coop920 commentedHow are you able to export the wysiwyg profiles? I'm trying to find the component to be added to a feature and can't seem to locate anything. Can you advise? Thanks.
Comment #4
hctomHi Coop920,
I configured my global CKEditor profile to have the right paths. And after that all profiles (including the ones that get installed by default) were exportable with the ckeditor_profile component.
Here are the steps I performed to create the feature:
drush fu feature_nameHope this helps?!
Comment #5
dxvargas commentedI also have this problem with latest versions:
Drupal 7.14
CKEditor 7.x-1.9
Features 7.x-1.0-rc2
After
drush fu feature_name, input_formats array is now empty and feature says it is overriden.Moreover, if I now do
drush fr feature_name, I get a "Current state already matches defaults, aborting." but feature still says it is overriden.Comment #6
schultetwin commentedStill an issue for me as well.
Comment #7
_tychris commentedI think to resolve your problem via drush you can add argument "--user" :
drush fu feature_name --user=1Comment #8
mbruneel commentedI confirm the issue (with 1.9 and -dev).
Adding
--user=1works. IMHO, that should be documented.Thank you _tychris!
Comment #9
Volx commentedI am having the same issue, --user=1 helps, but it doesn't really solve the problem. This should not be documented but instead be fixed. I never needed this flag for any features export and I don't see any reason why it should be necessary here.
Comment #10
Volx commentedAnd here is the fix :)
The problem is that ckeditor_profile_load checks the user's access to the filter formats. I added a parameter $check_access and set that to FALSE on features export. Default is TRUE so it should be fine security wise whenever the function is called somewhere else. I have never seen access checks on other features exports.
Comment #11
lundj commented#10 works pretty well for me!
A very important patch in my opinion.
Could this be included in the next release?
Comment #12
SebCorbin commentedWorks nicely here
Comment #13
yched commentedAgreed on the issue and on the fix :-)
Comment #14
yched commentedSeems pretty important too...
Comment #15
jcisio commentedThanks. Committed patch #10.
Comment #17
Kristina Katalinic commentedthis is still not resolved. Regardless of whether the feature was created using features UI or drush exported feature will show as "overridden" on the new site created using custom installation profile
here is the diff