Ticket #2309 (closed defect: fixed)

Opened 9 years ago

Last modified 9 years ago

Adherence to profiles of unicode upgrade steps

Reported by: gracinet Owned by: gracinet
Priority: P2 Milestone: CPS 3.5.2
Component: CPS (global) Version: 3.5.1
Severity: critical Keywords: profiles ascii upgrade step


Some upgrade steps require some technical string fields to be CPS Ascii String Field (typically those used to store relative paths in portlets).

For now, this is obtained by replaying the profiles, which is barely acceptable for portals using the meta_profiles system and a big problem for others.

We need to correct these fields before hand in the upgrade steps. There's an implicit contract on upgrade steps anyway, that they should work independently of (user-triggered) profiles loading.

Of course we can't update people's profiles for them. All we can do is issue warnings.

Change History

comment:1 Changed 9 years ago by gracinet

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

Just introduced two new upgrade steps in CPSDefault (for Ascii String Fields and also for the validate_none of #2180).

This should fix the issue. Note that products depending on CPSDefault are welcome to register in __init their fields to be upgraded in the two corresponding dicts defined in Products.CPSDefault.upgrade.

Note: See TracTickets for help on using tickets.