Ticket #2184 (closed enhancement: fixed)

Opened 9 years ago

Last modified 9 years ago

Make a unicode upgrade cpsjob

Reported by: gracinet Owned by: madarche
Priority: P1 Milestone: CPS 3.5.2
Component: CPS (global) Version: TRUNK
Severity: major Keywords: unicode upgrade


Having upgrade steps is nice, but not enough:

  • the whole upgrade process
  • the upgrade can be long, people will need to invoke it from server console, behind any corporate proxy
  • some treatment can be factorized among steps (crawling the folder hierarchy, see #2183)

Unicode upgrade steps will be kept, though, so that people can relaunch one independently from the big thing.

In my mind, the upgrade process needs not to be so polished for 3.5.1, but that'd be welcomed, of course

Change History

comment:1 Changed 9 years ago by gracinet

  • Status changed from new to closed
  • Resolution set to fixed

Done (CPSDefault/jobs/upgradeunicode.py) new steps will obviously have to be registered.

comment:2 Changed 9 years ago by madarche

I'm not sure if it's the right place to put it but here it is: the document history of each document should also be migrated to Unicode. As it is now, the rendering of the history has broken characters if there was some accented characters in the history. But there are no UnicodeDecodeError? or similar things that could break a page rendering.

comment:3 Changed 9 years ago by gracinet

I think it's #2179.

Note: See TracTickets for help on using tickets.