Feature #132
Container ordering
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Core
Target version:
-
Start date:
05/09/2011
Due date:
% Done:
0%
Estimated time:
Description
Although containers are always displayed in the same order, the order in which they are displayed is undefined - i.e. putting one container before another in a template doesn't seem to guarantee that the same order will be used in the admin interface. It would be useful to be able to be explicit about this.
Associated revisions
Merge branch 'master' of git://github.com/melinath/philo
- 'master' of git://github.com/melinath/philo:
Implemented the solution proposed to #130 - removed TreeModel and made a SlugTreeEntity subclass of TreeEntity to handle Node and Template. Correctly subclassed SlugTreeEntity.Meta so that Node and Template actually have the unique constraints they are meant to. Minor correction to TreeEntity.get_path.
Minor corrections to TagCreation.js. Resolves issue #125.
Switched contentlets to use lists rather than sets to preserve ordering. Resolves issue #132. Added some basic tests for containers. Moved build_extension_tree out of Template.containers.
Minor correction to FeedView docstrings. Resolves issue #139.
Refactored RequestNodeMiddleware to use SimpleLazyObject - comparable to django r16297/r16305. Resolves issue #144.
Corrected philo tests and removed all use of penfield models in those tests - resolves issue #80. Minor correction to TreeModel.get_path to save a query.
Added a 'getting started' tutorial and a short intro to philo page to the docs. Improved Attribute docstring.
History
Updated by Stephen Burrows almost 13 years ago
Updated by - Status changed from New to Resolved
Resolved with commit d8d6976f3a0646a05e052d33294e3c8c44c5eed3.
Switched contentlets to use lists rather than sets to preserve ordering. Resolves issue #132. Added some basic tests for containers. Moved build_extension_tree out of Template.containers.