Re: [Radiant] Looking for draft+history extension collaborators or contractors
Well, I for one haven't. I've been meaning to take a look at some other extensions and to see if they'll do. I've also been dreaming about how it might work to have a git interface to the versioned data as well, so for heavy-duty stuff like branching and merging you could use git tools. Right now I'm getting RedCloth compatible with Ruby 1.9, but then I'd be available to collaborate on something. Jason On Feb 18, 2009, at 6:32 PM, Joe Van Dyk wrote: Anyone make any progress on this? On Tue, Sep 2, 2008 at 11:39 AM, Jason Garber j...@jasongarber.com wrote: I'm needing an extension that will show the history of pages/snippets/layouts as well as allowing concurrent drafts of published pages/snippets/layouts. The basic structure is that there's a series of versions of the current page — some of which are drafts and some of which are published — and the dev site shows the latest draft and the live site shows the latest published version. Features I'm anticipating: * History of who changed what (including titles and other meta info, page parts, snippets, layouts) for the whole site or an individual page, including a diff so you can see at a glance exactly what changed with a toggle to see only changes between published versions or all the drafts in between and a timeline to visualize the changes. * Ability to revert to a prior version (actually just copy the old version to a new draft). * Ability to work on a single draft version and save it while an older published version is still live (like concurrent_drafts extension but without the scheduling and all the fields are draftable, not just the page parts' content). Does this resonate with anyone else? Already working on a similar extension? Anyone wanting to collaborate on it? Any freelancers want to pick up the job? Good ideas about what to name this extension? Jason Garber___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Looking for draft+history extension collaborators or contractors
Anyone make any progress on this? On Tue, Sep 2, 2008 at 11:39 AM, Jason Garber j...@jasongarber.com wrote: I'm needing an extension that will show the history of pages/snippets/layouts as well as allowing concurrent drafts of published pages/snippets/layouts. The basic structure is that there's a series of versions of the current page — some of which are drafts and some of which are published — and the dev site shows the latest draft and the live site shows the latest published version. Features I'm anticipating: * History of who changed what (including titles and other meta info, page parts, snippets, layouts) for the whole site or an individual page, including a diff so you can see at a glance exactly what changed with a toggle to see only changes between published versions or all the drafts in between and a timeline to visualize the changes. * Ability to revert to a prior version (actually just copy the old version to a new draft). * Ability to work on a single draft version and save it while an older published version is still live (like concurrent_drafts extension but without the scheduling and all the fields are draftable, not just the page parts' content). Does this resonate with anyone else? Already working on a similar extension? Anyone wanting to collaborate on it? Any freelancers want to pick up the job? Good ideas about what to name this extension? Jason Garber___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Looking for draft+history extension collaborators or contractors
On Sep 22, 2008, at 8:10 PM, Joe Van Dyk wrote: On Sat, Sep 6, 2008 at 12:34 PM, Joe Van Dyk [EMAIL PROTECTED] wrote: On Tue, Sep 2, 2008 at 12:39 PM, Jason Garber [EMAIL PROTECTED] wrote: I'm needing an extension that will show the history of pages/snippets/layouts as well as allowing concurrent drafts of published pages/snippets/layouts. The basic structure is that there's a series of versions of the current page — some of which are drafts and some of which are published — and the dev site shows the latest draft and the live site shows the latest published version. Features I'm anticipating: * History of who changed what (including titles and other meta info, page parts, snippets, layouts) for the whole site or an individual page, including a diff so you can see at a glance exactly what changed with a toggle to see only changes between published versions or all the drafts in between and a timeline to visualize the changes. * Ability to revert to a prior version (actually just copy the old version to a new draft). * Ability to work on a single draft version and save it while an older published version is still live (like concurrent_drafts extension but without the scheduling and all the fields are draftable, not just the page parts' content). Does this resonate with anyone else? Already working on a similar extension? Anyone wanting to collaborate on it? Any freelancers want to pick up the job? Good ideas about what to name this extension? I need something like that. I might be able to help work on it. Other thing I need is to only let a certain user role be able to push out all the changes to production. Has anyone done any work on this yet? Not yet AFAIK. This week I was busy wrapping up a couple other extensions, like textile_editor, but I plan to tackle this extension next week. Jason___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Looking for draft+history extension collaborators or contractors
On Sat, Sep 6, 2008 at 12:34 PM, Joe Van Dyk [EMAIL PROTECTED] wrote: On Tue, Sep 2, 2008 at 12:39 PM, Jason Garber [EMAIL PROTECTED] wrote: I'm needing an extension that will show the history of pages/snippets/layouts as well as allowing concurrent drafts of published pages/snippets/layouts. The basic structure is that there's a series of versions of the current page — some of which are drafts and some of which are published — and the dev site shows the latest draft and the live site shows the latest published version. Features I'm anticipating: * History of who changed what (including titles and other meta info, page parts, snippets, layouts) for the whole site or an individual page, including a diff so you can see at a glance exactly what changed with a toggle to see only changes between published versions or all the drafts in between and a timeline to visualize the changes. * Ability to revert to a prior version (actually just copy the old version to a new draft). * Ability to work on a single draft version and save it while an older published version is still live (like concurrent_drafts extension but without the scheduling and all the fields are draftable, not just the page parts' content). Does this resonate with anyone else? Already working on a similar extension? Anyone wanting to collaborate on it? Any freelancers want to pick up the job? Good ideas about what to name this extension? I need something like that. I might be able to help work on it. Other thing I need is to only let a certain user role be able to push out all the changes to production. Has anyone done any work on this yet? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Looking for draft+history extension collaborators or contractors
On Sep 2, 2008, at 4:11 PM, Jim Gay wrote: I'm assuming that it's a misstatement, but did you really mean to say that there are some versions of a page that are published, meaning more than one published version of the same page? Yes, I did, but maybe I should have said there's only ever one active published version and one active draft version. Let me try to illustrate: --+ #1 - 8:00 - Draft - initial version, only visible in dev --+ #2 - 8:20 - Published - made some changes to that initial version and published. Now live. --+ #3 - 10:00 - Draft - made a new change, but wanted to look at it in dev without disturbing live version --+ #4 - 10:01 - Draft - that wasn't quite right, so tweaking a bit --+ #5 - 10:02 - Published - yes, now it's good, so publish it --+ #6 - 11:58 - Draft - started adding a new paragraph, but had to go to lunch, so saved So, the world sees the page live as it is at #5, but the editor looking at the dev site sees version #6. Another way of thinking about it: #1-4 are past, #5 is present, and #6 is future. I'm constantly making a change in the admin interface, saving the page, and then looking at the page to see the change, so if it's me, there would be about 20 draft versions between each published version. :-) Anticipating this, I want to make a checkbox to hide draft versions, so the above illustration would be simplified to --+ #2 - 8:20 - Published --+ #5 - 10:02 - Published This is probably the way a site administrator would prefer to keep tabs on changes editors are making. It's important to save the intermediate (draft) versions, though, because you may make a good change, save, make a bad change, save, and then want to undo the bad one. Take a look at the concurrent_draft extension. It allows you to schedule a draft of a page, snippet or layout for publication. http://github.com/avonderluft/radiant-concurrent_draft-extension/ tree/master I looked at it the day it came out and had high hopes for it, but it only keeps a draft of the content. If you modify the title, slug, etc., the change is immediate. I want the entire page/snippet/layout to be draftable/versioned as a complete model, so I can add/delete page parts, change the slug, and so forth without messing up the published one. Plus, as I mentioned, scheduling the promotion of drafts isn't something I (or most people, I imagine) have a need for. Perhaps two extensions might be more appropriate, one for drafts (the future) and one for versioning (the past), but I thought we could kill two birds with one stone by having the drafts be versions too, but versions that exist ahead of the live version. I have no immediate need for holding onto old versions so I have no current plans to add that, but if it were unobtrusive and intuitive I'd certainly be interested. Yes! Unobtrusive and intuitive — I'm thinking just a little page history link on the edit page down by where it says the publisher and timestamp. Maybe a history tab, too, that shows all changes on the site. Drafts would be like in concurrent_draft--it's so intuitive you almost don't know you're making a draft. Sure. Are you planning for it to be open source? I'm sure there would be plenty of interest in the community. Absolutely. Even if we paid someone to write it, it must be open source. Good ideas about what to name this extension? How about chronicle? That's a good idea. I wish there was a way to capture the idea that it's history and drafts all in one. Thanks for all the feedback! Oh, and two features I forgot to list in the first email: * Deleting a page makes it go away in the pages tree and will give you a 404 on dev and live sites, but the version history is kept, so if the deletion was accidental, it can be undone * It should be compatible with page_attachments, so if you add/delete/ replace attachments on the draft, it doesn't affect the live version. Jason___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Looking for draft+history extension collaborators or contractors
On Sep 2, 2008, at 11:32 PM, Jason Garber wrote: Perhaps two extensions might be more appropriate, one for drafts (the future) and one for versioning (the past), but I thought we could kill two birds with one stone by having the drafts be versions too, but versions that exist ahead of the live version. Quickly and quietly chiming in, I think two extensions would probably be best. The 'do one thing well' ethos so to speak. I'm more than interested in a versions extension, but less so a drafts extension such as concurrent_drafts. So if you find a good way to keep track of the past in Radiant, please pass it on. And feel free to contact me off-list if you'd like to coordinate a new one. -- Janson Hartliep p| 616.931.4636 x101 e| [EMAIL PROTECTED] w| http://www.elevatorup.com Elevator UP - a Web Hosting Company ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Looking for draft+history extension collaborators or contractors
On Sep 2, 2008, at 3:39 PM, Jason Garber wrote: I'm needing an extension that will show the history of pages/ snippets/layouts as well as allowing concurrent drafts of published pages/snippets/layouts. The basic structure is that there's a series of versions of the current page — some of which are drafts and some of which are published — and the dev site shows the latest draft and the live site shows the latest published version. I'm assuming that it's a misstatement, but did you really mean to say that there are some versions of a page that are published, meaning more than one published version of the same page? Features I'm anticipating: * History of who changed what (including titles and other meta info, page parts, snippets, layouts) for the whole site or an individual page, including a diff so you can see at a glance exactly what changed with a toggle to see only changes between published versions or all the drafts in between and a timeline to visualize the changes. * Ability to revert to a prior version (actually just copy the old version to a new draft). * Ability to work on a single draft version and save it while an older published version is still live (like concurrent_drafts extension but without the scheduling and all the fields are draftable, not just the page parts' content). Does this resonate with anyone else? Already working on a similar extension? Take a look at the concurrent_draft extension. It allows you to schedule a draft of a page, snippet or layout for publication. http://github.com/avonderluft/radiant-concurrent_draft-extension/tree/master I began work on a drafts extension which plans to manage drafts on a page part basis (rather than the entire page) but I haven't been able to put a lot of time into it. I believe that in most regular use, authors will create draft content for page parts rather that entire pages so I'm creating it to do that. It is premature to suggest using it, but I'd love any help if you are interested http://github.com/saturnflyer/radiant-drafts-extension/tree/master I have no immediate need for holding onto old versions so I have no current plans to add that, but if it were unobtrusive and intuitive I'd certainly be interested. Perhaps the snapshot extension has some ideas in it for you: http://aitor.name/snapshot.tar.gz (not sure how up-to-date that is) Anyone wanting to collaborate on it? Any freelancers want to pick up the job? Sure. Are you planning for it to be open source? I'm sure there would be plenty of interest in the community. Good ideas about what to name this extension? How about chronicle? Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Looking for draft+history extension collaborators or contractors
Take a look at the concurrent_draft extension. It allows you to schedule a draft of a page, snippet or layout for publication. http://github.com/avonderluft/radiant-concurrent_draft-extension/tree/master I began work on a drafts extension which plans to manage drafts on a page part basis (rather than the entire page) but I haven't been able to put a lot of time into it. I believe that in most regular use, authors will create draft content for page parts rather that entire pages so I'm creating it to do that. It is premature to suggest using it, but I'd love any help if you are interested http://github.com/saturnflyer/radiant-drafts-extension/tree/master I have no immediate need for holding onto old versions so I have no current plans to add that, but if it were unobtrusive and intuitive I'd certainly be interested. That is the strategy that concurrent_draft takes -- each part has 'content' and 'draft_content' fields. The nice thing about that is that we could treat parts, snippets and layouts almost identically, with some tweaks for pages (and propagating publishing to the parts). There's no historical versioning, though. Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Looking for draft+history extension collaborators or contractors
On Sep 2, 2008, at 4:21 PM, Sean Cribbs wrote: Take a look at the concurrent_draft extension. It allows you to schedule a draft of a page, snippet or layout for publication. http://github.com/avonderluft/radiant-concurrent_draft-extension/tree/master I began work on a drafts extension which plans to manage drafts on a page part basis (rather than the entire page) but I haven't been able to put a lot of time into it. I believe that in most regular use, authors will create draft content for page parts rather that entire pages so I'm creating it to do that. It is premature to suggest using it, but I'd love any help if you are interested http://github.com/saturnflyer/radiant-drafts-extension/tree/master I have no immediate need for holding onto old versions so I have no current plans to add that, but if it were unobtrusive and intuitive I'd certainly be interested. That is the strategy that concurrent_draft takes -- each part has 'content' and 'draft_content' fields. The nice thing about that is that we could treat parts, snippets and layouts almost identically, with some tweaks for pages (and propagating publishing to the parts). There's no historical versioning, though. Thanks. I'll have to look more closely at it, perhaps my work is redundant. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Looking for draft+history extension collaborators or contractors
Sean, Is there any reason not to use technoweenie's Acts As Versioned plugin (http://github.com/technoweenie/acts_as_versioned/tree/master) for that? Strikes me a natural thing to do. Only that we didn't need versioning for the current application of concurrent_draft. Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
