Re: [Radiant] Page Reordering
hi Bob, I recently re-packaged the old reorder extension; the one where you have a reorder button for every page with children; https://github.com/jomz/radiant-reorder_children-extension This works well with edge, and is also available as a gem. About automatic menu generation; I dò agree with you. Anton has a point about not letting your main navigation grow too big, but on deeper navigations (for example on /about; /about/history,/about/team, ...) I also find it convenient to have new pages under about/ come up in there automatically by default. I use r:nav for this; https://github.com/jomz/navigation_tags Works well with Edge, and is available as a gem (radiant-navigation_tags-extension). Be sure to check https://github.com/jomz/navigation_tags/blob/master/lib/navigation_tags.rbas the README is slightly outdated (append_- and prepend_urls) 2011/6/21 Anton J Aylward radi...@antonaylward.com Bob Sleys said the following on 06/20/2011 09:59 PM: Thanks for the reply but I do find a couple of points interesting. First you rail against using the tree structure of the pages to generate menus and then point out that copy/reording is needed. Please re-read: that's not what I said. To the first point the entire tree structure doesn't feed into the menu. Which is what I *DID* say. It's easy to check for a page part and exclude that page and all it's children from the menu. Or reverse that and only include pages that have the page part. IE a filter in generating the menu. True, but the more processing you do the complicated things become and the more code the more room for mistakes and the more you deal with special cases and exceptions ... Yes, ANYTHING is possible if you're willing to put enough effort into coding it. No, I'd rather KISS and rely on good structure and design. I don't control all the content on the sites I put up. I have a quite a number of client sites like that. However I do have control over things like layouts, what extensions are loaded and the STRUCTURE. Users can add content: new articles, comments, but the content fits in with the STRUCTURE. They can't run it topsy-turvy or restructure it. What's so great about radiant is I can do the backup stuff get it all running, setup the basic site design etc. and then turn it over to the customer to add content. Yes. That's what I'm saying. I need to make it as easy as possible for the customer to add/more/change pages. But not restructure it. ... Back to the original pont of the post. I'm asking if anyone knows of a reorder extension that works with 1.0 of Radiant. All the ones I looked at including those posts here so far are quite old so AFAIK have a good chance of not working with 1.0. I'm also sugesting that it would be a good addition to core of radiant. Is there a particular reason you need to be at the bleeding edge? Are there more features there that are of greater importance than a working copy/move, because at 0.8.1 and 0.9.x I *KNOW FOR SURE* they work. And looking at them, I don't think its a big issue upgrading them. Its not as if you're adding some radically new functionality. I'm not sure I agree about adding to the core. Some of the sites I've developed while not actually static in content have no need for reordering once they are set up. Some of the blogs and BBoards are like that. Always new content, but it is added - the basic structure, layout, facilities etc, doesn't need to change. -- Met vriendelijke groeten, Benny Degezelle Gorilla webdesign www.gorilla-webdesign.be
Re: [Radiant] Page Reordering
in fact, you can add a 'no-map' part to a page to exclude it. When I find the time, I'll also make it look for a no-map page-field, that'd be cleaner.. 2011/6/21 Bob Sleys bsl...@gmail.com Thanks, I'll give those a try. The navagation_tags looks very nice, though I think I'll have to tweak it to add an option to ignore certain pages. Say if the page has a page part of no-nav ignore it and it's children. But otherwise it looks to be exactly what I end up building via 2 snippets. This would be much neater and less prone to the end user monkeying with it and messing it up. Bob -- Met vriendelijke groeten, Benny Degezelle Gorilla webdesign www.gorilla-webdesign.be
Re: [Radiant] Page Reordering
Very nice. I took a quick look through the code and missed that. Thanks Bob
Re: [Radiant] Page Reordering
getting an error running the migration for the reorder_children extension. rake radiant:extensions:reorder_children:migrate --trace (in /home/bsleys/projects/ooo-web) ** Invoke radiant:extensions:reorder_children:migrate (first_time) ** Invoke environment (first_time) ** Execute environment Could not load extension from file: reorder_children_extension. #NoMethodError: undefined method `migrate_from' for ReorderChildrenExtension:Class ** Execute radiant:extensions:reorder_children:migrate rake aborted! undefined method `migrate_from' for ReorderChildrenExtension:Class /home/bsleys/.rvm/gems/ruby-1.8.7-p334@ooo-web/gems/radiant-1.0.0.rc2/lib/simpleton.rb:16:in `method_missing' /home/bsleys/projects/ooo-web/vendor/extensions/reorder_children/reorder_children_extension.rb:13
Re: [Radiant] Page Reordering
gah! sorry.. the migrate_from will only run on Radiant edge I'm afraid. If you could, just comment that line, see https://github.com/jomz/radiant-reorder_children-extension/commit/578645d81718665267e6976986f46a2ae7ee7bfd 2011/6/21 Bob Sleys bsl...@gmail.com getting an error running the migration for the reorder_children extension. rake radiant:extensions:reorder_children:migrate --trace (in /home/bsleys/projects/ooo-web) ** Invoke radiant:extensions:reorder_children:migrate (first_time) ** Invoke environment (first_time) ** Execute environment Could not load extension from file: reorder_children_extension. #NoMethodError: undefined method `migrate_from' for ReorderChildrenExtension:Class ** Execute radiant:extensions:reorder_children:migrate rake aborted! undefined method `migrate_from' for ReorderChildrenExtension:Class /home/bsleys/.rvm/gems/ruby-1.8.7-p334@ooo-web/gems/radiant-1.0.0.rc2/lib/simpleton.rb:16:in `method_missing' /home/bsleys/projects/ooo-web/vendor/extensions/reorder_children/reorder_children_extension.rb:13 -- Met vriendelijke groeten, Benny Degezelle Gorilla webdesign www.gorilla-webdesign.be
Re: [Radiant] Page Reordering
On 20 June 2011 15:40, Bob Sleys bsl...@gmail.com wrote: Does radiant-reorder-extension work with radiant 1.0.0.rc? Reordering the pages to make it easy to automatically create properly sorted menus Only problem is menus? Have you thought about r:navigation/ tags in a layout/snippet which will allow you to configure the menu order? Paul
Re: [Radiant] Page Reordering
On Mon, Jun 20, 2011 at 10:57 AM, Paul Noden nod...@nodster.co.uk wrote: On 20 June 2011 15:40, Bob Sleys bsl...@gmail.com wrote: Does radiant-reorder-extension work with radiant 1.0.0.rc? Reordering the pages to make it easy to automatically create properly sorted menus Only problem is menus? Have you thought about r:navigation/ tags in a layout/snippet which will allow you to configure the menu order? Paul Have you looked into https://github.com/dirkkelly/radiant-drag_order-extension -- Jim Gay Saturn Flyer LLC http://www.saturnflyer.com 571-403-0338
Re: [Radiant] Page Reordering
On 6/20/11 10:55 AM, Jim Gay wrote: On Mon, Jun 20, 2011 at 10:57 AM, Paul Nodennod...@nodster.co.uk wrote: On 20 June 2011 15:40, Bob Sleysbsl...@gmail.com wrote: Does radiant-reorder-extension work with radiant 1.0.0.rc? Reordering the pages to make it easy to automatically create properly sorted menus Only problem is menus? Have you thought aboutr:navigation/ tags in a layout/snippet which will allow you to configure the menu order? Paul Have you looked into https://github.com/dirkkelly/radiant-drag_order-extension In my experience, there are issues with drag order not maintaining ordering correctly. I ended up exposing the page ordering info (provided by drag_order) in the admin interface and allowing those ordinals to be edited directly, which is more reliably than using the drag and drop of drag_order. Wes
Re: [Radiant] Page Reordering
The problem with the r:navigation is you need to pass the pages you want added manually OR loop though them all via other tags like the children tags but then you need some way to order them. IE the idea here is to setup the menu to be automatically created from the listing of pages without having the add new pages into the menu manually. Drag order is perfect idea however as Wes states there are some issues with it not working reliably. I've found you can generally move pages down in order fine but not up. IE if you want the new page, always initially listed last, to be the first page you need to drag each of the pages listed before it down below it and not simply drag the new page to the top. IMHO there should be something built into Radiant by default that allows the end user to move/copy/reorder pages. Now that we have attachments, JavaScript, css etc it's the last basic function lacking. Don't get me wrong I love Radiant and have used it for many years now, forget which was the first version I used but adding, despite the bugs, drag_order has always been an automatic must have extension to fill a gap in the basic functionality of Radiant. Bob
Re: [Radiant] Page Reordering
Bob Sleys said the following on 06/20/2011 02:24 PM: The problem with the r:navigation is you need to pass the pages you want added manually OR loop though them all via other tags like the children tags but then you need some way to order them. IE the idea here is to setup the menu to be automatically created from the listing of pages without having the add new pages into the menu manually. Which limits you. I have a setup where not all my top level items should be in the menu. Yes, they are a limited set and I don't need to auto-generate them. Yes, some pages do other things. My top level not only has the main categories that go in the main menu but additional ones such as book reviews, links collection, site map, styles, Amazon store and more - extras. I'm well aware that I could have one top level item MAIN and all the menu-able site stuff under that, but I chose not to. YMMV. There are good reasons not to have an automatically generated main menu. In a word Discipline. Figure out your site design beforehand and don't get caught up in 'yes but ...' and 'oh I forgot ...' If I were to have a site that expanded I hope I'd design one that expanded in depth not in width! The idea of a menu with more than half a dozen items[1] frightens me - poor usability. But that does depend on how you 'chunk' it[2]. Which is why I use r:navigation Now within each category I *DO* have a hierarchy and within that I have a number of representations, including a sidebar menu that lets you navigate to children, siblings and parent. THAT, because of DRY, I have a snippet that works automatically. But not all pages have that. Often its better to use other formats. For example, many wikipedia pages have a layout that goes Introductory Text menu Body The menu giving links to parts of the body. That's easy to set up. The parts are actually children. But do you need reordering? Possibly not: it depends on the discipline of your design. I rarely do and I've never _ever_ used the drag to do so. Copy/re-order? Yes its there. I use the copy/move extension by Andrea Franz. http://gravityblast.com/category/radiant/ Rock Solid Now if that's to gross (as in heavy handed) for you, there is the 'reorder' extension. Little up and down arrows on the page listing. Shuffle them up one step at a time. Fine control. https://github.com/radiant/radiant/wiki/Reorder-Extension Try those two. [1] See the classic seminal paper Seven Plus or minus two: a limit to our information handling capability Martin, Journal of the American Philosophical Society, 1956, Vol. 101, No. 2, 343-352 http://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two http://www.psych.utoronto.ca/users/peterson/psy430s2001/Miller%20GA%20Magical%20Seven%20Psych%20Review%201955.pdf [2] Many pages have hundred of links, but look at NYTmes or BBC and see how they group items.
Re: [Radiant] Page Reordering
Thanks for the reply but I do find a couple of points interesting. First you rail against using the tree structure of the pages to generate menus and then point out that copy/reording is needed. To the first point the entire tree structure doesn't feed into the menu. It's easy to check for a page part and exclude that page and all it's children from the menu. Or reverse that and only include pages that have the page part. IE a filter in generating the menu. I don't control all the content on the sites I put up. What's so great about radiant is I can do the backup stuff get it all running, setup the basic site design etc. and then turn it over to the customer to add content. I need to make it as easy as possible for the customer to add/more/change pages. Back to the original pont of the post. I'm asking if anyone knows of a reorder extension that works with 1.0 of Radiant. All the ones I looked at including those posts here so far are quite old so AFAIK have a good chance of not working with 1.0. I'm also sugesting that it would be a good addition to core of radiant.
Re: [Radiant] Page Reordering
Bob Sleys said the following on 06/20/2011 09:59 PM: Thanks for the reply but I do find a couple of points interesting. First you rail against using the tree structure of the pages to generate menus and then point out that copy/reording is needed. Please re-read: that's not what I said. To the first point the entire tree structure doesn't feed into the menu. Which is what I *DID* say. It's easy to check for a page part and exclude that page and all it's children from the menu. Or reverse that and only include pages that have the page part. IE a filter in generating the menu. True, but the more processing you do the complicated things become and the more code the more room for mistakes and the more you deal with special cases and exceptions ... Yes, ANYTHING is possible if you're willing to put enough effort into coding it. No, I'd rather KISS and rely on good structure and design. I don't control all the content on the sites I put up. I have a quite a number of client sites like that. However I do have control over things like layouts, what extensions are loaded and the STRUCTURE. Users can add content: new articles, comments, but the content fits in with the STRUCTURE. They can't run it topsy-turvy or restructure it. What's so great about radiant is I can do the backup stuff get it all running, setup the basic site design etc. and then turn it over to the customer to add content. Yes. That's what I'm saying. I need to make it as easy as possible for the customer to add/more/change pages. But not restructure it. ... Back to the original pont of the post. I'm asking if anyone knows of a reorder extension that works with 1.0 of Radiant. All the ones I looked at including those posts here so far are quite old so AFAIK have a good chance of not working with 1.0. I'm also sugesting that it would be a good addition to core of radiant. Is there a particular reason you need to be at the bleeding edge? Are there more features there that are of greater importance than a working copy/move, because at 0.8.1 and 0.9.x I *KNOW FOR SURE* they work. And looking at them, I don't think its a big issue upgrading them. Its not as if you're adding some radically new functionality. I'm not sure I agree about adding to the core. Some of the sites I've developed while not actually static in content have no need for reordering once they are set up. Some of the blogs and BBoards are like that. Always new content, but it is added - the basic structure, layout, facilities etc, doesn't need to change.
