Closed (fixed)
Project:
Rearrange child pages
Version:
6.x-1.0-rc3
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
5 Jan 2011 at 20:00 UTC
Updated:
3 Mar 2011 at 01:51 UTC
Jump to comment: Most recent
Comments
Comment #1
btopro commentedTry this, I think it'll provide the correct integration. I'm testing it right now but it appears to function correctly, just need to make sure it still respects permissions correctly
Also, you do a db check for if something has children when this property should be along for the ride in the node. Instead of the DB call you should just be able to verify with $node->book['has_children'] == 1 as long as the book property is there it should know if it has children or not
Comment #2
kyle_mathews commentedThis sounds very cool. Especially if you could load the form within a little popup, that make quick edits even quicker.
Comment #3
nirbhasa commentedThis looks great - im very happy to look at this. (Also Id never heard of the Outline Designer module before, but it seems to be just what I need!!!) Also, you're right about the $node object.
I'm on vacation at moment, but I hope to look at this in the next week. Thanks!
Comment #4
btopro commentedYeah, most people haven't but that's the typical reaction ;)
An issue that's still in OD's issue queue that this module seems like it might be able to help out with as well is this #794732: Expose interface to normal users...
You're project exposes based on just the admin-book-outlines permission, it would be awesome if we could come up with a permission that allowed someone to reorder the child pages of the content they have the ability to edit (or the admin book outlines permission).
Shoot me an email after you get back from vacation, I'd like to discuss plans for outline designer more as your project complements it extremely well.
Comment #5
btopro commentedOr I guess we could allow people with the "add content to books" permission to do it since they already have access to the outline tab. Maybe this module instead of adding it's tab it could add it's tab and remove the outline tab (or hijack it entirely) since this will provide a more usable solution then the outline select fields :p
Comment #6
btopro commentedHad any thought about this project / patch? Honestly I'd really like to just include this as a outline designer sub-module. I have an organic groups sub-module already and I think this would be another great one to add in. You could be added on as a project co-maintainer if you're interested. If you don't want to merge I'd just ask that you roll in the patch here since really I think most of my users should be using your module as well.
Comment #7
nirbhasa commentedHmmm..you know what - I think merging into the outline designer module would actually be a good idea. Theres way too many modules out there, and I dont want to be accused of adding to the cruft.
IMHO, I wouldn't even include it as a sub-module, i would just add the hooks and settings. If they just want the rearrange child pages feature, we could arrange that via permissions or something. What do you think?
Comment #8
btopro commentedThat sounds good to me (via a permission). I think this should use 2 permissions for this...
If they have admin book outlines then they can do it to anything
or a new permission for "outline own child content" (or something like that) so that if you own the node you're on (and it has items under it) then you can use the outline designer on it.
Thoughts?
Comment #9
nirbhasa commentedSounds great. Im a little tied up for next few days, so won't be able to create a patch before the weekend. But ill add a little notice now warning that the module will be merged.
Comment #10
btopro commentedawesome. When you create a patch please add it as a new issue in the outline designer issue queue referencing this thread. Once it's accepted (which I mean as long as it works I obviously will) I'll roll it in after the Git migration.
Thanks!
Comment #11
btopro commentedI'm going to be working on rolling this into outline designer tomorrow as a sub module (much in the way that OG was integrated). I love the functionality but don't want to freak out my user-base if tabs start showing up in their UIs that they don't expect :)
Comment #12
nirbhasa commentedPlease do! Things have been a bit nuts my end, and Im not sure when i can sit down and look at it. If you want to move this issue into the Outline Designer queue that's fine. Then i'll point everyone towards the outline designer project page when its done
Comment #13
btopro commentedI'll create a new issue in outline designer and reference this one, hopefully I'll have it added by the end of the day, working in a few other patches atm.
Comment #14
btopro commentedThis can now be found in Outline Designer 1.3, go get it! http://drupal.org/node/1063848
Comment #15
nirbhasa commentedThanks btopro! I've update module page accordingly.
Can I refer outstanding feature requests to the Outline Designer issue queue, and you can judge them on their merits?
Comment #16
btopro commentedthat sounds good to me