What steps will reproduce the problem?
1. Run a migration
2. View the gallery page post-migration
What is the expected output? What do you see instead?
The order of explorations on the gallery should not change during a migration.
Since a migration involves resaving all explorations in an arbitrary order, it
breaks the previous ordering of the explorations.
This can be fixed in one of two ways:
1. Introduce a new field to the exploration model indicating the last time it
was updated per updates that should resort the exploration.
2. Update the gallery exploration sorting to step back in exploration versions
until it encounters one which is not a migration, then use the created date of
that version as the last updated time of the exploration.
Original issue reported on code.google.com by bhenn...@google.com on 29 Jun 2015 at 9:05
Original issue reported on code.google.com by
bhenn...@google.comon 29 Jun 2015 at 9:05