Manuel,
Many people have asked for this. Please Do Investigate.
Sean
Manuel Meurer wrote:
Hello world.
I was thinking about creating an extension that saves the edit history
for pages, layouts, snippets etc.
That way you could go back to previous versions, perhaps make diffs
between
On Mon, Jan 5, 2009 at 11:14 AM, Andreas Roedl andreas.ro...@googlemail.com
wrote:
A Rails plugin that uses Git to version ActiveRecord fields:
http://github.com/courtenay/acts_like_git/tree/master
+1 for Acts as Git instead of Acts as Versioned
Wow, lots of ideas here.
I will go for the acts_as_versioned plugin as Andreas suggested.
Once that is working we can think about saving incremental changes,
different published versions etc.
Tim, why would you like the git option better?
For me it seems cleaner to have all your stuff in one
On 5-Jan-09, at 9:09 AM, Manuel Meurer wrote:
Wow, lots of ideas here.
I will go for the acts_as_versioned plugin as Andreas suggested.
Once that is working we can think about saving incremental changes,
different published versions etc.
Probably wise ;)
Tim, why would you like the git
On Mon, Jan 5, 2009 at 10:52 AM, Adam van den Hoven
adam.vandenho...@gmail.com wrote:
You should also consider that if you're going to keep a version history
that only one revision (and certainly not necessarily the current
revision) should be published. This will allow you make a number of
Hello world.
I was thinking about creating an extension that saves the edit history
for pages, layouts, snippets etc.
That way you could go back to previous versions, perhaps make diffs
between versions etc.
Has something like that ever been done before? (Wow, what a dramatic
sounding
Hello Sean.
Searching the mailing list I understand that the Radiant Podcast has
been generated by radius tags and served by radiant itself.
Wouldn't you mind to share some details about the tags used, the
page/sub-page architecture, etc.? For example how has been generated
the podcast.xml page?
You should also consider that if you're going to keep a version
history that only one revision (and certainly not necessarily the
current revision) should be published. This will allow you make a
number of changes to a page (especially useful if you extend the page
preview extension to
hello all, I have downloaded and installed Radiant CMS. I followed the
instructions in the handbook, and was able to get the application running
using script/server -e production. Now i'm in the process of using Phfusion
Passenger to server the application. What are the necessary changes that
Since Radiant is meant for more medium scale projects, is there any real
drawback to using an SQLite3 database instead of the heavier-duty MySQL?
Sort of thinking out loud here. I have my projects now managed with git, but
to move the database content from my local machine to the production server
Luigi,
I've written an audio player extension[1] for radiant, which you might
find useful. It allows you to upload mp3 files, without requiring any
other asset management extensions (e.g. page_attachments or
paperclipped). It also provides radius tags for embedding a flash mp3
player.
Saša Babić wrote:
Its really simple:
@mohit all:
I've made a draft page for the Summer Reboot:
http://wiki.radiantcms.org/Deploying_your_first_site
Someone should, please, do a sanity check on it. Also, english is not
native for me, so maybe that should be checked, too.
Side note: its
thank you for taking the time to put the article together.
Jason
On Mon, Jan 5, 2009 at 9:20 PM, Saša Babić s...@pharmacy.bg.ac.rs wrote:
Saša Babić wrote:
Its really simple:
@mohit all:
I've made a draft page for the Summer Reboot:
13 matches
Mail list logo
