Re: [Radiant] Custom Fields
Thanks Josh. I'll take a closer look at PageParts. I was manually creating page parts with this information before, so this would be an improvement. Looking forward to the screencasts. If you're on edge, PageParts + PageFactory might approximate what you're trying to do. PageParts would store those extra fields as parts, not in another association; so it might not be exactly what you're looking for. But right out of the box, PP + PF would let you do this: class EventPageFactory PageFactory::Base part Start Date, :page_part_type = DatePagePart part Organizer, :content = Default value goes here end I'm putting together a screencast on the two extensions, it should be posted in a few days. j ___ 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 -- marshal ___ 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] [ANN] Radiant 0.9.0 RC2
Excuse my ignorance, but the download link provides a source archive in zip or tgz format. How do I install a gem from it? And would this be equivalent to installing the previous rc1 gem and freezing to edge? On Tue, Apr 27, 2010 at 11:22 AM, Jim Gay j...@saturnflyer.com wrote: Announcing the second release candidate of Radiant 0.9.0. The big news in this release internationalization. For that we have many developers to thank, but in particular Keith Bingman for organizing the effort. There are a couple of changes that are worth mentioning, but see the http://github.com/radiant/radiant/blob/master/CHANGELOG for the full details. What’s changed? * The tab API has solidified. * There are new features for pagination (requiring will_paginate). * You can now run Radiant from a sub-directory. * When selecting a published date in the future, Radiant will treat the content as hidden until that date * Extensions may be loaded as gems and generated extensions now have features to easily create gems with Jeweler * We’re running on Rails 2.3.5 (but don’t worry, we’re working on Rails 3) If you are an extension developer, begin upgrading now. The official release of 0.9 is just around the corner. As always we welcome your feedback and contributions. Additionally, version 0.8.2 has quietly been released to prevent problems with running rake commands while newer cucumber versions are installed on your system. There are no new features in 0.8.2. Download Install You can download the gem here http://github.com/radiant/radiant/downloads Install it with the gem command: $ gem install radiant --prerelease This will install the gem as ‘radiant-0.9.0.rc2’. How to Upgrade an Existing Project or Site 1. Update the Radiant assets from in your project: rake radiant:update 2. Migrate the database: rake production db:migrate 3. Restart the web server -- 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 -- marshal ___ 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] Custom Fields
I'm looking at using the Custom Fields extension for some pages, for example pages with information about upcoming events. Each of these pages would have a custom field for start/end date, location, organizer, etc. Is there any way to create a template for these pages that would include the custom fields (maybe with default values)? I don't see how to do this with either the Stereotypes or Page Factory extensions. Thanks in advance for any help/suggestions. -- marshal ___ 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] Paperclipped extension problems
Hi all. I've discovered a problem with the Paperclipped extension not working properly when either the Drag or the Page Factory extensions are installed. Working with a clean install of Radiant 0.9 (from http://radiantcms.org/downloads/radiant-0.9.0-rc1.gem) and freezing to edge: radiant r9 --database sqlite3 cd r9 rake radiant:freeze:edge rake radiant:update rake production db:bootstrap Install the Paperclipped extension: git clone --branch 0.9.0 git://github.com/kbingman/paperclipped.git vendor/extensions/paperclipped rake production radiant:extensions:paperclipped:migrate this generates an error wrong number of arguments (3 for 2) which I worked around by changing line 55 of paperclipped_extension.rb from -- admin.nav[:content] admin.nav_item(:assets, Assets, /admin/assets) to -- admin.nav[:content] admin.nav_item(Assets, /admin/assets) rake production radiant:extensions:paperclipped:update Everything works as expected until I install Drag (or Page Factory): git clone git://github.com/squaretalent/radiant-drag-extension.git vendor/extensions/drag rake production radiant:extensions:drag:migrate rake production radiant:extensions:drag:update Paperclipped gets messed up; the Show Assets Bucket link is shoved over to the left of the pane and is colored blue, the popup dialog for managing assets is not displayed properly, and the drag n drop operation no longer works. The order of installing the the extensions doesn't seem to matter -- same corruption of Paperclipped. I have no idea where or what is causing the conflict. Hopefully, someone more skilled than me will be able to figure it out. Thanks in advance. -- marshal ___ 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] 0.9.0-rc1 and settings extension
I decided to take the plunge and investigate Radiant 0.9.0-rc1. Some things worked as expected and some didn't. Here's what I encountered; hope this might be helpful to others and/or provide information to developers and extension writers. Desktop: Ubuntu Lucid Lynx, Linux 2.6.32-21-generic Gems: (left out ones not used by radiant) activesupport (2.3.5) compass (0.10.0.rc3, 0.8.17) compass-960-plugin (0.9.13) haml (3.0.0.beta.2, 2.2.23) imagesize (0.1.1) mime-types (1.16) mysql (2.8.1) rack (1.0.1, 1.0.0) radiant (0.9.0, 0.8.1) rake (0.8.7) RedCloth (4.2.3, 4.2.2) rmagick (2.13.1, 2.12.2) rubygems-update (1.3.6) sqlite3-ruby (1.2.5) Radiant: radiant r9 --database sqlite3 cd r9; rake production db:bootstrap [answer prompts, select 1. Empty] Settings extension: git clone git://github.com/squaretalent/radiant-settings-extension.git vendor/extensions/settings rake production radiant:extensions:settings:migrate radiant:extensions:settings:update *** rake fails with undefined method `tab' for #SettingsExtension:0xb6ea8e0c same thing if the script/extension install settings command is used instead Here's the trace: mars...@vaio[~/web/r9] rake production radiant:extensions:settings:migrate --trace (in /home/marshal/web/r9) ** Invoke production (first_time) ** Execute production ** Invoke environment (first_time) ** Execute environment rake aborted! undefined method `tab' for #SettingsExtension:0xb6f17e4c /home/marshal/web/r9/vendor/extensions/settings/settings_extension.rb:29:in `activate' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/lib/radiant/extension.rb:60:in `activate' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:105:in `to_proc' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/lib/radiant/extension_loader.rb:98:in `each' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/lib/radiant/extension_loader.rb:98:in `activate_extensions' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/lib/radiant/initializer.rb:184:in `after_initialize' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/railties/lib/initializer.rb:179:in `process' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/railties/lib/initializer.rb:113:in `send' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/railties/lib/initializer.rb:113:in `run' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/lib/radiant/initializer.rb:148:in `run' /home/marshal/web/r9/config/environment.rb:12 /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:156:in `require' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in `new_constants_in' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:156:in `require' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/railties/lib/tasks/misc.rake:4 /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib/ruby/gems/1.8/gems/radiant-0.9.0/lib/tasks/environments.rake:10 /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 Any ideas? -- marshal
[Radiant] 0.9.0-rc1 experience
Taking 0.9 out for a test drive... here's an overview of what worked and what didn't. Radiant: radiant r9 --database sqlite3 cd r9; rake production db:bootstrap [answer prompts, select 1. Empty] The extensions I tried that installed and worked as expected were (some required a little tweaking): Custom Fields: script/extension install custom_fields Drag: [ok but messes up paperclipped, more about this in a separate post] git clone git://github.com/squaretalent/radiant-drag-extension.git vendor/extensions/drag rake production radiant:extensions:drag:migrate radiant:extensions:drag:update Schedule: [anyone up to adding this into the extension registry so script/extension can install it?] git clone git://github.com/radiant/radiant-scheduler-extension.git vendor/extensions/scheduler rake production radiant:extensions:scheduler:migrate radiant:extensions:scheduler:update Page Preview: script/extension install page_preview Enkoder Tags: script/extension install enkoder_tags Styles n Scripts: script/extension install sns Sass filter: *** script/extension install fails with: Too many arguments and cd: 1: can't cd to /tmp/sns_sass_filter - manual install works git://github.com/SwankInnovations/radiant-sns-sass-filter-extension.git vendor/extensions/sns_sass_filter Haml filter: script/extension install haml_filter The ones that I couldn't get to work were (details in separate posts): Settings extension *** rake fails with undefined method `tab' for #SettingsExtension:0xb6ea8e0c Page Factory extension *** installs without any errors but does not work correctly - Add Child icon replaced with en, add_child text - pop-up works but new employee page does not have proper page parts, same default page as without the extension Paperclipped extension *** installs without any errors, but Show Assets Bucket in odd place (should be like Create Custom Fields?) - if the Drag extension is installed either before/after paperclipped, it messes up the Assets pop-up, can't drag n drop. Gallery extension *** install task fails -- can't create gallery.yml or content_types.yml - copied these 2 files from my production system but rake fails with: undefined method `tab' for #GalleryExtension:0xb6dfdee4 PS. Great work by everyone involved, core developers and extension writers! Thank you so much. -- marshal ___ 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] 0.9.0-rc1 experience (Marshal Linfoot)
Thanks for the reply Josh (and for the great extension that I can't wait to use!) I do have the Radiant 0.9.0 gem installed, and everything looks like 0.9.0, but maybe there is something corrupted? I did try updating to edge before, several times over a few days, and ran into an error message about undefined method `tab' (don't have the exact message anymore). Tried again tonight and updating to edge worked without error. Installed Page Factory and it works like a charm. Settings extension also working. No idea what changed. Maybe some updates on the bleeding edge? Anyway, looks great so far. Time to start over and see if the rest of the extensions I want will now install correctly. Thanks again for the help. On Sun, Apr 18, 2010 at 11:00 PM, Josh French j...@digitalpulp.com wrote: Taking 0.9 out for a test drive... here's an overview of what worked and what didn't. Radiant: radiant r9 --database sqlite3 cd r9; rake production db:bootstrap Hi Marshal, Based on these error messages it sounds like you're not actually running 0.9. The latest gem is still Radiant 0.8.1. To check out edge: radiant r9 -d sqlite3 cd r9 rake radiant:freeze:edge rake radiant:update rake db:bootstrap That should fix most or all of your errors. j -- marshal ___ 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] SnS Usage Questions -- I Need Feedback
On Fri, Oct 9, 2009 at 3: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... Been waiting for this. Great news! 1. Does anyone use custom values for the SnS settings? These include: * css_dir * js_dir * css_mime * js_mime 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? Don't use. Defaults are fine. 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. I like this idea. Thanks. Thanks, Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] FAQ Extension
Nate, nice improvement. Thanks!
On Wed, Jul 8, 2009 at 11:30 AM, NT pixeln...@gmail.com wrote:
Marshal Linfoot wrote:
Elaborating on Mohit's suggestion...
Parent Index page:
div class=faqlist
ol
r:children:each
lia href=#r:slug /r:title //a/li
/r:children:each
/ol
/div
r:children:each
div class=faqitem
a name=r:slug /h3r:title //h3/a
r:content /
/div
/r:children:each
Sample child page (question as the title of the page)
pTo be or not to be, that is the question/p
Here it is on my site: http://www.octopusgardenyoga.com/FAQ
I would suggest that you use Definition Lists to display the items. So,
with some CSS slimming, it would be something like this:
Parent Index page:
ol id=faqlist
r:children:each
lia href=#r:slug /r:title //a/li
/r:children:each
/ol
dl id=faqitems
r:children:each
dta name=r:slug /r:title //a/dt
ddr:content //dd
/r:children:each
/dl
That way styling is a bit more straightforward.
Instead of:
div.faqitem a h3 {...}
You have:
dt {...}
or
dt a {...}
Just a suggestion.
~Nate
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
--
marshal
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] FAQ Extension
Elaborating on Mohit's suggestion... Parent Index page: div class=faqlist ol r:children:each lia href=#r:slug /r:title //a/li /r:children:each /ol /div r:children:each div class=faqitem a name=r:slug /h3r:title //h3/a r:content / /div /r:children:each Sample child page (question as the title of the page) pTo be or not to be, that is the question/p Here it is on my site: http://www.octopusgardenyoga.com/FAQ Hope this is helpful to someone. Suggestions for improvement always welcome. On Mon, Jun 29, 2009 at 10:34 PM, Mohit Sindhwanit...@onghu.com wrote: Jim Gay wrote: On Jun 25, 2009, at 3:30 PM, Merk S wrote: Hi Guys, Before i write this myself, i was wondering if anyone has already worked on or is aware of an existing FAQ extension? Googling has been tough due to 'FAQ' turning up lots of helps/tutorial pages for ruby/radiant. :) thanks!! If you only need something like a question a page, then it's not a bad idea to have just an FAQ index page with each question being a question. Then, at the index page, just collect the questions by doing a r:children:each and show the body of the child page. You could even make each of the questions an anchor by giving a name to the div. Search a thread called Index at top of page in the archive to see what I mean. Cheers, Mohit. 6/30/2009 | 10:34 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 500 Internal server errors with Radiant 0.7.1 and SNS
Same/similar problem. What fixed it for me was renaming the column filename to name in the text_assets table and renaming column list to names in the text_asset_dependencies table: mysql alter table text_assets change column filename name varchar(100); mysql alter table text_asset_dependencies change column list names varchar(255); Hope this helps someone. On Thu, Apr 9, 2009 at 12:30 AM, N. Turnage pixeln...@gmail.com wrote: I am running into the same problems with SNS that were mentioned here: http://www.ruby-forum.com/topic/176102 And just like the original person having problems, the info here was not the fix for it: http://www.nabble.com/SnS-Extension---500-Error-td21486070.html This is the error: Status: 500 Internal Server Error Content-Type: text/html 500 Internal Server Error Anybody have a fix for it? I have 5 stylesheets that I would really rather not bring into the main admin area. Thanks, ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- marshal ___ 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 question: db bootstrap failure problem
Tom, I;m running Radiant on Ubuntu 6.06.1 (*Dapper* Drake) without any problems. I wonder if your openssl libraries are too new. The output from locate openssl on my server shows only 2 lines: /usr/lib/libgnutls-openssl.so.12 /usr/lib/libgnutls-openssl.so.12.3.6 /usr/lib/libgnutls-openssl.so.12 is a link to the actual library file, /usr/lib/libgnutls-openssl.so.12.3.6, so you could try the following: sudo ln -s /usr/lib/libgnutls-openssl.so.13.9.1 /usr/lib/libgnutls-openssl.so.12 to create a similar link to your newer library. A shot in the dark ... if it doesn't work, remove the link with: sudo rm /usr/lib/libgnutls-openssl.so.12 On Mon, Aug 4, 2008 at 12:17 PM, Tom Cloyd [EMAIL PROTECTED] wrote: First, following from my previous post: the Summer Reboot project is a very exciting prospect. Its very nice to see the outline laid out as it is. I'll stay in close touch with this effort. Now...my next problem - Following along at http://wiki.radiantcms.org/Installation, the Bootstrap the Database section: I have a project - radiant-test started. I'm running Kubuntu Linux 8.04.1 and Ruby 1.8.6. Console output: [EMAIL PROTECTED]:~/Ruby-work/radiant-test$ rake development db:bootstrap (in /home/tomc/Ruby-work/radiant-test) rake aborted! no such file to load -- openssl Checking with the adept package manager, I see that I do have the openssl module (or whatever) installed. This is as far as I can go without help - don't know how to fix this. Don't even know what the problem is, in fact. All assistance will be gratefully received (especially if it resolves the problem!). t. -- ~ Tom Cloyd, MS MA, LMHC - Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 [EMAIL PROTECTED] (email) TomCloyd.com (website psychotherapy weblog) sleightmind.wordpress.com (mental health issues weblog) ~ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- marshal ___ 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 extension problem -- Fixed (New SnS Release)
Hi Chris. I hate to say it, but no change. Downloaded the latest version from the link in your message to vendor/extensions/sns. Ran the rake tasks again just to be safe. Page still displays without any styling. Here's what I see when accessing the css/elastic page directly: [EMAIL PROTECTED] curl -I test.octopusgardenyoga.com/css/elastic HTTP/1.1 404 Not Found Content-Type: text/css; charset=utf-8 Last-Modified: Wed, 23 Jul 2008 16:36:09 GMT X-Runtime: 0.00239 ETag: f95c66d251410f2f579f72e87fd28049 Date: Mon, 28 Jul 2008 13:42:16 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 PS. Minor thing...version says 0.5 on the Admin UI Extensions page. On Mon, Jul 28, 2008 at 2:15 AM, Chris Parrish [EMAIL PROTECTED] wrote: Marshal, those links helped. The controller/models weren't declaring a status code on success (just on failures) and apparently LiteSpeed doesn't like that (though Mongrel and Webrick seem just fine with it). Anyway, I've released an updated version of SnS to address this. You can get it here: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/latest The new and improved specs now claim it's working but I don't run LiteSpeed. Could you (or somebody) test this to make sure it solves this issue? -Chris -- marshal ___ 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 extension problem -- Fixed (New SnS Release)
That did it! Working like a charm now. Thank you very much Chris for a great extension and for all the help getting it to work with LiteSpeed. On Mon, Jul 28, 2008 at 12:33 PM, Chris Parrish [EMAIL PROTECTED] wrote: Oh, I forgot to mention, you'll need to clear the text asset cache too so that the new status header gets updated. You can do this one of two ways: 1. Save a javascript or stylesheet file (this will clear the cache for all javascripts and stylesheets). 2. Delete the text asset cache directory manually (the next request for each file will rebuild your cache). The default location for this is: [RADIANT_ROOT]/text_asset_cache. Also, I've just corrected the version issue and committed SnS v0.6.2 as the new latest version. (You can update your version of the extension but it won't affect this status header issue). Anyway, please test either version for me once you've cleared the cache and tell me if that fixes it. If it doesn't, please browse to the text asset cache directory and check the contents of the YML part of the cached file (given the default location above, it would be at: [RADIANT_ROOT]/text_asset_cache/stylesheet_cache/[your_file_name].yml). It should look something like: --- expires: 2009-07-28 10:25:57.84 -06:00 headers: Last-Modified: Thu, 19 Jun 2008 00:30:15 GMT Status: 200 OK cookie: [] Content-Type: text/css The line I care about is the Status: 200 OK one. Make sure it's there. -Chris -- marshal ___ 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 extension problem
Hi Chris. I found a couple of threads in the litespeed forums that might be helpful. http://www.litespeedtech.com/support/forum/showthread.php?t=1422 http://www.litespeedtech.com/support/forum/showthread.php?t=821 -- marshal ___ 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 extension problem
OK Chris, I get it now. Ready for you to take a look. Thanks for all of this, by the way. Much appreciated. On Wed, Jul 23, 2008 at 7:14 PM, Chris Parrish [EMAIL PROTECTED] wrote: Marshal Linfoot wrote: Chris, I hope this is what you had in mind...a slimmed down version of what I currently use for the live site. Not quite. That looks like a regular html page and not a css one. To create what I was talking about, do the following: 1. Create a new template\ * Name it: CSS * Expand the more button and change the content-type to: text/css * In the body of the layout, put nothing but: r:content * save the layout 2. Go to your tester page and change its layout to: CSS This should serve up your tester page using text/css mime type and without all the header/footer layout stuff. -Chris -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] SnS extension problem
Hi all.
I'm having a problem with the SnS extension and need some help.
Radiant 0.6.7 (gem) and Styles and Scripts extension v0.6. The
extension installed without any errors, I can access the CSS and JS
tabs, and have created a stylesheet called elastic.
In the layout for my pages I have: r:stylesheet name=elastic
as=link media=screen / which renders as link rel=stylesheet
href=/css/elastic type=text/css media=screen /. Looks okay to
me, but the page renders without the css being applied -- no styling.
The Radiant production log shows:
Processing SiteController#show_page (for 99.232.3.139 at 2008-07-23
14:58:33) [GET]
Parameters: {url=/, action=show_page, controller=site}
Completed in 0.19283 (5 reqs/sec) | DB: 0.0 (0%) | 200 OK
[http://test.octopusgardenyoga.com/]
Processing SiteController#show_page (for 99.232.3.139 at 2008-07-23
14:58:34) [GET]
Parameters: {url=[css, elastic], action=show_page,
controller=site}
Filter chain halted as
[#ActionController::Filters::ClassMethods::SymbolFilter:0x2adc426c66d0
@filter=:parse_url_for_text_a
ssets] rendered_or_redirected.
Completed in 0.01643 (60 reqs/sec) | DB: 0.0 (0%) | 304 Not
Modified [http://test.octopusgardenyoga.com/css/elastic]
I have no idea why the css isn't being applied. Tried naming it
elastic.css, same results. Tried r:stylesheet name=elastic
as=inline / and it places the css inline as expected, but no
styling.
Thanks for any help. I'm eager to use this extension for all the good
reasons Chris mentions in the README.
PS. You can see the rendered pages at http://test.octopusgardenyoga.com
--
marshal
___
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 extension problem
Thanks for all the quick responses! Removing the @import line fixes it for Safari, but Firefox 2.0.0.16 (MacOSX) and FF 3.0 (Ubuntu Linux) are still unstyled. Also, as Chris said if you download and run locally with FF, all's well. I'm hosting on Slicehost with the Litespeed web server. Could it be some quirk with Litespeed? Thanks again for all the help so far. -- marshal ___ 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 extension problem
Keith, here's the config table: mysql select * from config; ++--++ | id | key | value | ++--++ | 1 | admin.title | Radiant CMS| | 2 | admin.subtitle | Publishing for Small Teams | | 3 | defaults.page.parts | body, extended | | 4 | defaults.page.status | draft | | 5 | gallery.path_prefix | public/galleries | | 6 | gallery.processor| rmagick| | 7 | gallery.gallery_based| false | | 8 | SnS.stylesheet_directory | css| | 9 | SnS.javascript_directory | js | | 10 | SnS.stylesheet_mime_type | text/css | | 11 | SnS.javascript_mime_type | text/javascript| ++--++ All's well there. On Wed, Jul 23, 2008 at 11:28 AM, Keith Bingman [EMAIL PROTECTED] wrote: The other thing you need to check is that the header is being set correctly. SnS uses a config setting in the database for this, is should be set to text/css. Strangely, the link you sent renders perfectly in Safari, though in FF it renders without css... Keith ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- marshal ___ 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 extension problem
Chris, I hope this is what you had in mind...a slimmed down version of what I currently use for the live site. stylesheet layout template with r:content and a content-type of text/css A styles page that uses the stylesheet template, and child page test with slug test.css Simple layout template called test with link href=/styles/test.css rel=stylesheet type=text/css / to use css the old-fashioned way Simple page called tester that uses the test layout template. View the rendered page at http://test.octopusgardenyoga.com/tester PS. How do you see all the HTTP response headers? On Wed, Jul 23, 2008 at 6:10 PM, Chris Parrish [EMAIL PROTECTED] wrote: As you mentioned, the full file is being served up but the response includes: RESPONSE: HTTP/1.1 404 Not Found That has to be the problem but what is the cause? Anybody know enough about LightSpeed to know if this is a server issue (mime-type config, perhaps)? In the meantime, can you create a CSS page the old-fashioned way (build a template with just r:content and a content-type of text/css then create a regular old page that uses that layout)? I'd like to know what its headers look like (does it come up with a 200 like your home page or 404 like the stylesheets). That may tell us if it is server related or not. -Chris -- marshal ___ 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 extension problem
Hi all. I did some more testing via CrossBrowserTesting.com and for what it's worth, both Opera and Safari on Windows XP display the styled pages. FF and IE don't. -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] upgrading 0.6.6+shards extension to 0.6.7
My experience with upgrading from 0.6.4 to 0.6.7, in case someone is in a similar situation... I'm using several extensions: gallery (0.7.8), scheduler (0.2), reorder (0.1 with the up/down icons in the adminUI), and shards (0.3). Having read in other posts that the shards extension was integrated into 0.6.7 and no longer needed, I removed the reference to it from config/environment.rb and deleted the shards directory from vendor/extensions. Installed the latest radiant gem and ran the rake update. The rake radiant:update creates a new config/environment.rb file. I updated it to put the RADIANT_GEM_VERSION constant back in and set it to 0.6.7. The rake production db:migrate failed with an error related to the reorder extension. Deleted the reorder directory from vendor/extensions and the migration ran without any errors. Gallery and scheduler extension did not cause any problems. Running 0.6.7, everything looking good (except pages are all out of order, of course). There are a couple of other extensions similar to reorder that I wanted to try, copy-move and a drag-n-drop reorder. Grabbed the copy-move from git, but its rake install failed because it needs the shards extension. Same thing with the drag-n-drop reorder. So, installed shards, updated the config/environment.rb file accordingly and the copy-move and a drag-n-drop reorder extensions installed without any problems. Tried removing the shards extension to see if it was still needed, but the webserver choked with a 505 error; put it back in and all seems to be okay. Hope this is helpful to someone. PS. copy-move and the drag-n-drop reorder extensions are great! Thanks. On Fri, May 16, 2008 at 5:44 PM, john muhl [EMAIL PROTECTED] wrote: UPGRADING FROM 0.6.x 1. Update the Radiant gem: % gem update radiant 2. Change the RADIANT_GEM_VERSION constant in config/environment.rb to 0.6.7. 3. Run the update rake task: % rake radiant:update 4. Run migrations: % rake db:migrate 5. Restart the server Should an existing shards extension be removed before upgrading? Is removing the shards edit from environment.rb and the shards folder from vendor/extensions the proper way to uninstall the extension version? thanks. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- marshal ___ 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 the gallery extension
Hi Ollivier. ...some of this you might have already figured out.
Create a new gallery by going to the Admin UI and clicking on the
Galleries tab. Click on the New Gallery button and from there
upload some pics, edit the gallery description, etc. Name the gallery
MyPics for example.
Then go to the Pages tab and create a new page, call it Photos for
example, and make sure you select the Gallery page type from the
Page Type drop-down selections. In the body of this page, you'll put
some html and radiant tags to display pics from your MyPics gallery.
Here's the code I use for my galleries with some explanations added:
!-- galleries --
r:gallery:if_galleries
div class=galleries
## I have several galleries, so the next statement loops through each
of them, producing links to the individual
## galleries. You can still do this even with only one gallery.
r:galleries:each level=current
div class=gallery
r:gallery:if_items
div class=thumb style=background-image:
url('r:gallery:item:thumb width=120 position=first /');
a href=r:gallery:gallery_url /
title=r:gallery:name /
r:gallery:name /
/a
/div
/r:gallery:if_items
div class=description
h2r:gallery:link //h2
pr:gallery:description //p
/div
div class=clearer/div
/div
/r:galleries:each
/div
/r:gallery:if_galleries
!-- end galleries --
r:gallery:unless_galleries
!-- items --
r:gallery:item:unless_current
r:gallery:if_items
div class=gallery
pr:gallery:description //p
## This next loop picks up information about each item (ie. photo) in
the gallery and creates thumbnails and links
## to each of the photos. This is what you see when you click on the
gallery link produced above.
r:gallery:items:each
!-- item --
div class=container
div class=thumb style=background-image:
url('r:gallery:item:thumb width=150 /')
a href=r:gallery:item:thumb width=500 /
rel=lightbox[r:gallery:name /] title=r:gallery:item:name /
r:gallery:item:name /
/a
/div
/div
!-- end item --
/r:gallery:items:each
div class=clearer/div
/div
/r:gallery:if_items
/r:gallery:item:unless_current
!-- end items --
!-- item page --
## This next bit is what formats the page for individual photos, with
navigation links to next/previous items.
r:gallery:item:if_current
r:gallery:item:current
div class=item
div class=navigation
div class=prev
r:gallery:item:if_prev
a href=r:gallery:item:prev_page_url /laquo;
prev/a
/r:gallery:item:if_prev
/div
div class=next
r:gallery:item:if_next
a href=r:gallery:item:next_page_url /next
raquo;/a
/r:gallery:item:if_next
/div
div class=clearer/div
/div
div class=clearer/div
h2r:gallery:item:name //h2
div class=image
a href=r:gallery:item:path /
img src=r:gallery:item:thumb width=450 /
alt=r:gallery:item:name / /
/a
/div
p
r:gallery:item:description /
/p
/div
/r:gallery:item:current
/r:gallery:item:if_current
!-- end item page --
/r:gallery:unless_galleries
Most of the above code will be in the sample gallery, if you installed it.
Assuming you used my example names, you can go to
yourwebsiteaddress/photos (the Photos gallery-type page) and the
above code should display your MyPics gallery (and any others you
add later).
Hope this helps.
On Sun, May 18, 2008 at 1:04 AM, Ollivier Robert [EMAIL PROTECTED] wrote:
OK, I guess I must be missing something obvious but I just can't see
how it works. I've created public/galleries, create a Test one, put
a picture in it and... where is it supposed to appear?
/galleries/index? /galleries/Test? Do I have to create an new Page
with one of the gallery layouts, probably with a Gallery page type?
Is it documented somewhere??
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
--
marshal
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search:
[Radiant] Upgrading Gallery Extension
I'm currently using Andrea Franz's amazing Gallery extension, version 0.7.6, and would like to upgrade to his latest 0.7.10 version. Would I use the same procedure as installing it the first time or is there a different upgrade procedure? I don't want to lose the existing galleries... Thanks for any pointers. -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Upgrading Gallery Extension
YIKES! Following the instructions for installing the Gallery extension I did the following: cd vendor/extensions git clone git://github.com/pilu/radiant-gallery.git gallery and got a message that git-clone would not overwrite an existing directory (a good thing!). So I ran this instead: git clone git://github.com/pilu/radiant-gallery.git gallery2 creating a new directory, gallery2, and the whole website stopped functioning with a server temporarily busy message. Restarted LiteSpeed - no change. No errors in the LiteSpeed logs. Moved the new gallery2 dir out of the way, restarted LiteSpeed and everything back to normal. Whew! Thinking it was permissions problems on gallery2, I changed them all to match the working gallery. Moved gallery2 back into vendor/extensions and same thing all over again. I'm stuck now, unsure of how to upgrade. But I suspect something like: disable current gallery from the main admin page move gallery dir out of vendor/extensions move gallery2 into vendor/extensions and rename to gallery run the rake install task restart LiteSpeed Anyone successfully upgraded? What did you do, am I on the right track? On Mon, May 5, 2008 at 12:40 PM, Andrea Franz [EMAIL PROTECTED] wrote: On Mon, May 5, 2008 at 6:17 PM, Marshal Linfoot [EMAIL PROTECTED] wrote: I'm currently using Andrea Franz's amazing Gallery extension, version 0.7.6, and would like to upgrade to his latest 0.7.10 version. Would I use the same procedure as installing it the first time or is there a different upgrade procedure? I don't want to lose the existing galleries... Thanks for any pointers. You can launch the radiant:extensions:gallery:install task. This will trigger the migrations and it will upgrade the public files without deleting anything from the db. -- Andrea Franz http://gravityblast.com - http://nimboo.net ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] New Radiant powered site
Hi all. I wanted to say a big thank you to everyone involved in the Radiant development and also to everyone contributing tips/suggestions on the mailing list. I'm using Radiant for a fairly simple website and finding it very easy to use and very flexible. The website is http://www.octopusgardenyoga.com and it uses a few third-party extensions: gallery, reorder, scheduler, and shards. A special thanks to the people who contributed these great additions. Again, thanks to all and if you have any questions about how our site was constructed, please ask. -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
