Conversion utility should be in database project
Activity
Show:
Megan May February 6, 2008 at 11:59 AM
Tasks for 2.5.0 have been completed. We're nearing the end of the QA cycle and A lot of general regression testing has been going on for the past few months - the changes have likely been reviewed via this method of testing
David Haines November 14, 2007 at 10:13 AM
Is this just the cleanup of a duplication or is it causing errors?
David Haines November 14, 2007 at 9:26 AM
Would this require changes to other projects?
Jim Eng November 14, 2007 at 9:15 AM
Once we merge the conversion for trunk to post-2.4, this issue will also affect post-2.4. The question is whether this change should also be applied to post-2.4? Should we add the conversion utility to content in post-2.4 and then move it to db?
Megan May October 31, 2007 at 5:32 AM
Fixes included in 2.5.0.011 tag
Fixed
Details
Details
Assignee
Jim EngReporter
Jim EngFix versions
Affects versions
Priority
CriticalCreated October 23, 2007 at 3:11 PM
Updated October 23, 2008 at 6:30 AM
Resolved October 23, 2007 at 4:55 PM
The conversion utility classes are duplicated in assignments and content. They should be in database, with the config files and handlers in the project whose tables are being converted.