Ticket #1533 (new defect)

Opened 14 years ago

Last modified 13 years ago

Extension profile should be able to transtype vocabularies

Reported by: div Owned by: fguillaume
Priority: P1 Milestone: CPS 3.5.7
Component: CPS (global) Version: 3.4.0
Severity: normal Keywords:


An extension profile should be able to transtype an existing vocabulary, by omiting it's meta-type for instance

Change History

comment:1 Changed 14 years ago by gracinet

In the meanwhile, you can use the remove="True" attribute if it doesn't hurt. What do you mean with "omitting" ?

comment:2 Changed 14 years ago by div

I mean if you do not specify a meta-type, then it could be considered a transtyping. But even better would be to compare the meta-type in the extension profile with the meta-type of the existing vocabulary, and if they are different, a transtyping should be made. P.S. Yep, that's the workaround I've used, but of course that any import of the base profile will fail.

comment:3 Changed 14 years ago by gracinet

The second one is consistent with what's been implemented for widgets and fields. The main problem I see here is that this would have to be handled by the _initObjects method (that comes from ObjectManagerHelpers?). We have to duplicate it entirely if we want to change anything. That's what has been done in CPSDocument.exportimport.CPSObjectManagerHelpers.

[34654] makes the use of remove=True more comfortable by inheriting from the latter, at least for people that switch all the time between two extension profiles.

comment:4 Changed 13 years ago by sfermigier

  • Milestone changed from CPS 3.4.1 to CPS 3.4.2
Note: See TracTickets for help on using tickets.