[Radiant] [ANN] Globalize2 extension for site content I18n
Announcing the Radiant CMS Globalize2 extesion: http://bit.ly/246yd. The Globalize2 extension allows you to easily translate the content of your site into any number of languages. It is uses on the Globalize2 Rails plugin based on the I18N API available in Rails since version 2.2. This extension is a complete rewrite of the original Radiant Globalize extesion, based on the Globalize v1 Rails plugin. Available on Github: http://github.com/Aissac/radiant-globalize2-extension. Be sure to checkout the branch for the correct Radiant version for use in your project. It requires Radiant 0.8 or greater, tested with Radiant 0.9 RC1. Happy I18n in your sites! -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS Usage Questions -- I Need Feedback
On Fri, Oct 9, 2009 at 10:32 AM, Chris Parrish chris.parrish-forumm...@swankinnovations.com wrote: I'm upgrading/fixing/refactoring SnS right now -- partly to resolve some issues with 0.8.x and partly to get it ready for 0.9 -- and I could use some user feedback... This is exciting! Over at Aissac we have used SnS and SnS Minify for more than 10 sites and it goes into every new Radiant project. 1. Does anyone use custom values for the SnS settings? These include: * css_dir * js_dir * css_mime * js_mime We have never used custom values for these settings. John has suggested I simplify SnS by fixing these values to defaults (convention over configuration). Would this cause any problems for you or your users? Would anyone even notice? 2. Do most of you use SnS Minify along with SnS? Would anyone be opposed to my incorporating it into SnS? I don't mind leaving it as a separate extension but there's no need to make people install two extensions if we're all using both. We install SnS Minify for each SnS installation, because the primary reason for us to use SnS is to speed up asset serving. Fewer requests are good and adding minification even is better. Also, we couple this with gzip compression in Apache. It would make sense to bundle these in the one extension. There is no overhead for having it without being used as far as I can tell. Thanks! -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [RFC] Extensions as gems
Hi all! This is a request for comments regarding the possibility of packaging Radiant extensions as gems. I am addressing this mostly to those familiar with Radiant internals. Others are welcome to contribute, of course. Is it technically possible to load Radiant extesions as gems, in a manner similar to the way Rails loads plugins from gems? There are several reasons for wanting this: 1. Versioning. Packaging extensions as gems lets us leverage the gem versioning mechanism. This way we would be able to state that Radiant version 0.8 is compatible with a certain extension version 1.2. 2. Management. You could have several versions of the same extension installed on your system, and various projects running different versions of Radiant would just use the one specified. No git submodules or vendoring of extensions needed. This ties into versioning. I would be willing to invest the time in making this happen. Is anyone else interested in seeing this? I anyone interested in helping out? Can anyone point me in a starting direction? Thanks! -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant on IIS possible?
In a similar situation, I have done the reverse: run Apache on port 80 and proxy requests to IIS running on another port. The IIS port is protected from ouside access by firewall. Rails applications were running on Mongrel with mod_balancer and managed with the mongrel_service gem to make the apps spin up on reboot. -- Istvan Hoka On Thu, Sep 10, 2009 at 7:04 PM, Sean Cribbs seancri...@gmail.com wrote: The easy answer for this is to use the typical reverse-proxy to mongrel, thin, or some other Ruby application server. Most web-servers have an option to do that. Sean Nate Turnage wrote: My company is putting together an RFQ for a website project for one of our clients. We only build Ruby on Rails applications, mostly with Radiant. One of the requirements for their website is that it be hosted on their Windows server with IIS. Is this possible? What options are available for hosting Rails sites on IIS? Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Caching problem with SNS extension?
Glad to help out. -- Istvan Hoka On Fri, Aug 14, 2009 at 1:28 PM, Gus Gollings gus.golli...@gmail.comwrote: All fixed here as well - thanks very much, Istvan. Regards, Gus On Fri, Aug 14, 2009 at 6:51 PM, Istvan Hokaistvan.h...@gmail.com wrote: On Wed, Aug 12, 2009 at 7:44 PM, Gus Gollings gus.golli...@gmail.com wrote: Clinton R. Nixon wrote: On Tue, Jul 28, 2009 at 12:18 PM, Jørn Schou-Rodejsr at malamute.dk wrote: I have a site running Radiant 0.8 with the head revision of the SNS extension from the radiant hub, and I am experiencing a problem with assets only being deliveried correctly to every second request. When I navigate directly to my main stylesheet[1] in my browser, I get the stylesheet or a completely blank screen (with Content-Length: 0 in the HTTP headers). Pressing F5 to redo the request, I get the opposite. Every second request gives my the stylesheet, every other a blank response. Does anyone know whats going on? How I done something wrong in my setup? I am having the same problem, but have not investigated it. If I find anything, I'll let you know. I have pushed an update that fixes this issue for me: http://github.com/Aissac/radiant-sns-extension/tree/master. -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Caching problem with SNS extension?
On Wed, Aug 12, 2009 at 7:44 PM, Gus Gollings gus.golli...@gmail.comwrote: Clinton R. Nixon wrote: On Tue, Jul 28, 2009 at 12:18 PM, Jørn Schou-Rodejsr at malamute.dk wrote: I have a site running Radiant 0.8 with the head revision of the SNS extension from the radiant hub, and I am experiencing a problem with assets only being deliveried correctly to every second request. When I navigate directly to my main stylesheet[1] in my browser, I get the stylesheet or a completely blank screen (with Content-Length: 0 in the HTTP headers). Pressing F5 to redo the request, I get the opposite. Every second request gives my the stylesheet, every other a blank response. Does anyone know whats going on? How I done something wrong in my setup? I am having the same problem, but have not investigated it. If I find anything, I'll let you know. I have pushed an update that fixes this issue for me: http://github.com/Aissac/radiant-sns-extension/tree/master. -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] mailer extension and 0.8
Could you try moving the contents of your config.after_initialize block to development.rb or production.rb? -- Istvan Hoka On Wed, Jul 8, 2009 at 8:47 PM, john muhl johnm...@gmail.com wrote: oh, and those results are the same with radiant/mailer or aissac/mailer On Wed, Jul 8, 2009 at 11:43 AM, john muhljohnm...@gmail.com wrote: this is running locally in the development environment. i've tested with webrick, mongrel, thin and passenger and they all have the same error message until you get to server specific part. the test site is the styled blog with only the mailer extension added. all the page parts and environment.rb are here: http://gist.github.com/142995 - i also have mailer.post_to_page? = true set. just to make sure it wasn't inherent in the system i setup a styled blog with 0.7.1 installed mailer, used the same parts and smtp settings and was able to send mail on all 4 servers. thanks for help. On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hokaistvan.h...@gmail.com wrote: John, it looks like you are getting this on your production machine where you are using Thin. Could you test with Passenger or Mongrel, perhaps locally and see if you get the same error? Also, could you provide some more context? For instance, are you trying to attach a file or is it a simple form you are mailing? Cheers! -- Istvan Hoka On Wed, Jul 8, 2009 at 7:34 PM, john muhl johnm...@gmail.com wrote: thanks but it gives the same error. On Wed, Jul 8, 2009 at 10:02 AM, Cristi Dumacristi.d...@aissac.ro wrote: Hi John, I'm playing with it right now, tried some fixes, features and stuff It works for me on a site I'm currently developing Check it out: http://github.com/Aissac/radiant-mailer-extension/tree/master On 7/8/09 6:05 PM, john muhl wrote: has anyone successfully used mailer on 0.8? whenever i try to send mail i get a 500 error page and the following: SQL (1.2ms)SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' SQL (1.9ms) SELECT DISTINCT class_name FROM pages WHERE class_name '' AND class_name IS NOT NULL /!\ FAILSAFE /!\ Wed Jul 08 09:01:58 -0600 2009 Status: 500 Internal Server Error wrong number of arguments (1 for 2) /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `restore_response' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `map' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in `call!' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rewindable_input.rb:25:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:93:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/reloader.rb:9:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/failsafe.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `synchronize' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:106:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/cgi_process.rb:44:in `dispatch_cgi' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:102:in `dispatch_cgi' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:28:in `dispatch' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:81:in `call' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:69:in `call' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:76:in `pre_process' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:74
Re: [Radiant] Anyone have SNS extension working correctly in 0.8.0
We have just updated the SNS extension to work with Radiant 0.8: http://github.com/Aissac/radiant-sns-extension/tree/master. Pull requests are sent out. Cheers! On Mon, Jun 29, 2009 at 10:09 AM, Michael Kessler mi...@netzpiraten.chwrote: Daniel, I haven't had the time to migrate the sns extension, because we're moving at the moment and it takes a lot of time and I have no Internet connection at the moment :( There is a migrated fork here: http://github.com/dko/radiant-sns-extension/tree/mastera but I haven't tried it. Michael On Jun 24, 2009, at 10:51 PM, Daniel O'Connell wrote: Does anyone have the sns extension working in 0.8.0? -Daniel ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] member-extension checking if user is logged in
This is a limitation due to the way Radiant works. Radiant is built to serve mostly static content so when it first renders a page, it caches it and serves it up to the next request without re-rendering it. To have the page behave differently for users depending on whether they are logged in or not, requires to render the page each time it is requested. A way to get the result you desire is to show another layout to your members, one that renders a log out link. For instance, say you have this site: /company/about /company/team /members /members/some-sensitive-page-requiring-login. You should require login for anything below /members and also, make anything below /members render a layout that is similar to your other pages, but instead of Log in it renders Log out. This works because if you are rendering anything below /members you know someone must be logged in. On Tue, Jun 2, 2009 at 5:51 PM, Christian Nikolajsen christ...@nikolajsen.net wrote: Hey people, I'm currently having a go at member extension ( http://blog.aissac.ro/radiant/member-extension/) and so far all is good. But what I would really like is for my login form to be replaced when a user logs in with fx. a logout button, but I can't find a way to tell my layouts to display the logout part instead of the login part after the user has logged in. Is there a way to check if the user is logged in? As far as I can tell there isn't a tag for it... which would be really neat. -- Venlig hilsen / Best Regards Christian Nikolajsen Cheers! -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Contact Form
On 3/28/09 11:45 AM, Benjamin Weber wrote: vendor/extensions# rake radiant:extensions:mailer:update --trace Consequence: rake aborted! Don't know how to build task 'radiant:extensions:mailer:update' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1704:in `[]' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2026:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1999:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1977:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1974:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 Do I understand something wrong? You need to run rake in your project root folder. It looks like you are in vendor/extensions. Just do a cd ../../ and run rake again. -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant Stereotype Extension
On 3/28/09 2:52 PM, Keith Bingman wrote: Have you tried this with a MySQL db yet? The find method gives an error... it seems the key, the name of the attribute is reserved in MySQL. Ptiy, it looks like a great extension, but it really needs to work with MySQL. Any help getting it running would be appreciated. There was an issue with quoting inside a query. Fixed and pushed to Github - should be working now. Thanks for the heads up! -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Radiant Custom Fields Extension
Announcing the Radiant Custom Fields extension! Features: * Provides the ability to add custom fields to a Page; * The Page model is not changed: custom_fields are added as a belongs_to association; * Admin interface for managing assigned custom fields; * Radius tags for accessing custom fields. Check out the announcement [http://blog.aissac.ro/2009/03/27/radiant-custom-fields-extension/], the official documentation page [http://blog.aissac.ro/radiant/custom-fields-extension/] and the code on github [http://github.com/Aissac/radiant-custom-fields-extension/]. Cheers! -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Radiant Stereotype Extension
Announcing the Radiant Stereotype Extension. Features: * Define named templates (stereotypes) for Pages; * Templates are assigned per-parent Page, making all children have the defined ’stereotype’ by their parent; * You can specify the new page’s parts, filters, layout and page type. Check out the announcement [http://blog.aissac.ro/2009/03/27/radiant-stereotype-extension/], the official extension page [http://blog.aissac.ro/radiant/stereotype-extension/] and the code on github [http://github.com/Aissac/radiant-stereotype-extension/]. Cheers! -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Page_attachment image title as attachment:link title
On 3/17/09 6:15 AM, N. Turnage wrote: Hey all, Trying to get the image title to render as the link title attribute but title=r:title / is rendering out as title=lt;r:title /gt; in the following snippet: notextile r:attachment:each limit=2 offset=1 order=asc div class=galleryThumb r:attachment:link rel=facebox-cap title=r:title / r:attachment:image size=gallery_thumb / /r:attachment:link /div /r:attachment:each /notextile Can anyone tell me why the less-than and greater than symbols are becoming html names instead of the tag being interpreted? You are getting this because Radius does not expand tags inside tag attributes. To get around this you could use the radiant-extensions extension (not a good name, I know) [http://github.com/Aissac/radiant-extensions-extension] which, among other things, hacks Radius to do what you need. Hope this helps. -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Member Extension
On 3/17/09 9:33 AM, J Aaron Farr wrote: On Tue 17 Mar 2009 00:13, Istvan Hokaistvan.h...@gmail.com wrote: Announcing the Radiant Member Extension. * Restricts access to Radiant pages under a certain node, requiring member login. * Members can be managed from Radiant Admin. There is *NO* member self-registration. * Reset and email member’s password from Admin interface; * Bulk import members from a CSV file; fields: name, company, email; * Radius tags for integrating login/logout functionality into the site; * Cookie-based flash messages. Intersting. Had you seen my earlier member's extension? http://github.com/farra/radiant-members-extension/tree/master It allows for member self-registration and provides a profile tab for managing your personal bio. I'm going to be doing an update to this and my conferences extension next week at ApacheCon. I did give your extension a try before rolling our own. Unfortunately it did not meet my need to restrict access to certain pages on the site based on membership. I will extend this to support member roles in a future release. Also, one of my clients required to import a list of members from XLS. -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Member Extension
On 3/17/09 11:24 AM, J Aaron Farr wrote: On Tue 17 Mar 2009 16:54, Istvan Hokaistvan.h...@gmail.com wrote: I did give your extension a try before rolling our own. Unfortunately it did not meet my need to restrict access to certain pages on the site based on membership. I will extend this to support member roles in a future release. Also, one of my clients required to import a list of members from XLS. You mean certain pages under the Pages tab? Correct, it doesn't do that. Though patches are welcome. Actually I meant the pages rendered on the public site. Site visitors can only access certain parts of the site only if they have an account. -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Tiny-Paper Extension
On 3/17/09 6:45 PM, Adam van den Hoven wrote: This looks great!! One question, it says that its 0.7.1 compatible but what about earlier versions, like 0.6.9? We have not tested it on earlier versions or Radiant. Any feedback is appreciated. -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Member Extension
Announcing the Radiant Member Extension. * Restricts access to Radiant pages under a certain node, requiring member login. * Members can be managed from Radiant Admin. There is *NO* member self-registration. * Reset and email member’s password from Admin interface; * Bulk import members from a CSV file; fields: name, company, email; * Radius tags for integrating login/logout functionality into the site; * Cookie-based flash messages. Check out the source code on github [http://github.com/Aissac/radiant-member-extension/tree/master]. For installation and configuration details visit the Radiant Member Extension documentation page [http://blog.aissac.ro/radiant/member-extensionmember-extension/]. -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: [ANN] Member Extension
On 3/16/09 6:13 PM, Istvan Hoka wrote: Announcing the Radiant Member Extension. * Restricts access to Radiant pages under a certain node, requiring member login. * Members can be managed from Radiant Admin. There is *NO* member self-registration. * Reset and email member’s password from Admin interface; * Bulk import members from a CSV file; fields: name, company, email; * Radius tags for integrating login/logout functionality into the site; * Cookie-based flash messages. Check out the source code on github [http://github.com/Aissac/radiant-member-extension/tree/master]. For installation and configuration details visit the Radiant Member Extension documentation page [http://blog.aissac.ro/radiant/member-extensionmember-extension/]. Sorry for the self-reply. Here's the correct link: http://blog.aissac.ro/radiant/member-extension/ -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Paperclipped Extension improvements
Hi everyone! We have made some changes to Paperclipped we thought you might like: * r:assets:each enhanced with limit, offset, order, by, extension filtering; * r:if_assets and r:unless_assets tags for conditional rendering; * r:assets:width and r:assets:height via imagesize gem; * better migration compatibility with PageAttachments extension when they have title and description fields (degrades gracefully). Fork is at: http://github.com/Aissac/paperclipped/tree/master. Pull requests have been sent out. Cheers! -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] Ultrasphinx Search Extension
Ultrasphinx Search Extension indexes page titles and page part contents. It provides a search results page type and tags to iterate over search results and display excerpts around matches. Check it out on github http://github.com/Aissac/radiant-ultrasphinx-search-extension or go to the documentation page for more details: http://blog.aissac.ro/radiant/ultrasphinx-search-extension/. Cheers! -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Localization
On 18.12.2008, at 19:31, Ole Rehmsen wrote: Hello, I am really interested in localization of radiant. I already checked the mailing list archive, but it seems as if this is not yet supported and there is no extension which offers support for this - is that true? If so how are the plans coming along for adding it to future releases? I would be willing help adding it myself, but I don't have much experience with it, so all I could do is turn to solutions such as Globalize! or Localization. I also heard something about Rails 2.2. having some kind a language support, but I have not tried it yet. Is there any intelligence on how this should be done? Do you guys maybe need some help or someone doing it? Is there anyone else who has tried/done it before (and how)? If you are interested in making sites with multi-lingual content, check out http://github.com/Aissac/radiant-globalize-extension. It basically lets you translate pages, snippets and layouts in various languages. It also allows for the translation of slugs so you get nice URLs in each language. The extension does not translate the administrative interface however. You need the Globalize Rails plugin with a minor patch to make it work: http://github.com/ihoka/globalize. The extension is in use in production on two sites so far: http://www.atp-exodus.ro , (Romanian, English, German) and http://euro5.ro (Romanian and English). The version on github is slightly outdated but I will push my local changes asap if anyone is interested. Cheers! -- Istvan Hoka ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
