Migration from fck schema_version 6202 [#940376]

The install (migration) script of ckeditor accepts only a fckeditor schema version 6201. The current schema is 6202. I gues this schema version also works for a migration?

Comment	File	Size	Author
#4	940376-4_ckeditor_migrate_schema_6202.patch	419 bytes	rjacobs
#4

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

scott_earnest CreditAttribution: scott_earnest commented 28 October 2010 at 19:13

It worked for me, mostly. I needed to add 6202 as an accepted value in the switch. Sorry I don't have patch writing power.

Index: ckeditor.install
===================================================================
@@ 58,3
  switch ($f_sv) {
    case 6201:
+    case 6202:
      db_query("INSERT INTO {ckeditor_role}(name, rid) SELECT name, rid FROM {fckeditor_role}");

It did not reassign the permissions, like "access fckeditor, administer fckeditor". Looks like there may not be an equivalent for "allow fckeditor file uploads".

Comment #2

rjacobs CreditAttribution: rjacobs commented 28 October 2010 at 20:48

Tracking.

Is it safe to run the same code for either schema? Sounds like it may be. As far as I can see from the documentation, direct permissions are not copied from fckeditor... and it looks like the code supports this impression (though it does seem to copy the settings that state which role can use which profile).

Comment #3

rjacobs CreditAttribution: rjacobs commented 19 November 2010 at 06:05

I migrated from fckeditor to ckeditor on a couple of sites recently. I had good success using the small edit noted in #1. So long as you manually set the new ckeditor permissions, all my global and profile settings copied over fine. Saved me a lot of time.

Went fckeditor 6.x-2.1 -> ckeditor 6.x-1.2