Re: [Radiant] Configuring the admin panel
'https' is always configured in apache (or nginx, etc). To make radiant work with ssl you can use this extension: http://github.com/jfqd/radiant-ssl_requirement-extension On 24.01.2010, at 22:11, Paul Fox wrote: I need the admin console to be accessible from anywhere via https on port 443 (to protect passwords). Is this something configured in the apache passenger module, or in radiant? How do I configure this? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] Virtual children pf pages
Hi all, A client needs kind of a directory website, like an employee directory, with pages for each employee. I'd like to propose a solution using Radiant. However, due to the amount of employees and the repetetive structure of those pages, it would be uncomfortable and hard to handle to create an individual page for each of them. The final directory URL structure should look like this: website root - employees - emp1 - Documents - Photos - emp2 - Documents - Photos - [employee n] - Documents - Photos Pages in Radiant would be: - employees (Type: Employee archive) - Documents for %1 (Type: Normal page) - Photos for %1 (Type: Normal page) I was wondering if the employees would be some kind of an archive extension, getting the list of employees from the database. A request for /employees/emp1/ would be handled by the archive, selecting the data for emp1 and getting the layout from the content of employees, effectively producing emp1's personal page. A request for /employees/emp1/documents/ would be handled by the archive, too, checking if there's a page below with a slug documents and getting it's content from there. I've done some RoR stuff but I'm rather new to Radiant (although I've dug through the code) It'd be most appreciated if you could spare some time to help me with these questions: (1) Is there something like this already? Are you aware of anything that's similar so I could start from something? (2) How would I make my list of employees behave like pages (and play nicely with the sitemap extension and others) - without them showing up on the pages tab? (3) What's best practice to expand variables in a document title (like Documents for %1 which should become Documents for John Doe) I'd love to use Radiant for this, so any help is welcome. Regards, Christian ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Configuring the admin panel
That extension looks like what I need, but I still have some questions. Can I merely point apache to the public folder as webroot for the 443 vhost and configure ssl for the vhost? Is there any configuration I need to do in radiant to change the port for the admin console, since the docs suggest it defaults to 3000? I don't have write access to the apache config, and the admin doesn't know anything about rails, so I really need to be able to hand him a working config the first time around. Thank you for your help. On Mon, Jan 25, 2010 at 3:36 AM, qutic development mailingli...@qutic.comwrote: 'https' is always configured in apache (or nginx, etc). To make radiant work with ssl you can use this extension: http://github.com/jfqd/radiant-ssl_requirement-extension On 24.01.2010, at 22:11, Paul Fox wrote: I need the admin console to be accessible from anywhere via https on port 443 (to protect passwords). Is this something configured in the apache passenger module, or in radiant? How do I configure this? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] Problem with Settings extension
Hi all,
I've got a problem with the setting extension. It seems to have installed
fine. I can click on the settings tab, but whenever I go to edit a setting I
get an error 500. This is the error from the log:
Processing Admin::SettingsController#edit (for 81.99.59.16 at 2010-01-25
16:55:43) [GET]
Parameters: {action=edit, id=2, controller=admin/settings}
Rendering template within layouts/application
Rendering admin/settings/edit
ActionView::TemplateError (undefined method `description' for
#Radiant::Config:0xb6eafb94) on line #21 of
vendor/extensions/settings/app/views/admin/settings/edit.html.haml:
18:
19: %h2.setting-name= @setting.key
20:
21: .description= textilize @setting.description
22:
23: - form_for :setting, :url = admin_setting_path(@setting), :html = {
:method = :put } do |f|
24: .form-area
vendor/extensions/settings/app/views/admin/settings/edit.html.haml:21:in
`_run_haml_vendor47extensions47settings47app47views47admin47settings47edit46html46haml'
radiant (0.8.1)
vendor/plugins/haml/rails/./lib/haml/helpers/action_view_mods.rb:14:in
`render'
radiant (0.8.1)
vendor/plugins/haml/rails/./lib/haml/helpers/action_view_mods.rb:14:in
`render'
radiant (0.8.1)
vendor/plugins/haml/rails/./lib/sass/plugin/rails.rb:19:in `process'
passenger (2.2.9) lib/phusion_passenger/rack/request_handler.rb:92:in
`process_request'
passenger (2.2.9)
lib/phusion_passenger/abstract_request_handler.rb:207:in `main_loop'
passenger (2.2.9)
lib/phusion_passenger/railz/application_spawner.rb:400:in
`start_request_handler'
passenger (2.2.9)
lib/phusion_passenger/railz/application_spawner.rb:351:in
`handle_spawn_application'
passenger (2.2.9) lib/phusion_passenger/utils.rb:184:in `safe_fork'
passenger (2.2.9)
lib/phusion_passenger/railz/application_spawner.rb:349:in
`handle_spawn_application'
passenger (2.2.9) lib/phusion_passenger/abstract_server.rb:352:in
`__send__'
passenger (2.2.9) lib/phusion_passenger/abstract_server.rb:352:in
`main_loop'
passenger (2.2.9) lib/phusion_passenger/abstract_server.rb:196:in
`start_synchronously'
passenger (2.2.9) lib/phusion_passenger/abstract_server.rb:163:in
`start'
passenger (2.2.9)
lib/phusion_passenger/railz/application_spawner.rb:209:in `start'
passenger (2.2.9) lib/phusion_passenger/spawn_manager.rb:262:in
`spawn_rails_application'
passenger (2.2.9)
lib/phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add'
passenger (2.2.9) lib/phusion_passenger/spawn_manager.rb:256:in
`spawn_rails_application'
passenger (2.2.9)
lib/phusion_passenger/abstract_server_collection.rb:80:in `synchronize'
passenger (2.2.9)
lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
passenger (2.2.9) lib/phusion_passenger/spawn_manager.rb:255:in
`spawn_rails_application'
passenger (2.2.9) lib/phusion_passenger/spawn_manager.rb:154:in
`spawn_application'
passenger (2.2.9) lib/phusion_passenger/spawn_manager.rb:287:in
`handle_spawn_application'
passenger (2.2.9) lib/phusion_passenger/abstract_server.rb:352:in
`__send__'
passenger (2.2.9) lib/phusion_passenger/abstract_server.rb:352:in
`main_loop'
passenger (2.2.9) lib/phusion_passenger/abstract_server.rb:196:in
`start_synchronously'
Rendering /home/reclaim/radiant/public/500.html (500 Internal Server Error)
If anyone could help I'd much appreciate it.
James
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org
Re: [Radiant] Problem with Settings extension
On 25.01.2010, at 18:00, James Maskell wrote: ActionView::TemplateError (undefined method `description' for #Radiant::Config:0xb6eafb94) on line #21 of vendor/extensions/settings/app/views/admin/settings/edit.html.haml: 18: Did you run the migration for the settings extension? You miss a column in the config table named 'description' cu edi -- DI Edmund Haselwanter, edm...@haselwanter.com, http://edmund.haselwanter.com/ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Problem with Settings extension
Thanks - solved the problem. I had assumed ray would have made the necessary migrations when I installed the extension. 2010/1/25 banane ban...@gmail.com Hasselwanter is right, in your Radiant root run rake radiant:extensions:settings:migrate RAILS_ENV=[your environment dev, test, prod, etc.] On Mon, Jan 25, 2010 at 9:07 AM, Haselwanter Edmund edm...@haselwanter.com wrote: On 25.01.2010, at 18:00, James Maskell wrote: ActionView::TemplateError (undefined method `description' for #Radiant::Config:0xb6eafb94) on line #21 of vendor/extensions/settings/app/views/admin/settings/edit.html.haml: 18: Did you run the migration for the settings extension? You miss a column in the config table named 'description' cu edi -- DI Edmund Haselwanter, edm...@haselwanter.com, http://edmund.haselwanter.com/ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
[Radiant] trouble packaging extension as gem
i hope someone can point out what stupid thing i've done in my first attempt to package an extension as a gem. http://gist.github.com/286072 the extension works fine as a regular extension. i'm trying this on the edge (current as of about an hour ago). ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Problem with Settings extension
On Mon, Jan 25, 2010 at 11:17 AM, James Maskell ja...@jamesmaskell.co.uk wrote: Thanks - solved the problem. I had assumed ray would have made the necessary migrations when I installed the extension. ray should have; and does as far as i can tell. rake ray:i name=settings ... rake -q RAILS_ENV=development radiant:extensions:settings:migrate ... rake -q RAILS_ENV=development radiant:extensions:settings:update ... 2010/1/25 banane ban...@gmail.com Hasselwanter is right, in your Radiant root run rake radiant:extensions:settings:migrate RAILS_ENV=[your environment dev, test, prod, etc.] On Mon, Jan 25, 2010 at 9:07 AM, Haselwanter Edmund edm...@haselwanter.com wrote: On 25.01.2010, at 18:00, James Maskell wrote: ActionView::TemplateError (undefined method `description' for #Radiant::Config:0xb6eafb94) on line #21 of vendor/extensions/settings/app/views/admin/settings/edit.html.haml: 18: Did you run the migration for the settings extension? You miss a column in the config table named 'description' cu edi -- DI Edmund Haselwanter, edm...@haselwanter.com, http://edmund.haselwanter.com/ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] trouble packaging extension as gem
On Jan 25, 2010, at 1:08 PM, john muhl wrote: i hope someone can point out what stupid thing i've done in my first attempt to package an extension as a gem. http://gist.github.com/286072 the extension works fine as a regular extension. i'm trying this on the edge (current as of about an hour ago). It's probably a load order problem. Radiant adds the method to_name to String and perhaps it doesn't exist when KramdownFilter is loaded. http://github.com/radiant/radiant/blob/master/lib/plugins/string_extensions/lib/string_extensions.rb#L10-L12 Perhaps you can require that file in the extension, or maybe Radiant needs to address this by changing the load order ( since extensions as gems is the future). -Jim Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] trouble packaging extension as gem
Actually, I imagine :lib = false would do the trick -- gem requirements are loaded before extensions. As long as your extension file explicitly loads that text filter, you should be fine. Sean On 1/25/10 1:51 PM, Jim Gay wrote: On Jan 25, 2010, at 1:08 PM, john muhl wrote: i hope someone can point out what stupid thing i've done in my first attempt to package an extension as a gem. http://gist.github.com/286072 the extension works fine as a regular extension. i'm trying this on the edge (current as of about an hour ago). It's probably a load order problem. Radiant adds the method to_name to String and perhaps it doesn't exist when KramdownFilter is loaded. http://github.com/radiant/radiant/blob/master/lib/plugins/string_extensions/lib/string_extensions.rb#L10-L12 Perhaps you can require that file in the extension, or maybe Radiant needs to address this by changing the load order ( since extensions as gems is the future). -Jim Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] trouble packaging extension as gem
both suggestions seem to fix the boot problem but now i don't see the new filter in the drop down. although i do see the extension listed on the extensions page. On Mon, Jan 25, 2010 at 1:05 PM, Sean Cribbs seancri...@gmail.com wrote: Actually, I imagine :lib = false would do the trick -- gem requirements are loaded before extensions. As long as your extension file explicitly loads that text filter, you should be fine. Sean On 1/25/10 1:51 PM, Jim Gay wrote: On Jan 25, 2010, at 1:08 PM, john muhl wrote: i hope someone can point out what stupid thing i've done in my first attempt to package an extension as a gem. http://gist.github.com/286072 the extension works fine as a regular extension. i'm trying this on the edge (current as of about an hour ago). It's probably a load order problem. Radiant adds the method to_name to String and perhaps it doesn't exist when KramdownFilter is loaded. http://github.com/radiant/radiant/blob/master/lib/plugins/string_extensions/lib/string_extensions.rb#L10-L12 Perhaps you can require that file in the extension, or maybe Radiant needs to address this by changing the load order ( since extensions as gems is the future). -Jim Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] trouble packaging extension as gem
by explicitly loads that text filter you just mean having: def activate KramdownFilter end right? i'm at loss now for why it's not appearing in the drop down when loaded as a gem. no errors or anything unusual just a missing filter. On Mon, Jan 25, 2010 at 1:05 PM, Sean Cribbs seancri...@gmail.com wrote: Actually, I imagine :lib = false would do the trick -- gem requirements are loaded before extensions. As long as your extension file explicitly loads that text filter, you should be fine. Sean On 1/25/10 1:51 PM, Jim Gay wrote: On Jan 25, 2010, at 1:08 PM, john muhl wrote: i hope someone can point out what stupid thing i've done in my first attempt to package an extension as a gem. http://gist.github.com/286072 the extension works fine as a regular extension. i'm trying this on the edge (current as of about an hour ago). It's probably a load order problem. Radiant adds the method to_name to String and perhaps it doesn't exist when KramdownFilter is loaded. http://github.com/radiant/radiant/blob/master/lib/plugins/string_extensions/lib/string_extensions.rb#L10-L12 Perhaps you can require that file in the extension, or maybe Radiant needs to address this by changing the load order ( since extensions as gems is the future). -Jim Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Configuring the admin panel
On 25.01.2010, at 15:58, Paul Fox wrote: I don't have write access to the apache config, and the admin doesn't know anything about rails, The admin do not need to know anything about rails. It is all standard apache ssl config stuff. so I really need to be able to hand him a working config the first time around. You find useful apache/passenger config extensions (like: RailsEnv production) in the passenger docs: http://www.modrails.com/documentation/Users%20guide%20Apache.html ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] [Radiant OFF FORUM] Configuring the admin panel
Thanks for your help. I will look into updating the wiki when I understand it a bit better myself, but right now I'm pressed for time, and getting the site up and running is my first priority. I originally hoped to learn ruby and rails better before this point, but it was not possible. Fortunately, I am able to use SSL (for the time being) since this is a private server and not a host, and no other sites hosted on the server require SSL right now. SSH ports aren't open, I've tried. The proxy allows connections to be made only to ports 80, 443, and 21. As far as network policy, I am a university student, and I am reasonably sure that I am not violating the network usage policy, as this website is most certainly for an educational purpose (and I cannot find anything in the policy that forbids what I am doing). Unfortunately, the reason that I am hosting this site off-campus instead of on university servers is that I have had no luck whatsoever getting out IT department to do anything at all for me (I have waited over four months for them to give me a database and am rather fed up), so a request for an exemption would likely as not never receive a response. Fortunately, I am making progress now, and I have everything working except the ssl_requirement extension, which I am trying to find a clean way to install (I'm not very keen on cloning a git repository into my radiant app directory). On Mon, Jan 25, 2010 at 8:27 PM, Anton Aylward anton.aylw...@rogers.comwrote: Paul Fox said the following on 01/25/2010 03:05 PM: Yeah, I was just a bit confused by the arbitrary mention of port 3000 in the docs with reference to the admin panel. The documentation for deployment could use some improvement, I think. Its a Wiki. You can update it. I you think it is lacking you *should* update it. The reference to port 3000 is*not* to the admin panel. If you were to run rail locally in your machine with $ ./script/server you'd get a response Booting Mongrel Rails 2.x.x application starting on http://0.0.0.0:3000 Call with -d to detach Ctrl-C to shut down server So: you would have a Mongrel server running listening on port 3000 If you now point you browser at http://0.0.0.0:3000 you will get your application. If you point your browser at http://0.0.0.0:3000/admin you will get the login to admin panel. My point is: the Mongrel server is listening on port 3000. Its the path you give it that determines whether you are displaying a page or the admin panel. http://mongrel.rubyforge.org/ Now read this before looking at Apache setup http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ http://wiki.joyent.com/shared:kb:rails-with-mongrel You'll particularly want to read this and forward to you Sysadmin http://wiki.rubyonrails.org/deployment/apache-mongrel in particular setting up the virtual host. I was planning on using mod_ssl for encryption. Now there you may have a problem. SSL uses X.509 and x.509 binds to a SINGLE IP ADDRESS. It one of the things I don't like about X,509. It makes life difficult for situations like this. Many service providers require that you get a dedicated address, not a shared virtual host, if you want SSL service. You are also going to have to apply for the X.509 certificate, have the sysadmin install it, bind it to the address and your domain. Maybe the service provider will do that for you. I hope so 'cos its a tedious procedure. This is why I use SSH tunnels for the situation you are getting yourself into. Its simpler to set up, doesn't require X.509. https://calomel.org/firefox_ssh_proxy.html I understand Apache configuration somewhat, so as long as that's all that is involved here, I shouldn't have issues. Since I'm not sysadmin and this is a shared host, I don't really have much choice as regards webserver. Also, Apache is the only webserver I have used so far, and I'd prefer not to have to learn something completely new right now. Apache is probably the most complicated web server around, if you ignore Microsoft's IIS. Things like Mongrel, WEBbrick, nhttpd, ngnix are all a lot simpler - the just work. http://en.wikipedia.org/wiki/Comparison_of_web_server_software The shared host may also preclude you being able to use SSL. Alas, I must use port 443, since I am administrating the site from behind an extremely restrictive proxy that only allows outgoing connections to particular ports (and only allows encrypted connections on 443). Check: you'll probably be able to use one of the SSH ports. If this is a non work project and you are doing this all from work, then there are over-riding legal issues. Check with your corporate legal department first. If this is a work project and work access then you may have good cause for an exception. I work in IT security and I'm used to dealing with all that. But before doing any
Re: [Radiant] Wordpress migration
I'm running the wordpress migrator, and one thing I noticed is that the model files shouldn't be run in order. User.rb first, then Post.rb, etc. I'll document it in the README until I have time to fork/batch/pull req. Anna ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
