Closed (won't fix)
Project:
CKEditor 4 - WYSIWYG HTML editor
Version:
7.x-1.12
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Nov 2011 at 20:43 UTC
Updated:
11 Mar 2013 at 23:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
jherencia commentedAs said in the other issue:
It seems that ckeditor_profile_load, which is executed in update_7003, expects that ckeditor_input_format has been created previously, but somehow it has not.
Comment #2
astutonetOk.
I think some instruction is missing after line 485 of file ckeditor.install.
I have noticed this problem with other modules as well.
As in other modules, a patch may be able to fix the problem.
Can you help me?
Comment #3
jherencia commentedWell, in this commit the table ckeditor_input_format was introduced in hook_schema, but no hook_update was introduced. In every D6 migration ckeditor_input_format will not exist once reached #7003.
http://drupalcode.org/project/ckeditor.git/commitdiff/067a502f949e3baec0...
It looks like currently there is no upgrade path, it is needed:
Comment #4
mkesicki commentedWe will check this and try to fix it. Any help is nice welcome ;)
Comment #5
jherencia commentedHere is the patch, it important to know that #1329980: [D7] Problem with CKEditor module update needs to be applied too to solve all the issues related to #7003.
Comment #6
jherencia commentedComment #7
jherencia commentedI've added some comments.
Comment #8
astutonetThe patch works fine.
Tks.
Comment #9
dczepierga commented@jherencia, really thx for patch and good work. I commit your patch to GIT.
Pls update to last DEV version.
Greetings
Comment #10
dczepierga commentedComment #12
bok11 commentedI confirm - this patch is working.
Thank you :)
Comment #13
spidersilk commentedI'm still having this problem, with version 7.x-1.12 (while upgrading from D6). If the patch was committed in November 2011, and 7.x-1.12 was released in December 2012, wouldn't the change have been included in the official release by then? Or do people still need to use the dev version rather than the stable version?
Comment #14
spidersilk commentedSorry, never mind, just saw the upgrade.txt file and discovered that you can't upgrade the module at all, just uninstall and reinstall it, and reapply all your settings from scratch.
Closing the issue again, though I don't think "closed (fixed)" really applies under the circumstances...