Ideally, when you run the included migration, it should put all pages in a default order based on the title. Unfortunately, there are serious weaknesses to acts_as_list that cause it to break when any records get inserted inconsistently. I'd appreciate any tests/patches that could identify and resolve this issue.
Sean Naohiro Yoshida wrote: > Mario T. Lanza wrote: > >> When I try to move a page, it has unpredictable results. They don't >> seem to properly relocate. >> > > I encountered the same phenomenon before, having data incorrect. > "position" has to be unique in a certain "parent_id". > If you get no empty result executing following SQL(when you use MySQL), > you should modify "position" data first. > > select * from `pages` group by parent_id,position having count(*) > 1; > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
