Re: [Radiant] Radiant performance
Hi Stefan, wonderful hint, I found that both the NavigationTags and the Feedreader extensions were wasting time. After optimization, rendering time went down from 2500-3000ms to 200-600ms per page. Not too bad... Regards, Christian Am 04.01.2010 um 10:19 schrieb qutic development: You might check out Rack::Bug to get an idea why the rendering time is that high: http://github.com/brynary/rack-bug Best regards Stefan ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] ldap login and forum
Rob Levin wrote: Basic use case: User logs in -- ldap verified -- Rails/Radiant Auth (restful_authentication or similar) -- user goes to a Forum (without having to log in again) First, is there an extensions that I could hook in to that wraps something like restful_auth? (member extension won't work because admin must create user) I could probably just utilize the ruby-net-ldap stuff myself provided I could hook in to something like this. Second, if I use beastly, provided user has been authenticated (via whatever is the answer to my first question), will beastly/altered beast recognize that user (achieving single sign on)? Feedback/thoughts? If not, I'll probably have to supplant and use our already existing python/django ldap code, use a django forum, tweak Apache virtual hosts -- you catch my drift? Thanks all ;-) PS Basic forum requirements: 1. Data Migration: How do they store the data? DB not flat files? MySQL? 2. User Management: Single login via LDAP - whatever (Rails session,etc.) 3. Subscriptions RSS Integration 4. Easy to skin (CSS, etc.) 5. Attachments I'd love to hear what you come up with, but for what it's worth, I'm using Simple Machines Forum on my site alongside a Radiant install. There's currently no integration between the Radiant site (www.t-engine.info) and the SMF Forum (bbs.t-engine.info) - it meets most of your requirements, but unsure about #2 cos I haven't really checked. However, SMF claims to be good and easy to integrate against (it's PHP, mind you) - it also apparently does expose its authentication API but I haven't tried. I do hope that you'll share what you settle on. Cheers, Mohit. 1/5/2010 | 11:45 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] ldap login and forum
We have a client that uses Sun's Java Access Manager (now OpenSSO) to authenticate against LDAP and we built this to work with it: http://github.com/saturnflyer/radiant-header_authorize-extension And in our altered_beast implementation, we use http://github.com/saturnflyer/java_access_manager_plugin but we did modify the source of altered_beast to look to another location for users. You could probably use a plugin to modify the objects instead, but hacking the source was the simplest option at the time. The access manager sends authentication details to Apache and we have 4 rails apps and 1 php wiki sitting behind it all. If you use something like OpenSSO, you can use whatever apps you want and just override their authentication scheme to gather info from the headers. Jim Gay http://www.saturnflyer.com On Jan 5, 2010, at 10:33 AM, Rob Levin wrote: Basic use case: User logs in -- ldap verified -- Rails/Radiant Auth (restful_authentication or similar) -- user goes to a Forum (without having to log in again) First, is there an extensions that I could hook in to that wraps something like restful_auth? (member extension won't work because admin must create user) I could probably just utilize the ruby-net-ldap stuff myself provided I could hook in to something like this. Second, if I use beastly, provided user has been authenticated (via whatever is the answer to my first question), will beastly/altered beast recognize that user (achieving single sign on)? Feedback/thoughts? If not, I'll probably have to supplant and use our already existing python/django ldap code, use a django forum, tweak Apache virtual hosts -- you catch my drift? Thanks all ;-) PS Basic forum requirements: 1. Data Migration: How do they store the data? DB not flat files? MySQL? 2. User Management: Single login via LDAP - whatever (Rails session,etc.) 3. Subscriptions RSS Integration 4. Easy to skin (CSS, etc.) 5. Attachments ___ 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] Sharing radiant layouts with another Rails _application_ (not controller)
Hi, I know I can use a plugin to let a controller independant of Radiant to use Radiant's layout. But what if I have 2 applications - one with custom functionality, one as the Radiant CMS - serving the same 'site' on different paths, how I can I share as much of the layout as possible without having to copy/paste? Thanks ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] next 15
Steven, You should be able to add an offset attribute to the r:children:each tag. But yes, you'll likely need to create another page, or a virtual page that can deal with pagination of those aggregated children. Sean On 1/5/10 3:41 PM, Steven Southard wrote: When using a tag liker:aggregate urls=/articles/; / other_articles/;r:children:each limit=15 order=desc is there a way to ask for the next 15? Do I need to make another archive page to link to for that? Steven ___ 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] next 15
Okay great, very smart. Maybe just use parameters in the url to determine the offset? On Jan 5, 2010, at 2:53 PM, Sean Cribbs wrote: Steven, You should be able to add an offset attribute to the r:children:each tag. But yes, you'll likely need to create another page, or a virtual page that can deal with pagination of those aggregated children. Sean On 1/5/10 3:41 PM, Steven Southard wrote: When using a tag liker:aggregate urls=/articles/; / other_articles/;r:children:each limit=15 order=desc is there a way to ask for the next 15? Do I need to make another archive page to link to for that? Steven ___ 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] next 15
i've never used it personally (though i've had good results with other extensions from aissac) but you might try the paginate extension: http://github.com/Aissac/radiant-paginate-extension On Tue, Jan 5, 2010 at 2:59 PM, Steven Southard ste...@stevensouthard.com wrote: Okay great, very smart. Maybe just use parameters in the url to determine the offset? On Jan 5, 2010, at 2:53 PM, Sean Cribbs wrote: Steven, You should be able to add an offset attribute to the r:children:each tag. But yes, you'll likely need to create another page, or a virtual page that can deal with pagination of those aggregated children. Sean On 1/5/10 3:41 PM, Steven Southard wrote: When using a tag liker:aggregate urls=/articles/; / other_articles/;r:children:each limit=15 order=desc is there a way to ask for the next 15? Do I need to make another archive page to link to for that? Steven ___ 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 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] next 15
I've never understood the purpose of that extension, that's what it does? The offset with parameters was easy and didn't require any additional pages or anything. Thank you both for your help. Steven On Jan 5, 2010, at 3:07 PM, john muhl wrote: i've never used it personally (though i've had good results with other extensions from aissac) but you might try the paginate extension: http://github.com/Aissac/radiant-paginate-extension On Tue, Jan 5, 2010 at 2:59 PM, Steven Southard ste...@stevensouthard.com wrote: Okay great, very smart. Maybe just use parameters in the url to determine the offset? On Jan 5, 2010, at 2:53 PM, Sean Cribbs wrote: Steven, You should be able to add an offset attribute to the r:children:each tag. But yes, you'll likely need to create another page, or a virtual page that can deal with pagination of those aggregated children. Sean On 1/5/10 3:41 PM, Steven Southard wrote: When using a tag liker:aggregate urls=/articles/; / other_articles/;r:children:each limit=15 order=desc is there a way to ask for the next 15? Do I need to make another archive page to link to for that? Steven ___ 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 ___ 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] Display logged-in username using radius tags
Hi, I need to show the username for logged-in user on webpage. For that i need to read user session. So what is the *Radius tag* using which i can display logged-in username ? If no what is the possible way to do this ? Thanks in Advance. -- Thank you. Regards, Ninad ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Thinking Sphinx
Hi, I've recently upgraded to the 1.3.14 gem version of Thinking Sphinx and I know get this error when both running a search and running rake ts:index You have a nil object when you didn't expect it! You might have expected an instance of Array. The error occurred while evaluating nil. I've managed to pinpoint the problem to the define_index method in the SphinxSearch PageExtensions module. As soon as I remove this method all works fine. I'm not certain what the exact problem is in this method though. If anyone can quickly enlighten me it would be much appreciated. Thanks John ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] 1
testing testing :3 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 1
Sean Lum wrote: testing testing :3 successful, I guess.. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Thinking Sphinx
Hi John, I've run into that issue, too. It's currently being discussed on the thinking-sphinx GoogleGroup http://groups.google.com/group/thinking-sphinx/browse_thread/thread/4ce0b8ebd94cfcb9?fwc=1 Removing the define_index method basically means disabling the indexing part of the extension, since define_index tells thinking-sphinx what parts of your AR model should go into the sphinx configuration. Since you already had a working configuration and index, it may very well be that the rest of the search actually works. Maybe you have a chance to head over to googlegroups and leave a quick me too to show your interest in that issue. Regards, Christian Am 06.01.2010 um 07:46 schrieb John Polling: Hi, I've recently upgraded to the 1.3.14 gem version of Thinking Sphinx and I know get this error when both running a search and running rake ts:index You have a nil object when you didn't expect it! You might have expected an instance of Array. The error occurred while evaluating nil. I've managed to pinpoint the problem to the define_index method in the SphinxSearch PageExtensions module. As soon as I remove this method all works fine. I'm not certain what the exact problem is in this method though. If anyone can quickly enlighten me it would be much appreciated. Thanks John ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
