The file_system extension exists for this purpose. Check it out:
http://github.com/nelstrom/radiant-file-system-extension/tree/master
I should warn you that it is still under development, so if you do use
it, take care! I would appreciate feedback on any problems you
encounter.
Drew
On
I just had a crazy idea.
I'm looking for a way for users to have a draft version of the site.
When it's ready, they click a button and the pages/snippets/layouts
that are published get transferred over to the new site.
What if:
When they click Publish Site:
* test site does a rake
Back in December 2007 I wrote a quickie extension for someone to have
two separate sites, one being preview and one being live. In the end,
we decided it would be easiest to copy a SQLite3 database file from the
preview site to the live site (luckily on the same box). No version
control, but
I wrote an extension that is being used in production that does
something very similar. We have a staging environment and a
production environment. The production environment is read-only. The
users make all their changes on the staging environment. When they
are ready to migrate the changes
Will we ever see the light of day for this feature. I personally despise
editing code/indent-heavy layouts/snippets in Radiant. What are the
limitations that prevent this feature from being implemented?
--
Posted via http://www.ruby-forum.com/.
___
Arik Jones wrote:
Will we ever see the light of day for this feature. I personally despise
editing code/indent-heavy layouts/snippets in Radiant. What are the
limitations that prevent this feature from being implemented?
Would it help you to use an external text editor of your choice for
