I guess I mist this when posted, but this is really cool. Thanks !
On 9/13/07, Loren Johnson [EMAIL PROTECTED] wrote:
I'm a little late to the discussion, but here is the solution I
recently implemented for a client based on similar needs:
Damonica Miller wrote:
Sean Cribbs wrote:
Ideally you shouldn't use WEBrick in a production setting. I would
investigate Mongrel or FCGI, both of which can be 'daemonized'.
Sean
Sean, thanks for your rapid response. i did read that on the radiant
page after the fact
Peter,
I'm glad this looks like something you can use. Let me know how it
goes. The extension was developed for a client whose translated site
has not yet been put into production so this extension is somewhat
untested. It works and hopefully your purposes won't reveal any dark/
sharp
Hi list,
we developed an extension which adds multi-lingual capabilities to
Radiant 1.6.3, without the need to make multiple trees in your page-
hierarchy.
The extension allows a site to have pages and snippets in several
languages; with a default language (currently dutch, but easy to
No problem, thanks for the headsup anyway
if I run into something I will try to fix it and mail you the patch.
Peter.
On 10/10/07, Loren Johnson [EMAIL PROTECTED] wrote:
Peter,
I'm glad this looks like something you can use. Let me know how it
goes. The extension was developed for a
Sounds really promosing..Trying this out as well :D
P
On 10/10/07, Bernard Grymonpon [EMAIL PROTECTED] wrote:
Hi list,
we developed an extension which adds multi-lingual capabilities to
Radiant 1.6.3, without the need to make multiple trees in your page-
hierarchy.
The extension allows a
Peter Berkenbosch wrote:
Any news on this ticket ? Could someone patch it against the trunk ???
Committed:
http://dev.radiantcms.org/radiant/changeset/547
There were a few white space issues and I noticed that the tags didn't
work when rendering page's parts that were included into another
I'm trying to figure out a way to track whenever a given page's rendered
output may have changed.
Kind of tricky since changing the layout or, worse yet, a snippet could
change the page's output. And then, of course, there are those silly
extensions people keep making :-D with all their
I'm trying to figure out a way to track whenever a given
page's rendered
output may have changed.
I was doing some thinking about this recently, but haven't had a go at
implementing yet.
My basic idea was:
Add a listener that hooks into after_initialize on page, snippet and layout.
I saw in the changelog that Radiant 0.6.3 is using the 1.5.0 release
of Prototype, but updating the radiant gem does not update the
javascripts directory.
Should there be a rake:public:update task or something like that?
Running the radiant command on the directory will overwrite any
I saw in the changelog that Radiant 0.6.3 is using the 1.5.0 release
of Prototype, but updating the radiant gem does not update the
javascripts directory.
Should there be a rake:public:update task or something like that?
-Jim
___
Radiant mailing
Daniel Sheppard wrote:
I saw in the changelog that Radiant 0.6.3 is using the 1.5.0 release
of Prototype, but updating the radiant gem does not update the
javascripts directory.
Should there be a rake:public:update task or something like that?
Running the radiant command on the
I saw in the changelog that Radiant 0.6.3 is using the 1.5.0 release
of Prototype, but updating the radiant gem does not update the
javascripts directory.
Should there be a rake:public:update task or something like that?
Running the radiant command on the directory will overwrite any
13 matches
Mail list logo
