Deleting a page should make it go away in the pages tree and give you a 404 on dev and live sites, but the version history should be kept, so if the deletion was accidental, it can be undone. The deletion should show up under the history tab.

So you don't have to see every draft change.

I decided to change the page title for a page which is in draft or review mode. Now - even if I am in admin mode using the "dev.xxx...." url, it is still the old page title I see. Didn't try to switch the status to "published" yet, as I don't want to publish that version.

Could this be change to see the new title if the admin mode runs on the "dev" URL?

Cheers,
Andreas

Integration with the Dashboard extension so you can see what has

   changed recently

Integration with the Dashboard extension so you can see what pages have unpublished changes (drafts ahead of published versions)

The current help balloon you get when you click a version node in the timeline while editing a page isn't very nice. I would much prefer

• a larger, darker headline that says the version number
• a background image that looks more radianty

Prototip2's style is much nicer, but the license doesn't permit distribution.

Hi Jason,
first of all - a big thankyou for doing this extension. It looks very nice and I'm sure it will be useful for all of us.
I understand that you're planning on introducing versioning for snippets and layouts, as well as content. As I'm sure you're also aware, we've found versioning these becomes a big issue as soon as a Radiant site exceeds a certain size/complexity. And particularly when more than one person is working on it.
Our way (and probably lots of other folks) of resolving this has been to use the File System extension and Subversion (or Git). We've scoped the extension to just snippets and layouts (excludes content which stays as it is). The layouts and snippets live in Subversion, and when we deploy with Capistrano, they are raked in to whichever environment we deploy to.
So- I understand that in some cases having "Radiant versioning" on snippets and layouts would be useful. But for larger sites, using a developer's preferred version management tool can be an easier way of working. I'm not sure if you've already considered this, but it would be great if (when you do get around to versioning on snippets and layouts) either (1) the rake task is treated as just another change or (2) there is some way of keeping content versioned but ignore everything else.
Thanks again for such a great addition to Radiant.

regards

Ben

If I intend "just to save" and then continue my work, it might be a good idea, that no new version is created, at least not if the page isn't published yet. How about just saving the updated page into the current version?

Cheers,
Andreas

1. install Chronicle
   
2. greate some pages
   
3. install e.g. gallery extension
   4 ==> cannont edit any page
   
4. delete all entries from version table
   6 ==> pages are editable again

I think this has something to do with the yaml outline, maybe the yaml must be enriched with the current Page fields?

When acessing Layouts/Snippets page I got this error:

You have a nil object when you didn't expect it!
The error occurred while evaluating nil.name

Extracted source (around line #26):
26: %td.status{:class => "#{snippet.status.name.downcase}-status"}
Extracted source (around line #31):
31: %td.status{:class => "#{layout.status.name.downcase}-status"}

Radiant 0.8.0(gem) and chronicle installed today

Has anyone taken a look at what might be necessary to get copy/move to play nice with chronicle?

In chronicle/app/helpers/admin/preview_helper.rb change line 13 to

host =~ /^localhost/ ? host : Radiant::Config['dev.host'] || ("dev." + host)