Re: [Radiant] Handling multiple languages
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: http://svn.fn-group.com/radiant_extensions/language_switch I think it may be useful as-is but at least should be worth referencing. There is some hackery involved with using the cookies to store the current language preference and a set of tags for allowing the user to switch. The default is the browser language...the README reads thus: = Language Switch This extension creates a set of tags and page routing which responds to a cookie stored language variable that is settable and resettable through the language query parameters (e.g. http://yoursite.com/your_page?language=en). When this parameter isn't present the language selected will be based upon the current cookie value for language, or if this value is also blank then the default acceptable languages in the client's browser will be responded to. = Full text sample/text code (no, there is no Bulgarian sample content... that's to show that the default work :) h2Language Switcher/h2 r:language_switch language=enEnglish/r:language_switch | r:language_switch language=esSpanish/r:language_switch | r:language_switch language=frFrench/r:language_switch | r:language_switch language=deGerman/r:language_switch | r:language_switch language=bgBulgarian/r:language_switch | r:language_resetReset/r:language_reset h2Content/h2 r:language r:matches value=es h4Español/h4 pDiez soldados estadounidenses murieron a causa de bombas en carreteras y al estrellarse un helicóptero en Irak, mientras cinco británicos fueron secuestrados en el Ministerio de Hacienda iraquí, dijeron el martes las autoridades./p /r:matches r:matches value=fr h4Français/h4 pCes dernières semaines, le Brésil s'est d'ailleurs souvenu de la répression qui avait enrayé une vague de violence, il y a un an à Sao Paulo, avec un très lourd bilan : 493 morts en à peine six jours. Entre les 12 et 19 mai 2006, le Premier commando de la capitale (PCC), l'un des gangs mafieux les plus puissants d'Amérique latine, avait orchestré une série d'attaques contre les forces de l'ordre, semant la terreur parmi les 11 millions d'habitants de la ville./p /r:matches r:matches value=de h4Deutsche/h4 pDie Innenminister von Bund und Laendern beraten heute und morgen ueber den Poli zeieinsatz waehrend des G8-Gipfels in der kommenden Woche in Heiligendamm. Bis zu 16.400 Polizisten sollen waehrend des Treffens der Staats- und Regie rungschefs der fuehrenden Industriena tionen zum Einsatz kommen. Wie nah Glo balisierungsgegner dem Tagungsort kom men duerfen, ist noch unklar. Gestern wurde der zwoelf Kilometer lange Zaun um das Gelaende geschlossen. Fuer eine Woche duerfen nur die Bewohner und besonders Berechtigte in das Gebiet./p /r:matches r:matches value=en default=true h4English (default)/h4 pIs new software a key component to growth or essential to your new business idea? Rapid prototyping and constant evaluation can insure you only build exactly what need; nothing more, nothing less./p /r:matches /r:language h3Browser Languages/h3 pr:languages //p Thanks, Loren Johnson www.hellovenado.com On Sep 11, 2007, at 2:29 AM, Aitor Garay-Romero wrote: For this idea we also need parts for layouts and snippets, since they must be translated too. /AITOR On 9/10/07, Sylvestre Mergulhão [EMAIL PROTECTED] wrote: On 9/10/07, Aitor Garay-Romero [EMAIL PROTECTED] wrote: - define different page parts for the language versions. For example, have the parts body_en, body_fr and body_es. Or just body, fr, es. They could be special parts or not. I agree with this, some weeks ago I spent some time thinking about it. The dafult language could be the browsers one, or other after selected by the user. -- Sylvestre Mergulhão - Free Software Development - -- http://mergulhao.info http://www.euemeu.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- met vriendelijke groet,
Re: [Radiant] [ANN] Radiant 0.6.3 - Rock Grinder Release
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 (unfortunately i have to get this up and running a week ago so i'm having to do a lot of things in a hurry--not good i know, but it's for a class and i don't have any say in the timeline). but my question was because there was no return to the prompt(?). i'm not sure if that is even the right termbut what i mean is that usually in the terminal after you execute a command '[EMAIL PROTECTED]' displays followed by the cursor. that didn't happen but things seem to have worked--so do i need to type in another command or am i all set (and hence clear to go investigate mongrel/fcgi and also how to daemonize while i'm at it)? thanks, damonica If you can keep the shell running, you don't need to do anything else. At the point you described, WEBrick was waiting for its first request. Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Handling multiple languages
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 corners. Good Luck, Loren On Oct 10, 2007, at 6:20 AM, Peter Berkenbosch wrote: 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: http://svn.fn-group.com/radiant_extensions/language_switch I think it may be useful as-is but at least should be worth referencing. There is some hackery involved with using the cookies to store the current language preference and a set of tags for allowing the user to switch. The default is the browser language...the README reads thus: = Language Switch This extension creates a set of tags and page routing which responds -- met vriendelijke groet, Peter Berkenbosch ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [extension] site-language - multilingual capabilities for radiant 1.6.3
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 change in the source code. We didn't test this extension with other extensions, or how it behaves on a running installation, so install this with care. It works for us, and we will continue to add features, but this is a first version which gives us what we need. The major advantages are - no need to have multiple site-hierarchies in your pages - auto-redirection to the default language - use of globalize, which works wonderful Disadvantages - includes pages which are copied from Radiant 1.6.3 (view/admin/page/ _node.rhtml and snippet/index.rhtml) - includes code from the site-controller within the extension - currently only works with Radiant 1.6.3 (due to both previous points) More info and download here: http://www.openminds.be/article/radiant- site-language-extension TAKE CARE: you need to apply a patch to globalize! See this link: http://trac.globalize-rails.org/trac/globalize/ticket/172 Kind regards, Bernard Grymonpon Jan De Poorter Openminds BVBA - Rails hosting by professionals - http:// www.openminds.be/ ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Handling multiple languages
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 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 corners. Good Luck, Loren On Oct 10, 2007, at 6:20 AM, Peter Berkenbosch wrote: 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: http://svn.fn-group.com/radiant_extensions/language_switch I think it may be useful as-is but at least should be worth referencing. There is some hackery involved with using the cookies to store the current language preference and a set of tags for allowing the user to switch. The default is the browser language...the README reads thus: = Language Switch This extension creates a set of tags and page routing which responds -- met vriendelijke groet, Peter Berkenbosch ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- met vriendelijke groet, Peter Berkenbosch ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [extension] site-language - multilingual capabilities for radiant 1.6.3
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 site to have pages and snippets in several languages; with a default language (currently dutch, but easy to change in the source code. We didn't test this extension with other extensions, or how it behaves on a running installation, so install this with care. It works for us, and we will continue to add features, but this is a first version which gives us what we need. The major advantages are - no need to have multiple site-hierarchies in your pages - auto-redirection to the default language - use of globalize, which works wonderful Disadvantages - includes pages which are copied from Radiant 1.6.3 (view/admin/page/ _node.rhtml and snippet/index.rhtml) - includes code from the site-controller within the extension - currently only works with Radiant 1.6.3 (due to both previous points) More info and download here: http://www.openminds.be/article/radiant- site-language-extension TAKE CARE: you need to apply a patch to globalize! See this link: http://trac.globalize-rails.org/trac/globalize/ticket/172 Kind regards, Bernard Grymonpon Jan De Poorter Openminds BVBA - Rails hosting by professionals - http:// www.openminds.be/ ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- met vriendelijke groet, Peter Berkenbosch ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [Radiant-Dev] Re: tags for dev mode. http://dev.radiantcms.org/radiant/ticket/517
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 page. So I fixed these issues. Thanks. -- John Long http://wiseheartdesign.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Detecting Page Changes
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 dynamic tags. Does anyone have any clever suggestions to deduce that the page's output may be changed? I'd love to have an event (or set of events) to trigger the check but would settle for a smart polling solution (but it should scale well). BTW, I'd love to be able to know that the page had changed but, for my purposes, even being able to suspect it's guilt would be sufficient. -- View this message in context: http://www.nabble.com/Detecting-Page-Changes-tf4603945.html#a13145924 Sent from the Radiant - User mailing list archive at Nabble.com. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Detecting Page Changes
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. Hook into SiteController - reset the listener before rendering the page, and then read out the list of accessed objects after the render is complete and dump that list to the db. Have a listener that hooks into after_save on page, snippet and layout. Read the list of urls that accessed that object and clear them all - for pages also clear anything that has accessed the parent page. This should give pretty much complete coverage for pages with content that depend only on db changes. Any content that is time sensitive though, you'll have to have some other mechanism for. Dan. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] updating public
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 changed files (prompting before overwrite). Just don't let it overwrite things that you've changed by hand. Dan. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] updating public
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 list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] updating public
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 directory will overwrite any changed files (prompting before overwrite). Just don't let it overwrite things that you've changed by hand. Actually, try this: rake radiant:update To update all the significant files in his public and scripts directory. -- John Long http://wiseheartdesign.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] updating public
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 changed files (prompting before overwrite). Just don't let it overwrite things that you've changed by hand. Actually, try this: rake radiant:update To update all the significant files in his public and scripts directory. Duh. Thanks. Sure enough, there it is in the announcement... Sorry to bother http://radiantcms.org/blog/archives/2007/10/06/radiant-0-6-3---rock- grinder-release/ ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
