Re: [Radiant] How can I create a fork of an extension at Github?
If you are logged in to github, you should see a button labelled fork when you visit the home page for a repository. Just hit that button, and github will create your own fork of the project in question. Once that's done, you can clone your fork of the repository onto your local machine: click the link labelled Your clone URL, and it will show you the code that you should run on your development machine. Do your work in your local git repository, and then run `git push` to publish your commits on github. Cheers, Drew On Tue, Sep 15, 2009 at 4:15 AM, Nate pixeln...@gmail.com wrote: It appears as if the subscriber_lists on github is incompatible with Radiant 0.8.x and I would like to take a shot at fixing it. However, I have never forked a project on github before. What is the process for creating my own branch of the extension? Do I create a local branch first, then push it to the repo on github? Or do I need to do the setup through github, then just clone (or add as a submodule) the repo in my main site? Any tips/hits/tricks that y'all could share would be greatly appreciated. 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
Re: [Radiant] Using Page_Attachments and Paperclipped Simultaneously?
Alexis Masters wrote: Hello! I've been trying without success to install these two extensions simultaneously. I would use only paperclipped if it were not for the gallery extension, which seems to need page_attachments to operate. Are any of you using either the gallery extension without page_attachments or using page_attachments, gallery, and paperclipped all on the same site? Alexis, You don't need page_attachments for Gallery - I have successfully got paperclipped and gallery working together. Based on my notes, I installed Gallery first and then paperclipped. Cheers, Mohit. 9/15/2009 | 6:56 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Passenger vs thin/mongrel/ebb
Hello, I've been using mongrel then thin for my small website, with two instances (I have a dual core machine) withlittle or no problem (except when I tried to run 0.8.0, more on this after I'll have tried 0.8.1). Now, I've been hearing about the so called mod_rails aka Passenger. Is there any advantage(s) in running that instead of my current setup? It is on my home machine running FreeBSD so I have no constraints in running whatever I want. BTW what did ahappen to Ebb? It does not sem alive... Thanks. -- Ollivier Robert - ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Passenger vs thin/mongrel/ebb
On Tue, Sep 15, 2009 at 10:01 AM, Ollivier Robert kel...@gmail.com wrote: Hello, I've been using mongrel then thin for my small website, with two instances (I have a dual core machine) withlittle or no problem (except when I tried to run 0.8.0, more on this after I'll have tried 0.8.1). Now, I've been hearing about the so called mod_rails aka Passenger. Is there any advantage(s) in running that instead of my current setup? It is on my home machine running FreeBSD so I have no constraints in running whatever I want. You should be fine with any of those. If you're not having a problem or aren't trying to avoid a potential problem, there's no reason to change your infrastructure. But Radiant runs fine on Passenger (mod_rails) BTW what did ahappen to Ebb? It does not sem alive... Thanks. -- Ollivier Robert - -- Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Passenger vs thin/mongrel/ebb
Passenger does work well with Radiant, but in some instances you might need to chown or chgrp certain directories to the DefaultPassengerUser that you've specified in your respective config file (Apache or nginx). Some places I've had to do this recently (assuming radiant mysite) (...)/mysite (...)/mysite/tmp -r (...)/mysite/environment.rb (...)/mysite/public/assets (for paperclipped) (...)/mysite/public/galleries (for gallery) I don't quite know why these directories aren't created with the correct permissions in the first place, but it's a little gotcha that could save you a lot of time. Charlie On Tue, Sep 15, 2009 at 10:24 AM, Jim Gay j...@saturnflyer.com wrote: On Tue, Sep 15, 2009 at 10:01 AM, Ollivier Robert kel...@gmail.com wrote: Hello, I've been using mongrel then thin for my small website, with two instances (I have a dual core machine) withlittle or no problem (except when I tried to run 0.8.0, more on this after I'll have tried 0.8.1). Now, I've been hearing about the so called mod_rails aka Passenger. Is there any advantage(s) in running that instead of my current setup? It is on my home machine running FreeBSD so I have no constraints in running whatever I want. You should be fine with any of those. If you're not having a problem or aren't trying to avoid a potential problem, there's no reason to change your infrastructure. But Radiant runs fine on Passenger (mod_rails) BTW what did ahappen to Ebb? It does not sem alive... Thanks. -- Ollivier Robert - -- Jim Gay http://www.saturnflyer.com ___ 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] Passenger vs thin/mongrel/ebb
I was running Gallery. Don't really need it anymore. Really wish someone could just introduce the concept of a Gallery (or Group of assets) to Paperclipped. Having two separate extensions managing my assets seems redundant to me. Charlie On Tue, Sep 15, 2009 at 11:25 AM, Nate Turnage pixeln...@gmail.com wrote: On Tue, Sep 15, 2009 at 10:20 AM, Charlie Robbins charlie.robb...@gmail.com wrote: (...)/mysite (...)/mysite/tmp -r (...)/mysite/environment.rb (...)/mysite/public/assets (for paperclipped) (...)/mysite/public/galleries (for gallery) So you are running the gallery extension with paperclipped, then? ~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
Re: [Radiant] Passenger vs thin/mongrel/ebb
As far as paperclipped doing a group of assets it's pretty much there. You can attach images to a page and then using r:assets:each / display all those images. Steven On Sep 15, 2009, at 10:28 AM, Charlie Robbins wrote: I was running Gallery. Don't really need it anymore. Really wish someone could just introduce the concept of a Gallery (or Group of assets) to Paperclipped. Having two separate extensions managing my assets seems redundant to me. Charlie On Tue, Sep 15, 2009 at 11:25 AM, Nate Turnage pixeln...@gmail.com wrote: On Tue, Sep 15, 2009 at 10:20 AM, Charlie Robbins charlie.robb...@gmail.com wrote: (...)/mysite (...)/mysite/tmp -r (...)/mysite/environment.rb (...)/mysite/public/assets (for paperclipped) (...)/mysite/public/galleries (for gallery) So you are running the gallery extension with paperclipped, then? ~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
[Radiant] Per-request caching?
Anyone have any pointers toward the best way of implementing per-request caching in Radiant 0.8.x? The basic idea is that we're writing a bunch of extensions to handle a membership database, user login, etc. - logged-in users may have different options appear, will have their name in a corner of the page, etc, whereas anonymous users will all see the same page content. I'm thinking it should be adequate to simply check the session or their cookie to see if they're logged in, and if so bypass the cache - otherwise normal Radiant cache behavior can apply. I took a look into this briefly a while back, but wasn't quite sure what the right way to go about this was - any thoughts would be appreciated. Rufo ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Per-request caching?
Rufo, The key is adding the correct caching-related headers that will be detected by Rack::Cache. You can do this automatically in your controllers using expires_in, expires_now, and the like. I suggest checking out the ActionController API for more details. Sean Rufo Sanchez wrote: Anyone have any pointers toward the best way of implementing per-request caching in Radiant 0.8.x? The basic idea is that we're writing a bunch of extensions to handle a membership database, user login, etc. - logged-in users may have different options appear, will have their name in a corner of the page, etc, whereas anonymous users will all see the same page content. I'm thinking it should be adequate to simply check the session or their cookie to see if they're logged in, and if so bypass the cache - otherwise normal Radiant cache behavior can apply. I took a look into this briefly a while back, but wasn't quite sure what the right way to go about this was - any thoughts would be appreciated. Rufo ___ 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] Re: Radiant Digest, Vol 42, Issue 18
Thanks, Mohit. That vote of confidence is just what I needed to hear. Smiles, ~ Alexis On Sep 15, 2009, at 7:24 AM, radiant-requ...@radiantcms.org wrote: Message: 8 Date: Tue, 15 Sep 2009 19:15:31 +0800 From: Mohit Sindhwani t...@onghu.com Subject: Re: [Radiant] Using Page_Attachments and Paperclipped Simultaneously? To: radiant@radiantcms.org Message-ID: 4aaf7753.6020...@onghu.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Alexis Masters wrote: Hello! I've been trying without success to install these two extensions simultaneously. I would use only paperclipped if it were not for the gallery extension, which seems to need page_attachments to operate. Are any of you using either the gallery extension without page_attachments or using page_attachments, gallery, and paperclipped all on the same site? Alexis, You don't need page_attachments for Gallery - I have successfully got paperclipped and gallery working together. Based on my notes, I installed Gallery first and then paperclipped. Cheers, Mohit. 9/15/2009 | 6:56 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Blade Interface merged into edge
Radiant users, John Long and I just merged the blade branch into the master branch. This includes a large number of changes to the user interface and some fundamental API changes (especially related to the navigation tabs). The work is by no means done on the interface, but now you can start using it if your project is on edge. We look forward to your input! Cheers, Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Per-request caching?
Gah - I *knew* I was leaving something out of my explanation. :-) The main point is that there are Radius tags that will display certain information on *all* pages on the system that shouldn't be cached when logged in - the caching isn't limited to just our extension's controllers, I can handle that part. Would an acceptable method to add this to Radiant-handled Pages be to override the set_cache_control filter in the SiteController via an extension, or is there a cleaner way of handling this? Rufo On Tue, Sep 15, 2009 at 12:22 PM, Sean Cribbs seancri...@gmail.com wrote: Rufo, The key is adding the correct caching-related headers that will be detected by Rack::Cache. You can do this automatically in your controllers using expires_in, expires_now, and the like. I suggest checking out the ActionController API for more details. Sean Rufo Sanchez wrote: Anyone have any pointers toward the best way of implementing per-request caching in Radiant 0.8.x? The basic idea is that we're writing a bunch of extensions to handle a membership database, user login, etc. - logged-in users may have different options appear, will have their name in a corner of the page, etc, whereas anonymous users will all see the same page content. I'm thinking it should be adequate to simply check the session or their cookie to see if they're logged in, and if so bypass the cache - otherwise normal Radiant cache behavior can apply. I took a look into this briefly a while back, but wasn't quite sure what the right way to go about this was - any thoughts would be appreciated. Rufo ___ 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] Blade Interface merged into edge
For those of you who are developing extensions for Radiant, please update them to work with the new interface and give us your feedback on what your like and dislike. The most significant changes in the UI have been made to help extension developers keep things organized. --John On Sep 15, 2009, at 12:45 PM, Sean Cribbs wrote: Radiant users, John Long and I just merged the blade branch into the master branch. This includes a large number of changes to the user interface and some fundamental API changes (especially related to the navigation tabs). The work is by no means done on the interface, but now you can start using it if your project is on edge. We look forward to your input! Cheers, Sean ___ 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] Per-request caching?
Radiant::Cache doesn't discriminate between users who are logged in or not. IMO it would be best to either: 1) Turn off all caching by removing the Radiant::Cache middleware. 2) Load your user-specific stuff into the page using Ajax, allowing the caching to still occur. Sean Rufo Sanchez wrote: Gah - I *knew* I was leaving something out of my explanation. :-) The main point is that there are Radius tags that will display certain information on *all* pages on the system that shouldn't be cached when logged in - the caching isn't limited to just our extension's controllers, I can handle that part. Would an acceptable method to add this to Radiant-handled Pages be to override the set_cache_control filter in the SiteController via an extension, or is there a cleaner way of handling this? Rufo On Tue, Sep 15, 2009 at 12:22 PM, Sean Cribbs seancri...@gmail.com wrote: Rufo, The key is adding the correct caching-related headers that will be detected by Rack::Cache. You can do this automatically in your controllers using expires_in, expires_now, and the like. I suggest checking out the ActionController API for more details. Sean Rufo Sanchez wrote: Anyone have any pointers toward the best way of implementing per-request caching in Radiant 0.8.x? The basic idea is that we're writing a bunch of extensions to handle a membership database, user login, etc. - logged-in users may have different options appear, will have their name in a corner of the page, etc, whereas anonymous users will all see the same page content. I'm thinking it should be adequate to simply check the session or their cookie to see if they're logged in, and if so bypass the cache - otherwise normal Radiant cache behavior can apply. I took a look into this briefly a while back, but wasn't quite sure what the right way to go about this was - any thoughts would be appreciated. Rufo ___ 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] Re: Radiant Digest, Vol 42, Issue 18
Alexis Masters wrote: Thanks, Mohit. That vote of confidence is just what I needed to hear. Smiles, ~ Alexis Cheers! Ping me if you have any trouble. Cheers, Mohit. 9/16/2009 | 1:29 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Per-request caching?
one option is what we did on member extensionhttp://github.com/Aissac/radiant-member-extension/blob/master/lib/site_controller_member_extensions.rb. You need to add a filter to the site_controller that tells it to not cache specific pages (in our case the pages that need member registration). This probably doesn't solve your problem but could be a place to start :) On Tue, Sep 15, 2009 at 8:19 PM, Sean Cribbs seancri...@gmail.com wrote: Radiant::Cache doesn't discriminate between users who are logged in or not. IMO it would be best to either: 1) Turn off all caching by removing the Radiant::Cache middleware. 2) Load your user-specific stuff into the page using Ajax, allowing the caching to still occur. Sean Rufo Sanchez wrote: Gah - I *knew* I was leaving something out of my explanation. :-) The main point is that there are Radius tags that will display certain information on *all* pages on the system that shouldn't be cached when logged in - the caching isn't limited to just our extension's controllers, I can handle that part. Would an acceptable method to add this to Radiant-handled Pages be to override the set_cache_control filter in the SiteController via an extension, or is there a cleaner way of handling this? Rufo On Tue, Sep 15, 2009 at 12:22 PM, Sean Cribbs seancri...@gmail.com wrote: Rufo, The key is adding the correct caching-related headers that will be detected by Rack::Cache. You can do this automatically in your controllers using expires_in, expires_now, and the like. I suggest checking out the ActionController API for more details. Sean Rufo Sanchez wrote: Anyone have any pointers toward the best way of implementing per-request caching in Radiant 0.8.x? The basic idea is that we're writing a bunch of extensions to handle a membership database, user login, etc. - logged-in users may have different options appear, will have their name in a corner of the page, etc, whereas anonymous users will all see the same page content. I'm thinking it should be adequate to simply check the session or their cookie to see if they're logged in, and if so bypass the cache - otherwise normal Radiant cache behavior can apply. I took a look into this briefly a while back, but wasn't quite sure what the right way to go about this was - any thoughts would be appreciated. Rufo ___ 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
Re: [Radiant] Small obstacle for a newby installing settings and paperclipped extentions
Mohit Sindhwani schreef: Eric de Hont wrote: Hi all, Being a newbie to Radiant I have encountered -and gloatsolved/gloat- a little problem. I'll describe the problem and the solution so other people might learn from the mistakes I made. Perhaps a more experienced person can give some background information. Environment: Radiant CMS version 0.8.1. Problem: installing the extentions 'settings' and 'paperclipped' fails with sqlite3-errors. Still the extentions get a status 'installed' and after that, every work you try to do as admin leads to internal server errors. (500) Solution: Making the 'production' and 'development' database equal in config/database.yml, uninstalling the extentions and installing them again. [snip] Hi Eric, There are a couple of things to keep in mind when working with Radiant, Thanks for enlightening these points. Eric ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Radiant Phusion Passenger Issue
Hi all, I installed Radiant 0.8.1 on Apache using Passenger on my Ubuntu linux system. I did not install it on the DocumentRoot but at /blog/ (RailsBaseURI /blog Directive) What I notice is that in the admin, I cannot expand the Children pages of Articles, I get an error: The requested URL /admin/pages/4/children was not found on this server. It seems that it should be looking for /blog/admin/pages/4/children. When I start the server on the command line with script/server everything works fine. Any help appreciated. 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] Radiant Phusion Passenger Issue
On Sep 15, 2009, at 2:28 PM, Thembile wrote: Hi all, I installed Radiant 0.8.1 on Apache using Passenger on my Ubuntu linux system. I did not install it on the DocumentRoot but at /blog/ (RailsBaseURI /blog Directive) What I notice is that in the admin, I cannot expand the Children pages of Articles, I get an error: The requested URL /admin/pages/4/children was not found on this server. It seems that it should be looking for /blog/admin/pages/4/children. When I start the server on the command line with script/server everything works fine. Any help appreciated. Thanks. http://github.com/radiant/radiant/issues/closed#issue/10 Static javascript files are used to expand the children and they have no knowledge of your alternate URL. Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Blade Interface merged into edge
On Tue, Sep 15, 2009 at 11:10 AM, John W. Long m...@johnwlong.com wrote: For those of you who are developing extensions for Radiant, please update them to work with the new interface and give us your feedback on what your like and dislike. The most significant changes in the UI have been made to help extension developers keep things organized. i sent a bunch of feedback to the list sometime ago about the blade ui but it was never responded to. should i bother re-sending that? or was the lack of response the response? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Blade Interface merged into edge
On Sep 15, 2009, at 3:47 PM, john muhl wrote: On Tue, Sep 15, 2009 at 11:10 AM, John W. Long m...@johnwlong.com wrote: For those of you who are developing extensions for Radiant, please update them to work with the new interface and give us your feedback on what your like and dislike. The most significant changes in the UI have been made to help extension developers keep things organized. i sent a bunch of feedback to the list sometime ago about the blade ui but it was never responded to. should i bother re-sending that? or was the lack of response the response? I've actually been meaning to respond. I agreed with much of it, but haven't had the time to really look at it and write back. Also, I've been uninvolved with the push to include the Blade UI, so I thought John Long might be better suited to respond. Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Blade Interface merged into edge
On Sep 15, 2009, at 3:47 PM, john muhl wrote: i sent a bunch of feedback to the list sometime ago about the blade ui but it was never responded to. should i bother re-sending that? or was the lack of response the response? I must have missed that somehow. Please repost it. -- John Long http://wiseheartdesign.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Blade Interface merged into edge
On Tue, Sep 15, 2009 at 3:15 PM, John W. Long m...@johnwlong.com wrote: On Sep 15, 2009, at 3:47 PM, john muhl wrote: i sent a bunch of feedback to the list sometime ago about the blade ui but it was never responded to. should i bother re-sending that? or was the lack of response the response? I must have missed that somehow. Please repost it. http://groups.google.com/group/radiantcms-dev/browse_thread/thread/dc9b43114574cc40 ___ 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 Phusion Passenger Issue
Thanks! On Tue, Sep 15, 2009 at 11:59 AM, Jim Gay j...@saturnflyer.com wrote: On Sep 15, 2009, at 2:28 PM, Thembile wrote: Hi all, I installed Radiant 0.8.1 on Apache using Passenger on my Ubuntu linux system. I did not install it on the DocumentRoot but at /blog/ (RailsBaseURI /blog Directive) What I notice is that in the admin, I cannot expand the Children pages of Articles, I get an error: The requested URL /admin/pages/4/children was not found on this server. It seems that it should be looking for /blog/admin/pages/4/children. When I start the server on the command line with script/server everything works fine. Any help appreciated. Thanks. http://github.com/radiant/radiant/issues/closed#issue/10 Static javascript files are used to expand the children and they have no knowledge of your alternate URL. Jim Gay http://www.saturnflyer.com ___ 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] Small obstacle for a newby installing settings and paperclipped extentions
Eric de Hont wrote: [snip] Hi Eric, There are a couple of things to keep in mind when working with Radiant, Thanks for enlightening these points. You're most welcome :) Welcome to Radiant Cheers, Mohit. 9/16/2009 | 9:45 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
