Closed (fixed)
Project:
CKEditor Link
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
11 Jul 2011 at 14:18 UTC
Updated:
2 Jan 2012 at 10:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
anrikun commentedYep, but what happens if user disables Clean URLs afterwards?
Does it work too?
Edit:
After looking at your patch, it seems that you didn't move but added things, right?
Comment #2
nico heulsen commentedGood point, didn't keep that in mind. But I really think we should avoid the hook_init as much as possible, so I created a new patch (in this I removed the hook_init), and added an extra submit-handler (on the Clean URLs settings form) to disable the CKEditor link module when disabling the "Clean URLs". I also added a notice within the description to inform the user.
Comment #3
anrikun commentedThanks! Several problems though:
- Your patch does not apply to the last dev. I can see this because of a missing
menu_rebuild();-
' <em>(' . t('Notice : When disabling the "Clean URLs", CKeditor Link module will also be disabled.') . ')</em>'needs a better message, and no ems!-
drupal_set_message(t('Disabled CKEditor module, since it requires "Clean url" to be active.'), 'notice');: message is wrong and this should be a warning IMHO.Comment #4
devin carlson commentedThis is still an issue.
Besides the performance impact, using hook_init makes it very difficult to automatically configure CKEditor Link using an installation profile because the module automatically disables itself whenever it detects that Clean URLs aren't available (and Clean URLs aren't available during installation).
I've provided an updated patch against 7.x-2.x-dev.
Comment #5
anrikun commentedThanks to both of you!
This is now committed to 6.x-2.x-dev and 7.x-2.x-dev with some minor changes/fixes.