This has got my fervent vote. I'll try and not go on and on... but...
For every of the 5 or 6 sites I've now put up in Radiant sorting was a requirement that I have had to work around not having. It seems like it'd be a very natural addition to what Radiant is. Mostly the workarounds have entailed manually maintain navigation schemes where I otherwise would have just done a <r:childeren:each ... or written a tag to automate them. On the most complex site we have up, www.diopa.org, all of the 2nd and 3rd level navigation items of which there are a fair amount, get created through an annoying set of snippets and <r:if ... <r:unless ... switches to bring in the right snippet of completely manually maintained navigation. The worst part of this is that every time my client or designer wants content added in these sections (most of the site) I have to add it to the nav for them. Also, one of Radiant's more significant talents derived from it's simplicity is that it's a great tool for figuring-out the initial structure and content of a site. However, the pretty hierarchical page tree so central to Radiant admin is much diminished in this role without the ability to freely move pages around as you work away. So re-parenting is equally important to me in at least this respect. I tried the patch long ago and found it to be cumbersome and slow and I really don't want to worry about maintaining a patched environment. I don't currently feel qualified to work-up a new patch nor improve the existing one, but I've got $$$ (seriously) for the first one to do it well enough to get it included in a core release. So much for not going on and on... Loren www.fn-group.com _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
