[Radiant] db:migrate brought upon reordering nightmare -- <r:children:each by="date'> exist?

[Oliver Baltzer]

Andrew Klein wrote:
> I've just finished porting my website to 0.6.0rc2 after running with 
> 0.5.2 live and 0.6.0 on a test-and-build server. However, after got it 
> ported and did the db:migrate, I fell into an evil issue: For some 
> bizarre reason, db:migrate this time somehow decided it wanted to 
> re-sort all of the news articles I already had in place. Now, my article 
> order is totally random (About 90 of them) and I can't figure out why on 
> Earth it did it this time, when I didn't have this issue the last two 
> times I migrated the database to 0.6.0rc2 to make sure my migration went 
> smoothly. Anyone have any ideas?

I suspect something went wrong in migration
010_merge_behaviors_and_pages.rb where a method in the Page model is
called to update the published_at field during #save, though it
shouldn't have changed anything. If you have access to the database
via a command line interface you can try to execute the following
update (make a backup first):

UPDATE pages SET published_at = created_at WHERE published_at IS NOT NULL;

Maybe that helps.

Cheers,
Oliver

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 191 bytes
Desc: OpenPGP digital signature
Url : http://lists.radiantcms.org/pipermail/radiant/attachments/20070417/a23d480e/signature.bin