Bug #239
closed
Class import doesn't prune erased classes
Added by SyRenity Now over 14 years ago.
Updated over 14 years ago.
Description
I imported some classes, which I later erased from disk.
Repeating import doesn't prune these classes.
- Target version set to 0.1-6
- Status changed from New to Ready For Testing
- Assignee changed from Ohad Levy to Paul Kelly
- Branch set to bug/239-prune-erased-classes
The fix also includes a page in which the user selects the additions and removals which they would wish to apply to their database.
Errors are reported and an opportunity is given to reapply the changes.
Paul Kelly wrote:
The fix also includes a page in which the user selects the additions and removals which they would wish to apply to their database.
Errors are reported and an opportunity is given to reapply the changes.
Would you mind adding tests?
A few minor fixes
Tests added
NOTE that this branch consists of two commits, #239 and then #377, as the assert_select tests do not work without XHTML compliance
I would guess that git will find that the patch has already been applied if you were to apply this branch to develop after the separate #377 branch had been applied.
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF
Updated by 
Updated by