Re: [Radiant] Maxlength attribute not displaying on mailer generated form
On Thu, Apr 29, 2010 at 9:37 AM, Victor Zuniga vzun...@westervillelibrary.org wrote: One of our staff members encountered an interesting behavior when setting up a form for a local activity. They wanted to limit the amount of characters a user can type within the text box. They went ahead and used the maxlength in the following manner: r:mailer:text name=1engraving4x8 id=1engraving4x8 maxlength=13 / However, when looking at the generated page on the browser (View Page Source) the attribute is nowhere to be found. If I go back to edit the page, I¹ll find the attribute where is meant to be placed. Any ideas as to why is not displaying when using the mailer form tags? the mailer extension only allows you to pass the size, class and id attributes through. i've run into this before and in my fork accept many more attributes. ___ 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] Maxlength attribute not displaying on mailer generated form
On Thu, Apr 29, 2010 at 12:04 PM, Jim Gay j...@saturnflyer.com wrote: On Apr 29, 2010, at 11:03 AM, john muhl wrote: On Thu, Apr 29, 2010 at 9:37 AM, Victor Zuniga vzun...@westervillelibrary.org wrote: One of our staff members encountered an interesting behavior when setting up a form for a local activity. They wanted to limit the amount of characters a user can type within the text box. They went ahead and used the maxlength in the following manner: r:mailer:text name=1engraving4x8 id=1engraving4x8 maxlength=13 / However, when looking at the generated page on the browser (View Page Source) the attribute is nowhere to be found. If I go back to edit the page, I¹ll find the attribute where is meant to be placed. Any ideas as to why is not displaying when using the mailer form tags? the mailer extension only allows you to pass the size, class and id attributes through. i've run into this before and in my fork accept many more attributes. John, I just added you to the mailer repository. Feel free to update it. i've pushed up the changes now. some of the new html5 inputs types are added and most attributes are now allowed (the few i left out didn't seem to make sense in this context). if you're trying to set boolean attributes you'll need to use the long version; e.g. autofocus=autofocus ___ 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 page_attachment
On Thu, Apr 29, 2010 at 3:16 PM, Horst Rischbode ho...@horibo.de wrote: Hi John, thanks for the quick answer. Tried to follow Your instructions but failed. git checkout... raises an error: fatal: git checkout: updating paths is incompatible with switching branches. Did you intend to checkout 'radiant-0.8.0' which con not be resolved as commit? Sorry, but I'm an absolute newby to git. I'm working an a windows development machine. Don't know, if git bash for windows behaves as expected in this situation. Is there a way to download the right version via web? try this link: http://github.com/radiant/radiant-page-attachments-extension/archives/radiant-0.8.0 ___ 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 page_attachment
you need the 0.8 branch cd radiant/vendor/extensions git clone git://github.com/radiant/radiant-page-attachments-extension.git page_attachments cd page_attachments git checkout -b 0.8 radiant-0.8.0 cd ../../.. rake radiant:extensions:page_attachments:migrate rake radiant:extensions:page_attachments:update On Wed, Apr 28, 2010 at 2:34 PM, Horst Rischbode ho...@horibo.de wrote: Hello, trying to get started with page_attachments extension. I'm running Radiant 0.8.1. Installation was successful. rake tasks migrate update ran without any errors. In Database, I have a new table page_attachments and under each page in Admin-Interface, I get the expected page attachment stuff. So far so good... But if I click the '+' sign, nothing happens. This is the case for all page types. Tried to reorder the loading of extensions via environment.rb. Nothing changes. My development.log doesn't show any entry for hitting the '+' sign. Any ideas? Thanks Horst ___ 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] page factory css
i installed the page factory extension and ran the migrate/update tasks but the page_factory.css is not being included in the admin ui. i see the public/stylesheets/admin/page_factory.css file but it's not being added to the @stylesheets array while other css (e.g. page_attachments.css) are included as expected. this is on the current master. any hints? ___ 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] page factory css
On Wed, Apr 28, 2010 at 10:18 PM, Josh French j...@digitalpulp.com wrote: oops. i meant that it's not included on the factory pages but is included on the main page list. That's correct. The CSS only styles the popup on the pages index, so I didn't include it on the new/edit screens. that explains that :) i was trying to apply some styling to the descriptions to set them off from the other stuff in the tab area i guess it should be easy enough to add in overrides.css I should have time tomorrow to look at the other issues you filed on Github. Thanks for the feedback! 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 ___ 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] RadiantCasts episode 8
On Thu, Apr 15, 2010 at 3:00 PM, Cristi Duma cristi.d...@aissac.ro wrote: bliptv provides a .mov version but I think their TOS don't allow me to publish deep links to those .mov versions. I'll have to check that up, just to be sure. surely they don't have a problem with linking to http://blip.tv/file/3479659/ right? no need for a link directly to the file if they have a problem with that. ___ 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] RadiantCasts episode 8
On Wed, Apr 14, 2010 at 1:50 AM, Cristi Duma cristi.d...@aissac.ro wrote: @John if you mean like downloading .mov version from amazon or something similar... you can't. nor can i watch them in the first place since i do not have flash installed. Maybe in the future, but at the moment i'm only investing time in Radiantcasts. why spend the time to output flash? why not just output something that everyone can watch? ___ 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] RadiantCasts episode 8
...or just add the link to the .mov version that blip.tv automatically creates to the post...by the way it's embed src=abc not embed src=xyz/embed On Wed, Apr 14, 2010 at 9:25 AM, Joel Oliveira joel.olive...@gmail.com wrote: If you can get the url to the FLV from Cristi then you should be able to watch it in something like VLC. Even without flash installed (I do believe). - Joel On Wed, Apr 14, 2010 at 10:18 AM, john muhl johnm...@gmail.com wrote: On Wed, Apr 14, 2010 at 1:50 AM, Cristi Duma cristi.d...@aissac.ro wrote: @John if you mean like downloading .mov version from amazon or something similar... you can't. nor can i watch them in the first place since i do not have flash installed. Maybe in the future, but at the moment i'm only investing time in Radiantcasts. why spend the time to output flash? why not just output something that everyone can watch? ___ 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] [ANN] RadiantCasts episode 8
On Wed, Apr 14, 2010 at 9:41 AM, Cristi Duma cristi.d...@aissac.ro wrote: yeah, great idea http://blip.tv/file/get/Radiantscreencast-Episode8RadiantChronicleExtension139.mov hope it works thanks. About the embed stuff... i just copy paste it from bliptv. ah. they probably think they're writing XHTML :) Umm.. how come you don't have flash installed? I hate flash, too but I just use a flash block add-on and what about mobile devices that just can't run flash? On Wed, Apr 14, 2010 at 5:37 PM, john muhl johnm...@gmail.com wrote: ...or just add the link to the .mov version that blip.tv automatically creates to the post...by the way it's embed src=abc not embed src=xyz/embed On Wed, Apr 14, 2010 at 9:25 AM, Joel Oliveira joel.olive...@gmail.com wrote: If you can get the url to the FLV from Cristi then you should be able to watch it in something like VLC. Even without flash installed (I do believe). - Joel On Wed, Apr 14, 2010 at 10:18 AM, john muhl johnm...@gmail.com wrote: On Wed, Apr 14, 2010 at 1:50 AM, Cristi Duma cristi.d...@aissac.ro wrote: @John if you mean like downloading .mov version from amazon or something similar... you can't. nor can i watch them in the first place since i do not have flash installed. Maybe in the future, but at the moment i'm only investing time in Radiantcasts. why spend the time to output flash? why not just output something that everyone can watch? ___ 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 ___ 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] RadiantCasts episode 8
On Wed, Apr 14, 2010 at 11:37 AM, Jeff Casimir j...@casimircreative.com wrote: Hey John, Sorry if this comes off dick-ish, but I just wanted to remind you that Cristi is making these videos for the good of everybody on his freetime -- not even ad supported. and now that i've discovered the videos are hosted on blip.tv which provides a non-flash version i can appreciate his efforts. it's positively awesome and i'm going to be adding links to the wiki. I'm no flash lover myself, but I don't think he's being pretentious or anything posting them from a flash-based system. Let's get solutions-oriented. someone mentioned that vlc may be able to play the flv directly so i went looking through the html looking for the flv url. instead i found a bit that lead me to blip.tv to discover that there already was a non-flash version. then i suggested that a link to the non-flash version be included in the posts. problem solved. Are you trying to view them in an HTML5-compliant browser? Maybe suggest an HTML5 site he could host the videos at? Your line of comments so far have been a little antagonistic. sorry. On Wed, Apr 14, 2010 at 10:57 AM, john muhl johnm...@gmail.com wrote: On Wed, Apr 14, 2010 at 9:41 AM, Cristi Duma cristi.d...@aissac.ro wrote: yeah, great idea http://blip.tv/file/get/Radiantscreencast-Episode8RadiantChronicleExtension139.mov hope it works thanks. About the embed stuff... i just copy paste it from bliptv. ah. they probably think they're writing XHTML :) Umm.. how come you don't have flash installed? I hate flash, too but I just use a flash block add-on and what about mobile devices that just can't run flash? On Wed, Apr 14, 2010 at 5:37 PM, john muhl johnm...@gmail.com wrote: ...or just add the link to the .mov version that blip.tv automatically creates to the post...by the way it's embed src=abc not embed src=xyz/embed On Wed, Apr 14, 2010 at 9:25 AM, Joel Oliveira joel.olive...@gmail.com wrote: If you can get the url to the FLV from Cristi then you should be able to watch it in something like VLC. Even without flash installed (I do believe). - Joel On Wed, Apr 14, 2010 at 10:18 AM, john muhl johnm...@gmail.com wrote: On Wed, Apr 14, 2010 at 1:50 AM, Cristi Duma cristi.d...@aissac.ro wrote: @John if you mean like downloading .mov version from amazon or something similar... you can't. nor can i watch them in the first place since i do not have flash installed. Maybe in the future, but at the moment i'm only investing time in Radiantcasts. why spend the time to output flash? why not just output something that everyone can watch? ___ 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 ___ 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] [ANN] RadiantCasts episode 8
any chance of getting alternative non-flash versions of your screencasts? On Tue, Apr 13, 2010 at 10:51 AM, Cristi Duma cristi.d...@aissac.ro wrote: just released episode 8http://radiantcms.org/blog/archives/2010/04/13/radiantcasts-episode-8-radiant-chronicle-extension/, presenting Jason Garber's Chronicle Extension. I'm sure you already heard about it, and I must add it's really great. and if you missed ithttp://radiantcms.org/blog/archives/2010/04/06/radiantcasts-episode-7-radiant-styles-n-scripts-extension/, last week was Styles 'n Scripts Extension (SNS) with SNS-Minifier and SNS-SASS-Filter by Chris Parish. any feedback is greatly appreciated :) thanks, Cristi ___ 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] error on welcome
did you run `rake radiant:update` and `rake db:migrate` after updating to the master branch? On Mon, Apr 12, 2010 at 3:53 PM, Jan M.J. Storms j...@storms.org wrote: L.S., I have radiant gem 0.8.1 installed, made a fresh site and then followed the instructions on the download page under the heading The Bleeding Edge I see the login page, but after login, I see Application error Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html I wonder what I am missing or what i did wrong. Could you help me out? the log shows this: -- Processing Admin::WelcomeController#index (for 80.61.243.71 at 2010-04-12 22:21:20) [GET] Parameters: {action=index, controller=admin/welcome} NoMethodError (undefined method `locale' for #User:0x2304574): vendor/radiant/app/controllers/application_controller.rb:68:in `set_user_locale' vendor/radiant/vendor/plugins/haml/rails/./lib/sass/plugin/rails.rb: 19:in `process' thin (1.2.7) lib/thin/connection.rb:76:in `pre_process' thin (1.2.7) lib/thin/connection.rb:74:in `catch' thin (1.2.7) lib/thin/connection.rb:74:in `pre_process' thin (1.2.7) lib/thin/connection.rb:57:in `process' thin (1.2.7) lib/thin/connection.rb:42:in `receive_data' eventmachine (0.12.10) lib/eventmachine.rb:256:in `run_machine' eventmachine (0.12.10) lib/eventmachine.rb:256:in `run' thin (1.2.7) lib/thin/backends/base.rb:57:in `start' thin (1.2.7) lib/thin/server.rb:156:in `start' thin (1.2.7) lib/thin/controllers/controller.rb:80:in `start' thin (1.2.7) lib/thin/runner.rb:177:in `send' thin (1.2.7) lib/thin/runner.rb:177:in `run_command' thin (1.2.7) lib/thin/runner.rb:143:in `run!' thin (1.2.7) bin/thin:6 /usr/local/bin/thin:19:in `load' /usr/local/bin/thin:19 -- Jan ___ 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] Trailing slash for URLs
On Sat, Apr 10, 2010 at 11:07 AM, Christian Aust christian.a...@software-consultant.net wrote: Hi all, search engines consider URLs /some-page and /some-page/ to be two different pages (well, at least Google analytics does). I'd like to get rid of that. Would you expect Radiant to redirect clients to the trailing-slash-form of an URL, or should that be the duty of the web server above? Any comments are appreciated. Regards, if the issue is people manually typing or linking to your pages in inconsistent ways then i think sticking a rewrite rule in your server config is the easiest way. however if the issue is that your site template uses inconsistent urls then i'd fix that first. ___ 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] Where should I go from 0.7.2?
don't fix it if it ain't broken. On Mon, Apr 5, 2010 at 9:44 AM, Mohit Sindhwani t...@onghu.com wrote: On 4/4/2010 5:16 PM, Mohit Sindhwani wrote: Hello All, It's spring... and I'm getting ready to revamp an old site. Since the site has not been launched for a while, we have gone from a very sketchy prototype in 0.6.7 to a better prototype in 0.6.9. Since then, I have moved it to 0.7.1 and most of the things work fine there. However, as I said, it is spring! We're getting ready to launch the site in a few weeks, and I thought it would be a good time to reconsider if we should move to 0.8.0 or even 0.9.0 - that's where I would like a bit of input! The site uses the following extensions right now: * Admin Breadcrumbs * Aggregation * Blog Tags * Copy Move * Comments (patched by me to avoid rendering error due to wrong level of rendering) * CodeRay * Gallery * paperclipped * Reorder * Radiant Settings * RSpec gems (just so that it all runs) * TEDN (tedn, ezlang) - my own extension for a few minor things What I'm adding right now is: * share layouts * event calendar I think I will also need something that allows people to email a page to others (ar_mailer?) and something that lets them submit feedback to us about the site (I know there's one for this, just can't remember the name). Given these, I am wondering if the extensions all work happily together at a higher version. What do you recommend? Should I move to 0.8.0 or 0.9.0 - or should I just stay at 0.7.1? Any guidance for me? Thanks, Mohit. ___ 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] Where should I go from 0.7.2?
On Mon, Apr 5, 2010 at 12:11 PM, Mohit Sindhwani t...@onghu.com wrote: Thanks, I think we may start with 0.7.1/ 0.7.2 and then move to 0.8.0 or 0.9.0 during the maintenance. i think you're going to have a heck of a time with 0.7.2 :) ___ 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] Is settings extension ready for 0.9?
On Thu, Apr 1, 2010 at 4:10 AM, Xavier Guardiola xavier.guardi...@gmail.com wrote: Im trying to install settings extension to edge but after the installation+migration+update but when I try to access the settings tab the whole app freezes and pops up the following error: Rendered admin/users/_password_fields (19.4ms) Completed in 167ms (View: 145, DB: 4) | 200 OK [ http://localhost/admin/preferences/edit] Thu Apr 01 11:45:41 +0200 2010: Read error: #NoMethodError: undefined method `remove' for #Radiant::AdminUI::NavTab: 0x27f83dc /vendor/extensions/settings/settings_extension.rb:41:in `deactivate' /vendor/radiant/lib/radiant/extension.rb:86:in `deactivate' May this mean settings is still not ready for 0.9? most likely that is what it means. fortunately you don't really need it for anything. you can set any options from the rails console. cd radiant_project script/console Radiant::Config['defaults.page.filter'] = 'Markdown' ... Refer to the wiki for more available options. http://wiki.github.com/radiant/radiant/additional-configuration-options ___ 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] Something strange here
On Thu, Apr 1, 2010 at 3:14 PM, Arlen Walker arlen.wal...@gmail.com wrote: Was working with a development environment when suddenly the admin pages started looking funny, and I'm getting some javascript errors. The js errors are centered around Behavior, which comes from lowpro.js, and I'm noticing that the admin pages aren't loading it correctly. not sure what I screwed up, but when I try to go back and what does the error console have to say about the javascript errors? rebuild from fresh, I'm getting undefined method 'locale' after logging in. this part sounds like you were running an edge version and then updated to a newer edge version and didn't run `rake db:migrate` Any idea what I screwed up? Have Fun, Arlen -- In God we trust, all others must supply data ___ 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] Reorder Extension testing issues
On Tue, Mar 30, 2010 at 9:53 AM, Arlen Walker arlen.wal...@gmail.com wrote: BTW, am I right in assuming there isn't a command to test a specific extension, only one which tests all installed extensions at once? rake spec:extensions EXT=ext_name ___ 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] Newbie Issues with Radiant on Snow Leopard
gem uninstall rack gem install rack -v 1.0.1 On Fri, Mar 26, 2010 at 8:17 AM, Ilan Volow list...@clarux.com wrote: I'm trying out Radiant on my machine, OS X 10.6 Snow Leopard, using the version of Ruby that came with the OS, rails 2.3.5 and Radiant 0.8.1 (which was the version of Radiant installed when I did gem install radiant). I create a test site, I try running the rake production db:bootstrap command and I get the follow error rake aborted! can't activate rack (~ 1.0.0, runtime) for [], already activated rack-1.1.0 for [radiant-0.8.1] Can anyone shed some light on what's happening? ___ 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] Newbie Issues with Radiant on Snow Leopard
On Fri, Mar 26, 2010 at 2:31 PM, Gabe Koss gabe.k...@gmail.com wrote: I have fixed the problem without uninstalling rack. In /lib/action_controller.rb there is a line which specifies the raelck gem version. I was able to change this line to the correct rack version. which fixed my issue. sure you can always hack on the radiant source but that makes upgrades slightly more difficult as you have to keep reapplying your changes. unless you actually need a different version or rack for some other app i think the simplest solution is just to install the older version. That was actually on Ubuntu 9.04 but maybe it'll work on osx. .. Gabe On Mar 26, 2010 2:33 PM, john muhl johnm...@gmail.com wrote: gem uninstall rack gem install rack -v 1.0.1 On Fri, Mar 26, 2010 at 8:17 AM, Ilan Volow list...@clarux.com wrote: I'm trying out Radiant on my machine, OS X 10.6 Snow Leopard, using the version of Ruby that cam... ___ 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] RC to Edge?
On Tue, Mar 23, 2010 at 4:06 PM, Alexis Masters alexismast...@gmail.com wrote: I thought we had upgraded to Radiant Edge for Womensgivingtree.org, but now suspect the guys installed Radiant RC instead. How do you upgrade safely on a site that is up and running? What is the correct shell command to accomplish the upgrade? All help gratefully accepted :-) i hope you're not going to upgrade the actual running application... the commands are: rm -r vendor/radiant # if you have radiant vendor'd already rake radiant:freeze:edge rake radiant:update rake db:migrate # you may need to provide your environment here ___ 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 RC1 suitable for production use?
if you want to use 0.9 i'd recommend using the current master branch as the RC1 release is far, far behind the current work. personally i'm still starting new projects with 0.8.1 mostly because these are sites for clients and being profitable means i don't want to be tracking a moving target; not because 0.9 is unstable or anything. On Tue, Mar 16, 2010 at 4:54 AM, Charles Roper reac...@charlesroper.co.uk wrote: I'm about to start a new Radiant site and was wondering whether I should go with 0.9RC1 or 0.8.1? In the opinion of the community, is RC1 stable enough for production use? Cheers, Charles ___ 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] Problem with MarkDownFilter
On Mon, Mar 15, 2010 at 6:31 PM, Johannes Fritsch nos...@jfritsch.de wrote: Hi! I tested this on a brand new iMac (delivered today) with Snow Leopard: Rails was installed with Aptana RadRails. any version of rails you have installed will be ignored by radiant unless you've hacked it. otherwise the version radiant has in vendor will be used. so that's not the problem. From there on i did: sudo gem install radiant sudo gem install rake --version 1.0.1 // Or similar, can not remember which one radiant required radiant --database=sqlite3 myTest cd myTest % rake radiant:freeze:edge % rake radiant:update % rake db:migrate (According to install notes for bleeding edge) % rake db:bootstrap - Leaving all default, i've choosen empty template Everything works fine except for MarkDownFilter. When i put that on a page i get the following error: NameError in SiteController#show_page undefined local variable or method `auto_ids' for #MarkdownFilter:0x10314f218 auto_ids is from kramdown. Is the trunk broken or is it my fault and i'm doing something wrong? Can anyone reproduce this? i cannot reproduce it here following the exact steps you've listed. do you get any other error messages in your logs? and could you provide more information about your environment; windows, linux, mac; ruby version; etc. that way i can have a go at reproducing it in an environment that more closely matches the one you're using. ___ 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 MarkDownFilter
could you try it again with the current master branch. i committed a change which at least in my testing seems to have cleared up the issue. sorry for the inconvenience. On Mon, Mar 15, 2010 at 6:31 PM, Johannes Fritsch nos...@jfritsch.de wrote: Hi! I tested this on a brand new iMac (delivered today) with Snow Leopard: Rails was installed with Aptana RadRails. From there on i did: sudo gem install radiant sudo gem install rake --version 1.0.1 // Or similar, can not remember which one radiant required radiant --database=sqlite3 myTest cd myTest % rake radiant:freeze:edge % rake radiant:update % rake db:migrate (According to install notes for bleeding edge) % rake db:bootstrap - Leaving all default, i've choosen empty template Everything works fine except for MarkDownFilter. When i put that on a page i get the following error: NameError in SiteController#show_page undefined local variable or method `auto_ids' for #MarkdownFilter:0x10314f218 Is the trunk broken or is it my fault and i'm doing something wrong? Can anyone reproduce this? Best regards Johannes Fritsch ___ 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] how do I add git submodule for reader extension
i'm not 100% but it may just not be updated to work with 0.9 yet. On Sun, Mar 7, 2010 at 11:36 PM, Daniel O'Connell d...@mac.com wrote: Im able to install and run migrate/update tasks. But when I try to create a reader I get this: Connection refused - connect(2) RAILS_ROOT: /Users/dev/Sites/gla1 Application Trace | Framework Trace | Full Trace /usr/local/lib/ruby/1.8/net/smtp.rb:551:in `initialize' /usr/local/lib/ruby/1.8/net/smtp.rb:551:in `open' /usr/local/lib/ruby/1.8/net/smtp.rb:551:in `do_start' /usr/local/lib/ruby/1.8/timeout.rb:62:in `timeout' /usr/local/lib/ruby/1.8/timeout.rb:93:in `timeout' /usr/local/lib/ruby/1.8/net/smtp.rb:551:in `do_start' /usr/local/lib/ruby/1.8/net/smtp.rb:525:in `start' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionmailer/lib/action_mailer/base.rb:682:in `perform_delivery_smtp' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionmailer/lib/action_mailer/base.rb:523:in `__send__' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionmailer/lib/action_mailer/base.rb:523:in `deliver!' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionmailer/lib/action_mailer/base.rb:395:in `method_missing' /Users/dev/Sites/gla1/vendor/extensions/reader/app/models/message.rb:93:in `deliver_to' /Users/dev/Sites/gla1/vendor/extensions/reader/app/models/reader.rb:75:in `send_functional_message' /Users/dev/Sites/gla1/vendor/extensions/reader/app/models/reader.rb:67:in `send_invitation_message' /Users/dev/Sites/gla1/vendor/extensions/reader/app/controllers/admin/readers_controller.rb:11:in `create' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `send' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/base.rb:1331:in `perform_action_without_filters' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/filters.rb:617:in `call_filters' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/local/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/rescue.rb:160:in `perform_action_without_flash' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/flash.rb:146:in `perform_action' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `send' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `process_without_filters' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `sass_old_process' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/plugins/haml/lib/sass/plugin/rails.rb:19:in `process' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/base.rb:391:in `process' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/base.rb:386:in `call' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/routing/route_set.rb:437:in `call' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:87:in `dispatch' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:121:in `_call' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:130:in `build_middleware_stack' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/activerecord/lib/active_record/query_cache.rb:29:in `call' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/activerecord/lib/active_record/query_cache.rb:29:in `call' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/activerecord/lib/active_record/query_cache.rb:9:in `cache' /usr/local/lib/ruby/gems/1.8/gems/radiant-0.9.0/vendor/rails/activerecord/lib/active_record/query_cache.rb:28:in `call'
Re: [Radiant] Radiant Upgrade from 0.5.2 to 0.8.1 Please help
i don't think you'll be able to upgrade in one easy step. i'd recommend taking small steps to get to 0.8.1; such as 0.5.2 = 0.6.0 = 0.6.4 = 0.6.9 = 0.7.1 = 0.8.1 On Fri, Feb 19, 2010 at 11:12 AM, Hugo Villero hvill...@gmail.com wrote: Hi There, I know this could be a recall situation but, I have to upgrade a my site from Radiant 0.5.2 to Radiant 0.8.1, I was following the docs but that doesn't work, I looks like the current tables like pages on others have to change in some fields and contents. Is there someone with a very good document about that some URLs or experience doing that? Please help me and let me know, Hvillero ___ 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] wiki vandalism
http://wiki.github.com/radiant/radiant/radiant-users has pretty much been ruined by a spammer. after bringing it to the attention of github they banned the user but all the spam they left is still there. if you have a valid listing on that page perhaps you could move it to another list above the current one then when time permits someone could go through the remainder and get rid of the spam. the github support guy said the page itself is probably going to be a hotspot for spam so if anyone has any ideas on someway to reduce the chance of future spam there i'm all ears. maybe just changing to a more complicated style (like the radiant pros page) would make it easier to spot. ___ 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 install concurrent_draft extension
are you using the 0.7.1 tag or the master branch? if the latter you might try switching to the former and running the migrate/update commands by hand. On Thu, Feb 11, 2010 at 3:32 PM, Stan Rawrysz smoo...@gmail.com wrote: I'm trying to install the concurrent_draft extension, but I'm guessing I'm missing a plugin or something. Running Radiant 0.7.1 Rails 2.3.5 (installed through macports) OS X 10.6 PostgreSQL Error while installing: $ script/extension install concurrent_draft Initialized empty Git repository in /private/var/folders/DM/DMD0iVG4Fb0a50Z09mRvnU+++TI/-Tmp-/concurrent_draft/.git/ remote: Counting objects: 506, done. remote: Compressing objects: 100% (279/279), done. remote: Total 506 (delta 233), reused 329 (delta 138) Receiving objects: 100% (506/506), 71.54 KiB, done. Resolving deltas: 100% (233/233), done. rake aborted! undefined method `select_hour' for class `ActionView::Helpers::DateTimeSelector' (See full trace by running task with --trace) rake aborted! undefined method `select_hour' for class `ActionView::Helpers::DateTimeSelector' (See full trace by running task with --trace) - Error at runtime: $ script/server = Booting Mongrel (use 'script/server webrick' to force WEBrick) = Rails 2.1.2 application starting on http://0.0.0.0:3000 = Call with -d to detach = Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... Exiting /opt/local/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activesupport/lib/active_support/core_ext/module/aliasing.rb:31:in `alias_method': undefined method `select_hour' for class `ActionView::Helpers::DateTimeSelector' (NameError) Did a bit of searching for this error and found a thread about rails-unobtrusive-date-picker, but I think that's a red herring. http://code.google.com/p/rails-unobtrusive-date-picker/issues/detail?id=17 If anyone can help, that would be awesome. Stan ___ 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 install concurrent_draft extension
i meant are you running the 0.7.1 tag or the master branch of the concurrent_draft extension. if you used script/extension install chances are you're on master. try this: cd vendor/extensions/concurrent_draft git checkout 0.7.1 cd ../../.. rake radiant:extensions:concurrent_draft:migrate rake radiant:extensions:concurrent_draft:update On Thu, Feb 11, 2010 at 4:47 PM, Stan Rawrysz smoo...@gmail.com wrote: I have inherited the project from another developer. I'm not sure I understand your question, either. I'm pretty sure it was created from the gem. And a correction below, it is not running 2.3.5, it's actually 2.1.2 like it's supposed to. Thanks, Stan On Thu, Feb 11, 2010 at 1:46 PM, john muhl johnm...@gmail.com wrote: are you using the 0.7.1 tag or the master branch? if the latter you might try switching to the former and running the migrate/update commands by hand. On Thu, Feb 11, 2010 at 3:32 PM, Stan Rawrysz smoo...@gmail.com wrote: I'm trying to install the concurrent_draft extension, but I'm guessing I'm missing a plugin or something. Running Radiant 0.7.1 Rails 2.3.5 (installed through macports) OS X 10.6 PostgreSQL Error while installing: $ script/extension install concurrent_draft Initialized empty Git repository in /private/var/folders/DM/DMD0iVG4Fb0a50Z09mRvnU+++TI/-Tmp-/concurrent_draft/.git/ remote: Counting objects: 506, done. remote: Compressing objects: 100% (279/279), done. remote: Total 506 (delta 233), reused 329 (delta 138) Receiving objects: 100% (506/506), 71.54 KiB, done. Resolving deltas: 100% (233/233), done. rake aborted! undefined method `select_hour' for class `ActionView::Helpers::DateTimeSelector' (See full trace by running task with --trace) rake aborted! undefined method `select_hour' for class `ActionView::Helpers::DateTimeSelector' (See full trace by running task with --trace) - Error at runtime: $ script/server = Booting Mongrel (use 'script/server webrick' to force WEBrick) = Rails 2.1.2 application starting on http://0.0.0.0:3000 = Call with -d to detach = Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... Exiting /opt/local/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/activesupport/lib/active_support/core_ext/module/aliasing.rb:31:in `alias_method': undefined method `select_hour' for class `ActionView::Helpers::DateTimeSelector' (NameError) Did a bit of searching for this error and found a thread about rails-unobtrusive-date-picker, but I think that's a red herring. http://code.google.com/p/rails-unobtrusive-date-picker/issues/detail?id=17 If anyone can help, that would be awesome. Stan ___ 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] restart server on site5
http://wiki.github.com/radiant/radiant/installing-on-site5 says they support passenger so if you're using that then `touch tmp/restart.txt` should do the trick. if not you'll have to figure out what application server you are using before anyone can tell you how to restart it. On Wed, Feb 3, 2010 at 11:15 AM, Ming Pan fallspin...@gmail.com wrote: Hi, I've been using the web hosting service provided by site5.com, and it seems to be working well with radiant cms. But I've never figured out the right way to restart server, which is often required while adding new extensions or changing environment.rb. I searched around and tried many things like to touch public/dispatch.fcgi, touch tmp/restart.txt, kill ruby process, ..., but never knew which one worked or not or worked properly. Anyone knows about that? And how to determine the server has been restarted properly? For example, anything to look for in the log file? I'm asking this question because I'm having trouble with the mailer extension and I suspect that I'm not restarting the server properly. Thanks. ming ___ 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] Radiant Installation Failing Using Ruby 1.9.1/1.8.7
On Wed, Feb 3, 2010 at 4:18 PM, Conrad Taylor conra...@gmail.com wrote: On Wed, Feb 3, 2010 at 4:31 PM, Jake Skedgell jjskedg...@gmail.com wrote: This 0.8.2 bug fix release would be very welcome. There is also a problem with the bundled Rails that conflicts with the new Rack 1.1.0. I don't know how easily that could be fixed. It's not really a Radiant bug. Any idea when we can expect 0.9 to be finished? Jake Skedgell Does anyone know which version of Rails is being used with the current github version of Radiant? http://github.com/radiant/radiant/tree/master/vendor/rails/ ___ 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 installing mailer extension
On Mon, Feb 1, 2010 at 2:48 PM, Ming Pan fallspin...@gmail.com wrote: Dear List, I was trying to install the mailer extension. First I tried ./script/extension install mailer, and I got the following errors: + Initialized empty Git repository in /tmp/mailer/.git/ remote: Counting objects: 184, done. remote: Compressing objects: 100% (168/168), done. remote: Total 184 (delta 72), reused 25 (delta 1) Receiving objects: 100% (184/184), 35.66 KiB, done. Resolving deltas: 100% (72/72), done. rake aborted! Mysql::Error: Table 'lovebaob_radiantdev.extension_meta' doesn't exist: SELECT schema_version FROM extension_meta WHERE name = 'Mailer' (See full trace by running task with --trace) rake aborted! Don't know how to build task 'radiant:extensions:mailer:update' (See full trace by running task with --trace) + Then I tried to do it manually, and the errors are basically the same: + (in /home/lovebaob/radapp) rake aborted! Mysql::Error: Table 'lovebaob_radiantdev.extension_meta' doesn't exist: SELECT schema_version FROM extension_meta WHERE name = 'Mailer' (See full trace by running task with --trace) + I checked my databases and the table extension_meta only exists in my production database and not in the development database. Any idea how I should fix the problem? run the install command against your production database like so `script/extension install mailer RAILS_ENV=production` ___ 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 installing mailer extension
there is no update task for mailer which is why you see the error. just to be safe `script/extension install` tries to run both migrate and update regardless of if they exist or not. so when installing a Don't know how to build task 'XYZ' message is harmless; it just means that task does not exist. you need to restart your application server (passenger, mongrel, thin, unicorn etc. etc.) after installing extensions. On Mon, Feb 1, 2010 at 3:02 PM, Ming Pan fallspin...@gmail.com wrote: Thanks so much John! Now I went through the migrate step successfully, but it gave errors on the update step: (in /home/lovebaob/radapp) rake aborted! Don't know how to build task 'radiant:extensions:mailer:update' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1704:in `[]' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2026:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1999:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1977:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1974:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 Is this update step required by the mailer extension? I reloaded my admin/extensions page and mailer is not there. ming ___ 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 installing mailer extension
On Mon, Feb 1, 2010 at 3:14 PM, Jim Gay j...@saturnflyer.com wrote: If you've got specs for your changes to script/extension (which skips the migrate and update tasks if they don't exist) go ahead and push them into the master branch. I meant to take a look at your work on that a long time ago, but haven't gotten around to it. i'm pretty sure i abandoned that before i got it to do anything useful like checking for tasks before running them. in the time since the installer was added it seems this comes up rarely enough that complicating things is probably not worth it. perhaps something in the creating extensions part of the wiki that informs authors their extension will spit up errors if they don't provide (at least empty) tasks would help. now that i think about it again though the simplest solution seems like it would be to stub out rake tasks like This extension does not have a migrate/update task upon extension creation. at least that way authors who forget about it wouldn't these have error messages. I'm personally in favor of a single install task. and a single uninstall task! :) On Mon, Feb 1, 2010 at 4:02 PM, Ming Pan fallspin...@gmail.com wrote: Thanks so much John! Now I went through the migrate step successfully, but it gave errors on the update step: (in /home/lovebaob/radapp) rake aborted! Don't know how to build task 'radiant:extensions:mailer:update' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1704:in `[]' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2026:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1999:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1977:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1974:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 Is this update step required by the mailer extension? I reloaded my admin/extensions page and mailer is not there. ming ___ 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 -- Jim Gay Saturn Flyer LLC j...@saturnflyer.com http://www.saturnflyer.com 571-403-0338 ___ 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] next 15
On Mon, Feb 1, 2010 at 4:05 PM, Steven Southard ste...@stevensouthard.com wrote: I've kind of rethought this and I think the url parameter idea might cause problems with search engines. If the resulting link creates a url like ...?offset=15 I'm not sure search engines will ever find this content. i'm not an seo expert by any stretch but i don't think it matters. presumably all the items your paginating also reside on individual pages in your sitemap so even if some search engine spider skips a page like /items?page=4 it should still see the /items/19 page and index that. Is Paginate what John used for Extension Registry? looks like it http://github.com/radiant/radiant-extension-registry/blob/master/.gitmodules On Jan 5, 2010, at 3:29 PM, Steven Southard wrote: I've never understood the purpose of that extension, that's what it does? The offset with parameters was easy and didn't require any additional pages or anything. Thank you both for your help. Steven On Jan 5, 2010, at 3:07 PM, john muhl wrote: i've never used it personally (though i've had good results with other extensions from aissac) but you might try the paginate extension: http://github.com/Aissac/radiant-paginate-extension On Tue, Jan 5, 2010 at 2:59 PM, Steven Southard ste...@stevensouthard.com wrote: Okay great, very smart. Maybe just use parameters in the url to determine the offset? On Jan 5, 2010, at 2:53 PM, Sean Cribbs wrote: Steven, You should be able to add an offset attribute to the r:children:each tag. But yes, you'll likely need to create another page, or a virtual page that can deal with pagination of those aggregated children. Sean On 1/5/10 3:41 PM, Steven Southard wrote: When using a tag liker:aggregate urls=/articles/; / other_articles/;r:children:each limit=15 order=desc is there a way to ask for the next 15? Do I need to make another archive page to link to for that? Steven ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant 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 Tue, Jan 26, 2010 at 8:32 AM, Josh French j...@digitalpulp.com wrote: 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. I'm actually at a loss as to why it would appear when vendored if you're not explicitly loading that subclass. Radiant doesn't do any pre-loading of filter subclasses in the way that it automatically seeks out and loads Page subclasses. If you look at the textile and markdown extensions that ship within core, you'll see that both of them explicitly load the filter subclass within their #activate methods. It'll be safer to follow their example. huh? so you mean this: --- require 'kramdown' class KramdownFilterExtension Radiant::Extension version 1.0 description kramdown is a fast pure-Ruby Markdown converter. url http://kramdown.rubyforge.org/index.html; def activate KramdownFilter end end --- is not explicitly enough? i can't see how that is any different to what the markdown or textile extensions do but i guess it's not. could someone explain how to make it explicit enough for the gem loader? textile_filter --- class TextileFilterExtension Radiant::Extension version 1.0 description Allows you to compose page parts or snippets using the Textile text filter. url http://textism.com/tools/textile/; def activate TextileFilter Page.send :include, TextileTags end end --- markdown_filter --- class MarkdownFilterExtension Radiant::Extension version 1.0 description Allows you to compose page parts or snippets using the Markdown or SmartyPants text filters. url http://daringfireball.net/projects/markdown/; def activate MarkdownFilter SmartyPantsFilter Page.send :include, MarkdownTags end end --- ___ 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
just noticed that extracting the textile_filter extension out into a gem also fails in the exact same ways that i've run into... On Tue, Jan 26, 2010 at 9:13 AM, john muhl johnm...@gmail.com wrote: On Tue, Jan 26, 2010 at 8:32 AM, Josh French j...@digitalpulp.com wrote: 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. I'm actually at a loss as to why it would appear when vendored if you're not explicitly loading that subclass. Radiant doesn't do any pre-loading of filter subclasses in the way that it automatically seeks out and loads Page subclasses. If you look at the textile and markdown extensions that ship within core, you'll see that both of them explicitly load the filter subclass within their #activate methods. It'll be safer to follow their example. or are you talking about this not being explicit enough? --- class KramdownFilter TextFilter description_file File.dirname(__FILE__) + /../markdown.html def filter(text) Kramdown::Document.new(RubyPants.new(text).to_html).to_html end end --- textile_filter --- class TextileFilter TextFilter description_file File.dirname(__FILE__) + /../textile.html def filter(text) RedCloth.new(text).to_html end end --- markdown_filter --- class MarkdownFilter TextFilter description_file File.dirname(__FILE__) + /../markdown.html def filter(text) if defined? RDiscount RDiscount.new(text, :smart).to_html else RubyPants.new(BlueCloth.new(text).to_html).to_html end end end --- again looks the same to me. ___ 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
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] More 'Rails app to Radiant extension' questions
On Tue, Jan 12, 2010 at 9:22 AM, Asfand Yar Qazi ayq...@gmail.com wrote: 2010/1/11 banane ban...@gmail.com: Put the routes.rb stuff in [yourapplication]_extension.rb You can extend ActiveRecord, just like in Rails. Rails is embedded in Radiant, so it works pretty much the same. Put the testing stuff in /rspec, test as usual. And what about selenium on rails tests? That is another stickler. Another question: My app currently uses several plugins it needs. If I make my app an extension, where do those plugins go? If I simply move them to the Radiant app, won't that make upgrading difficult? if your rails app has vendor/plugins/xyz then your extension would have vendor/plugins/xyz. for example: /rails_app/vendor/plugins/xyz /radiant_app/vendor/extensions/your_extension/vendor/plugins/xyz ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] next 15
i've never used it personally (though i've had good results with other extensions from aissac) but you might try the paginate extension: http://github.com/Aissac/radiant-paginate-extension On Tue, Jan 5, 2010 at 2:59 PM, Steven Southard ste...@stevensouthard.com wrote: Okay great, very smart. Maybe just use parameters in the url to determine the offset? On Jan 5, 2010, at 2:53 PM, Sean Cribbs wrote: Steven, You should be able to add an offset attribute to the r:children:each tag. But yes, you'll likely need to create another page, or a virtual page that can deal with pagination of those aggregated children. Sean On 1/5/10 3:41 PM, Steven Southard wrote: When using a tag liker:aggregate urls=/articles/; / other_articles/;r:children:each limit=15 order=desc is there a way to ask for the next 15? Do I need to make another archive page to link to for that? Steven ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Port number.....
radiant does not set any port number. it is set by your application server (mongrel, thin, unicorn etc.). On Mon, Jan 4, 2010 at 2:29 PM, David Passmore d...@psu.edu wrote: Installation of Radiant sets port 8080. How do I change this port number? ___ 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] radiant::cache, nginx and :use_x_accel_redirect
today i had go at upgrading a 0.6.9 app (which used a very old patch to make x-accel-redirect work with radiant's ResponseCache) to 0.8.1 and ran into (what i'm guessing is) an issue with radiant::cache, :use_x_accel_redirect option and firefox. under the following conditions firefox will receive a response with an application/octet-stream content-type header and prompts me to save an untyped data file. 1. rm -rf tmp/cache/*/* 2. load a page in firefox 3. verify entity and meta cache entries were created 4. reload the page - 304 not modified response - see the custom X-Accel-Redirect header i set in nginx - see all the headers set by radiant 5. edit and save the page that has been cached 6. verify that new entity and meta cache entries were created 7. reload the page and get prompted to save untyped data (i'm guessing that step 5 could be replaced by waiting five minutes for the cache to expire) i've only been able to reproduce this in firefox (versions 1.0.7, 1.5.0.7, 2.0.0.20, 3.0.12 and 3.5.6) which seems to be the only browser (and i tested in about 15 different versions of various browsers) that gets a 304 response when clicking the reload button. has anyone else experienced similar behavior or have any advice on what i'm doing wrong in my configuration? the relavent bits are: environment.rb config.middleware.use ::Radiant::Cache, :use_x_accel_redirect = '/entity' nginx.conf location /entity { internal; root /radiant/tmp/cache; } ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ 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] How to improve site performance?
oh and i'd think 300-400ms or less spent inside the rails process would be sufficient for all but the most performance critical applications since your web server should be able to serve the rest of your page (static assets, css, js) in less than 100ms On Mon, Dec 28, 2009 at 6:49 PM, john muhl johnm...@gmail.com wrote: some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ 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] How to improve site performance?
On Mon, Dec 28, 2009 at 7:13 PM, Rob Levin roblevinten...@gmail.com wrote: change the page caching time to a much larger value compared to the default 5 minutes if your pages can manage it. Yes, I'm looking in to this. I'm almost positive we're just using the default. I agree that this may help a LOT! Does someone have a working example of setting: ResponseCache.defaults[:expire_time] or whatever? That would be very helpful. http://groups.google.com/group/radiantcms/msg/01ac040dbcf76479 John Mohit: make sure you are not serving css and/or js from radiant I have my styles and js in RADIANT_ROOT/public/stylesheet /javascripts respectively. Is that correct? It's my understanding that Apache will serve anything under /public right? that's right page parts Well we are using layouts, snippets, parts, etc., pretty heavily. Is this specific to page parts or are snippets, layouts, etc., also hot spots? they require additional database access. however if your database is properly tuned it's generally not much of an issue. it's just something i've noticed on the few apps i track with new relic rpm; in nearly all of them PagePart#find is the most time consuming transaction except in apps that use paperclipped and in that case Asset#find is the slowest. Here's the live site: http://www.snaplogic.com/ the x-runtime header (for the homepage) says 457ms (which is a pretty insignificant part of your total response time) is spent in the rails process so you're likely going to get much more bang for your buck by starting with generic optimizations rather that digging too deeply into radiant (e.g. reducing use of snippets or page parts). a tool like the yslow addon for firefox might help get you started: https://addons.mozilla.org/en-US/firefox/addon/5369. Thanks for the great help all! On Mon, Dec 28, 2009 at 4:54 PM, john muhl johnm...@gmail.com wrote: oh and i'd think 300-400ms or less spent inside the rails process would be sufficient for all but the most performance critical applications since your web server should be able to serve the rest of your page (static assets, css, js) in less than 100ms On Mon, Dec 28, 2009 at 6:49 PM, john muhl johnm...@gmail.com wrote: some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ 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] Deployment database merging
heroku has a tool called taps that i use for this purpose; it's not tied to the heroku service at all so you can use it to push/pull databases from any where you like. http://docs.heroku.com/taps http://adamblog.heroku.com/past/2009/2/11/taps_for_easy_database_transfers/ On Sun, Dec 13, 2009 at 3:52 AM, Konstantin Antipin antipin.konstan...@gmail.com wrote: Hi everybody, I am developing a blog for a customer using Radiant 0.8.1 What is the usual way of deploying radiant to the production server? Since lot's of configuration is stored in the database, I need to overwrite db on the server with my development db (with capistrano it is not a problem). But this will work only if I am the only one who updates the website. And what if customer in a meanwhile has published new post? I need to merge databases somehow. There was a similar question some time ago ( http://www.ruby-forum.com/topic/167040 ), but there was no real conclusion... So, how do _you_ deploy your radiant website? How do you solve issue with database merge? This must have some simple answer, but I can't see one... my best, Konstantin PS It would be absolutely awesome if you share your capistrano recipe in case you use it ;) ___ 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] Recursion error: already rendering the part
there is nothing wrong with that snippet. so maybe you have already entered the amazon_link part before you call the snippet; maybe in another snippet or a layout. On Thu, Nov 19, 2009 at 2:35 PM, Dmitry Belitsky dmitry.belit...@gmail.com wrote: Hey guys, take a look at http://pastie.org/706339 i get error: StandardTags::TagError in SiteController#show_page Recursion error: already rendering the `amazon_link' part. Can you help me fix it? Thanks! -- With optimism, Dmitry Belitsky http://belitsky.info ___ 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] Recursion error: already rendering the part
are you by any chance running radiant 0.9rc1 (or a recent master branch)? on a fresh 0.8.1 the snippet works as expected; on master i see the behavior you describe. the test case can be narrowed to: r:children:each r:content part=a/ r:content part=a/ /r:children:each On Thu, Nov 19, 2009 at 3:15 PM, Dmitry Belitsky dmitry.belit...@gmail.com wrote: Thanks for reply, but i can't find any mention of this part in other places. Only here. If i used this snipped on home page - it works, if i used it in other page: Recordings - here i want to show list of children, which have parts which i define in Stereotype: - Rec1 - Rec2 - Rec3 If i remove one of r:content part='amazon_link' / - this page works, if i left both - i get this: Recursion error: already rendering the `amazon_link' part. Any suggestions? Thanks. P.S. I used Paperclipped and Stereotype plugins if this matters. On Nov 19, 2009, at 10:43 PM, john muhl wrote: there is nothing wrong with that snippet. so maybe you have already entered the amazon_link part before you call the snippet; maybe in another snippet or a layout. On Thu, Nov 19, 2009 at 2:35 PM, Dmitry Belitsky dmitry.belit...@gmail.com wrote: Hey guys, take a look at http://pastie.org/706339 i get error: StandardTags::TagError in SiteController#show_page Recursion error: already rendering the `amazon_link' part. Can you help me fix it? -- With optimism, Dmitry Belitsky http://belitsky.info ___ 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] Pages, Snippets and Layouts Coordination
On Fri, Nov 13, 2009 at 4:45 PM, Jason Broom jbroo...@gmail.com wrote: Would I be better off skipping CSS as a Page, and just link rel=stylesheet somewhere in the metaverse? that's my preferred way; not to mention spending a database lookup (actually more than one) and having your css expire from the cache every five minutes aren't what you'd call performant. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] dreamhost
On Mon, Nov 9, 2009 at 10:36 AM, Brian Wolf brw...@gmail.com wrote: I was wondering if you might update your dreamhost install directions, as radiant is an installed gem. on my dreamhost ps the system radiant gem is version 0.6.9 which is more than a year out of date and probably won't work with lots of extensions; certainly new extensions are not targeting 0.6.x and even old extensions that get updates have probably dropped 0.6.x support by now. Do I still need to install my own gems? if you want to run a current version of radiant and/or have any control over the environment yes you should install your own gems. These configuration issues seem to get in the way of my eval. then ignore these configuration issues and do as was suggested by others and do your evaluation on your local computer. trying to evaluate anything on dreamhost's notoriously crappy platform seems like an unnecessary pain to put yourself through. if you must do the evaluation on a remote server have a look at http://heroku.com/ you can get started for free and their platform is actually built to run ruby applications. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] page_attachment error
does this help? http://groups.google.com/group/radiantcms/msg/aedda395081a30c9 On Thu, Nov 5, 2009 at 1:47 PM, Jeff Randall jrand...@iaak.net wrote: I am running Rails 2.3.4, Radiant 0.8.1 on Ubuntu 8.0.4 It seems the installation of page _attachments is successful per http://wiki.github.com/radiant/radiant/page-attachments-extension . In the admin I can see Attachments area when I am working with a page but nothing happens when I click the + icon. Firebug is telling there is an error with the JS. Event.addBehavior is not a function '#attachments:click': function(event) {\n Any ideas? ___ 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] iterating over children of children in order of creation
take a look at the aggregation extension: http://github.com/radiant/radiant-aggregation-extension On Thu, Nov 5, 2009 at 7:45 PM, Joe Van Dyk j...@pinkpucker.net wrote: Hello, I've got the following structure: /publications /publications/boats/page1 /publications/boats/page2 /publications/boats/page3 /publications/cars/page1 /publications/cars/page2 etc I want to make a RSS feed that lists the most recent pages from the publications directory. when I do something like: r:find /publications / r:children:each by=created_at order=desc limit=20 ... /r:children:each It seems to order the pages by whenever the top-level boats and cars pages themselves were updated, not by the most recent updated children of the cars and boats pages. Again, if /publications/cars/page5 was added, I'd want that to be at the top of the rss feed. Ideas on how to do that? -- Joe Van Dyk http://fixieconsulting.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
[Radiant] latest (0.8.x compatible) page_attachments woes
it seems 8105853c35071712ab130e668d14e813a95f5ebe broke at least the saving of file titles/descriptions and causes PAGE_ATTACHMENTS_SIZES hash to be ignored. reverting that commit makes everything working again. anyone else seeing similar behavior on the 0.8.1 branch? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Extension page_attachments no reaction after click
the master branch of page_attachments does not work with 0.8.x anymore you'll need to checkout the 0.8.1 branch. git clone git://github.com/... vendor/extensions/page_attachments # checkout the 0.8.1 branch cd vendor/extension/page_attachments git checkout origin/radiant-0.8.1 cd ../../.. rake radiant:extensions:page_attachments:migrate rake radiant:extensions:page_attachments:update On Thu, Oct 29, 2009 at 1:18 PM, Boris Raeschler boris.raesch...@googlemail.com wrote: Hello, I´m using a fresh radiant copy 0.8.1 and the latest version of page_attachments. Installation of radiant and the plugin works like a charm. I'm using this steps for installation git clone git://github.com/radiant/radiant-page-attachments-extension.git vendor/extensions/page_attachments rake radiant:extensions:page_attachments:migrate rake radiant:extensions:page_attachments:update But here´s my problem. I would like to upload a attachment to a page. In admin/page/edit I see the green + button. But clicking the button has no result. I didn´nt see the upload form or an other button? The Database Table and Javascript file (page_attachments) are present?? What did I wrong? Who can help? Best regards Boris ___ 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] Troubles with mailer extension
On Mon, Oct 26, 2009 at 9:37 AM, Travis D. Warlick, Jr. warli...@operissystems.com wrote: You should be using the following tag syntax for the form fields: r:mailer:text name=name / See the Usage section here: http://github.com/radiant/radiant-mailer-extension not true. everything inside r:mailer:form is already in the r:mailer... namespace so r:mailer:form r:mailer:text... is exactly the same as r:mailer:form r:text... (this is pretty much true of all radius tags) On Oct 26, 2009, at 9:26 AM, María Paula Mariani wrote: I'm trying to build a contact form using the Mailer extension. I've followed step by step the documentation, but I can't find the way. When clicking at Submit form, it do not deliver the message and forward to this path /pages/84/mail#mailer that url suggest you haven't set `Radiant::Config['mailer.post_to_page?'] = true`. see http://wiki.github.com/radiant/radiant/mailer-extension i also see that you're trying to send to an @gmail.com address so i'm guessing that you're using the gmail smtp server; if that's the case and you're running ruby 1.8.6 you'll need to install the action_mailer_tls rails plugin. if none of that helps could you provide more details on your setup. action mailer config, smtp provider, ruby version, radiant version etc. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Troubles with mailer extension
i also see that you're trying to send to an @gmail.com address so i'm guessing that you're using the gmail smtp server; if that's the case and you're running ruby 1.8.6 you'll need to install the action_mailer_tls rails plugin. I've installed the action_mailer_tls gem, should I include it this way before the Action Mailer SMTP configuration require 'smtp_tls' or it is not needed? from what i understand it's not needed. see the first comment here: http://apidock.com/rails/ActionMailer/Base ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Stylesheet and articles not working
On Thu, Oct 15, 2009 at 5:42 PM, Bhavin Patel mindtra...@gmail.com wrote: HiI am new to raidant cms. I posted my query but was not able to get a proper solution. more likely you ignored the answer. http://groups.google.com/group/radiantcms/msg/2f4c94f8ee3b7b9d? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: Git Confusion - thread detour from [Radiant] [ANN] Radiant 0.9.0 RC1
On Mon, Oct 12, 2009 at 3:02 PM, Nate Turnage pixeln...@gmail.com wrote: On Mon, Oct 12, 2009 at 2:45 PM, Dayne Broderson da...@gina.alaska.eduwrote: [dbrod...@beef ~]$ gem environment ... [dbrod...@beef ~]$ /usr/local/lib/ruby/gems/1.8/gems/radiant-0. radiant-0.6.9/ radiant-0.7.0/ radiant-0.7.1/ radiant-0.8.1/ [dbrod...@beef ~]$ /usr/local//ib/ruby/gems/1.8/gems/radiant-0.7.1/bin/radiant That's pretty easy? :^O I guess it's not that difficult, but I could have sworn there was an easier way. Something like this: radiant -v=0.7.1 --database [mysql] project That of course doesn't work, but I thought there was something easy like that. I could be wrong, probably am. i've found the following to be pretty easy to use once it's setup. - clone the latest radiant source to somewhere in your home directory; i use ~/.radiant git clone git://github.com/radiant/radiant.git ~/.radiant - add aliases to your ~/.bashrc file (or ~/.profile or whatever) such as: alias radiant-0.6.8=PWD=`pwd` cd ~/.radiant git checkout -q 0.6.8 cd $PWD ~/.radiant/bin/radiant alias radiant-0.6.9=PWD=`pwd` cd ~/.radiant git checkout -q 0.6.9 cd $PWD ~/.radiant/bin/radiant alias radiant-0.7.0=PWD=`pwd` cd ~/.radiant git checkout -q 0.7.0 cd $PWD ~/.radiant/bin/radiant alias radiant-0.7.1=PWD=`pwd` cd ~/.radiant git checkout -q 0.7.1 cd $PWD ~/.radiant/bin/radiant alias radiant-0.8.0=PWD=`pwd` cd ~/.radiant git checkout -q 0.8.0 cd $PWD ~/.radiant/bin/radiant alias radiant-0.8.1=PWD=`pwd` cd ~/.radiant git checkout -q 0.8.1 cd $PWD ~/.radiant/bin/radiant alias radiant-edge=PWD=`pwd` cd ~/.radiant git checkout -q master cd $PWD ~/.radiant/bin/radiant (http://gist.github.com/208708 in case the mailing list mangles the line endings) - reload your .bashrc (or .profile or whatever you edited); i.e. `source ~/.bashrc` you can test them by running commands like `radiant-0.7.1 --version` and `radiant-0.8.1 --version` you may see errors having to do with submodules but those are harmless for the use of simply being able to generate new sites from any version of radiant. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: Git Confusion - thread detour from [Radiant] [ANN] Radiant 0.9.0 RC1
oh and once you've created a radiant from an older version (or edge) you probably want to freeze it with `rake radiant:freeze:edge TAG=0.7.1` or whatever On Mon, Oct 12, 2009 at 3:35 PM, john muhl johnm...@gmail.com wrote: On Mon, Oct 12, 2009 at 3:02 PM, Nate Turnage pixeln...@gmail.com wrote: On Mon, Oct 12, 2009 at 2:45 PM, Dayne Broderson da...@gina.alaska.eduwrote: [dbrod...@beef ~]$ gem environment ... [dbrod...@beef ~]$ /usr/local/lib/ruby/gems/1.8/gems/radiant-0. radiant-0.6.9/ radiant-0.7.0/ radiant-0.7.1/ radiant-0.8.1/ [dbrod...@beef ~]$ /usr/local//ib/ruby/gems/1.8/gems/radiant-0.7.1/bin/radiant That's pretty easy? :^O I guess it's not that difficult, but I could have sworn there was an easier way. Something like this: radiant -v=0.7.1 --database [mysql] project That of course doesn't work, but I thought there was something easy like that. I could be wrong, probably am. i've found the following to be pretty easy to use once it's setup. - clone the latest radiant source to somewhere in your home directory; i use ~/.radiant git clone git://github.com/radiant/radiant.git ~/.radiant - add aliases to your ~/.bashrc file (or ~/.profile or whatever) such as: alias radiant-0.6.8=PWD=`pwd` cd ~/.radiant git checkout -q 0.6.8 cd $PWD ~/.radiant/bin/radiant alias radiant-0.6.9=PWD=`pwd` cd ~/.radiant git checkout -q 0.6.9 cd $PWD ~/.radiant/bin/radiant alias radiant-0.7.0=PWD=`pwd` cd ~/.radiant git checkout -q 0.7.0 cd $PWD ~/.radiant/bin/radiant alias radiant-0.7.1=PWD=`pwd` cd ~/.radiant git checkout -q 0.7.1 cd $PWD ~/.radiant/bin/radiant alias radiant-0.8.0=PWD=`pwd` cd ~/.radiant git checkout -q 0.8.0 cd $PWD ~/.radiant/bin/radiant alias radiant-0.8.1=PWD=`pwd` cd ~/.radiant git checkout -q 0.8.1 cd $PWD ~/.radiant/bin/radiant alias radiant-edge=PWD=`pwd` cd ~/.radiant git checkout -q master cd $PWD ~/.radiant/bin/radiant (http://gist.github.com/208708 in case the mailing list mangles the line endings) - reload your .bashrc (or .profile or whatever you edited); i.e. `source ~/.bashrc` you can test them by running commands like `radiant-0.7.1 --version` and `radiant-0.8.1 --version` you may see errors having to do with submodules but those are harmless for the use of simply being able to generate new sites from any version of 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] Regarding the diplay of posts and stylesheets
On Sun, Oct 11, 2009 at 8:05 AM, Bhavin Patel mindtra...@gmail.com wrote: *Still i am not able to see the post ? why .. what can be done?* i see your posts. could you be more clear about what the issue is? *as well as i have created stylesheet layout too to use with styles page in root but even the styles are not in effect... i tried many things.. but maybe i am missing something core* your style sheets page is called styles but in your layout you have: link rel=stylesheet href=/stylesheet media=all title=Default charset=utf-8/ which should be: link rel=stylesheet href=/styles media=all title=Default charset=utf-8/ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Regarding the diplay of posts and stylesheets
On Sun, Oct 11, 2009 at 9:03 AM, Nate pixeln...@gmail.com wrote: Bhavin Patel wrote: HiI have a problem. I am new to radiant. You are wrapping your title and content with snippet tags. r:snippet name=headerh1r:title//h1 r:content/ /r:snippet Whether you intended that or not, hat's not how snippets work. Snippets are self-contained blocks of content, defined in the snippets area of the admin. The snippet tags are not used to define areas of a page on the fly. actually that is a perfectly valid way for snippets to work. for example: page: r:snippet name='title'r:title//r:snippet snippet: h1r:yield//h1 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Paginating
http://github.com/Aissac/radiant-paginate-extension looks like it might help. On Thu, Sep 24, 2009 at 11:48 PM, Mamed Mamedov mamed.mame...@gmail.com wrote: Hi all! I'am using Radiant 0.7.1 in one of my projects now. And I need to paginate my articles stored in the tree under /releases/ slug. For example, 1. /releases/20090921-01 2. /releases/20090921-02 3. /releases/20090921-03 4. /releases/20090920-01 And so on... Count of this pages may be about 200-300. I have some page, called /press-releases/ which is described as: r:find url=/releases/ r:children:each limit=20 order=desc by=published_at div class=dater:date for=published_at format=%d.%m.%Y //div div class=texta href=r:url /r:translator:title //abr /r:translator:short length=450 //div table cellpadding=0 cellspacing=0 class=sep_linetrtd/td/tr/table /r:children:each /r:find This helps me to display only last 20 items of /releases/ tree. But what if I need to display other releases, even after this 20? I need to draw some page-link, for example: Pages: 1 | 2 | 3 | 4 | 5 ... On page 2, it will display items from 21 to 40 On page 3, it will display items from 41 to 60 and so on... Is there any stuff in radiant CMS to help me with this task? Can anybody help me? Thank you all! Regards, Mamed Mamedov Sent from Baku, Azerbaijan Marie von Ebner-Eschenbachhttp://www.brainyquote.com/quotes/authors/m/marie_von_ebnereschenbac.html - Even a stopped clock is right twice a day. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Caching Mystery
On Thu, Sep 24, 2009 at 1:04 PM, Mohit Sindhwani t...@onghu.com wrote: Tom Stoll wrote: HI, I managed to install Radiant 0.8.1 on Bluehost via the vendor directory. Everything worked on the admin page, and I set up a page following the tutorials. However, when I viewed my site, the same page is served, no matter what, for 5 minutes. I'm thinking that I missed something obvious, but what? There's very little on the radiant wiki about caching besides some brief discussion about pages being automatically cached for 5 minutes. How do I control the caching behavior? what about it do you want to control? if you just want the 5 minutes to be longer or shorter you can add something like `SiteController.cache_timeout = 1.week` or `SiteController.cache_timeout = 1.minute` to your environment.rb file inside the config.after_initialize block Silly question... but you are editing the page you are viewing, right? I haven't used 0.8.1, but in earlier versions, if you changed a child page and that should update a parent, it would not happen. 0.8.1 removes the entire cache when you save any page. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] radiant pros wiki page
apparently edit 26 or general github wonkiness caused the radiant pros wiki page to lose all the listings after paceline. if you had a listing there you might want to go have a look at see that it's still there. if yours got lost http://wiki.github.com/radiant/radiant/radiant-pros/25 might help. ___ 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 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] copy move extension install error
it looks like the copy_move extension doesn't have an install task try: rake production radiant:extensions:copy_move:migrate rake production radiant:extensions:copy_move:update or just use ./script/extension install copy_move and let it take care of that for you. On Thu, Sep 10, 2009 at 9:02 AM, Jan M.J. Storms j...@storms.org wrote: Hi, I just installed the copy/move extension for a site running radiant 0.8.1 The installation gives the error below. As far as I can tell thoucgh, the extension works properly. rake production radiant:extensions:copy_move:install --trace (in /Library/WebServer/stekstad/info.psychopathie/cms/radiant) ** Invoke production (first_time) ** Execute production ** Invoke environment (first_time) ** Execute environment rake aborted! Don't know how to build task 'radiant:extensions:copy_move:install' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1728:in `[]' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2050:in `invoke_task' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/local/bin/rake:16:in `load' - Jan ___ 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] Backup
2009/9/9 María Paula Mariani paulamari...@gmail.com: Considering this, I've made a .tar.gz of my whole radiant directory, including /config. I would like to make that db:dump (which is the correct command?) to create the db backup but I don't know which command is it and which is the name of the database radiant is creating per default when we create a project. you can find your database connection information inside the config/database.yml file. you're probably most interested in the production database settings; unless of course you have other environments you'd like to backup. for mysql you'll need to run a terminal command such as: mysqldump -u mysql_user your_radiant_db_name dump.mysql.db or: mysqldump -u mysql_user -p your_radiant_db_name dump.mysql.db if the mysql_user requires a password to connect to the db. see http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html for the full documentation. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] extension dependencies in ray
On Sat, Sep 5, 2009 at 10:12 AM, Sean Cribbs seancri...@gmail.com wrote: Looks like it's time for another release of Radiant: WHAT'S NEW IN THIS RELEASE? * Allow extensions to declare dependencies [Josh French] does this mean that i can safely rip out all the code in ray that tries to allow some extension dependencies? my feeling is that it wasn't ever a hit feature in ray and that the implementation in radiant is more usable/flexible. is anyone using the dependency feature in ray who be sad to see it go? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] extension dependencies in ray
thanks for the details. guess that code stays for now. On Wed, Sep 9, 2009 at 1:32 PM, Sean Cribbs seancri...@gmail.com wrote: This is a *runtime* dependency, not an install-time one. Basically, an extension can do this: extension_config do |config| config.extension paperclipped end The initializer will check that paperclipped is available in the app and error out if not. Sean john muhl wrote: On Sat, Sep 5, 2009 at 10:12 AM, Sean Cribbs seancri...@gmail.com wrote: Looks like it's time for another release of Radiant: WHAT'S NEW IN THIS RELEASE? * Allow extensions to declare dependencies [Josh French] does this mean that i can safely rip out all the code in ray that tries to allow some extension dependencies? my feeling is that it wasn't ever a hit feature in ray and that the implementation in radiant is more usable/flexible. is anyone using the dependency feature in ray who be sad to see it go? ___ 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] Backup
it depends on how what sort of database you're using. if it's sqlite you can simply zip up the entire radiant project and call that a backup. if it's mysql or something else you can use that db's dump/import tools plus a zip file of the radiant project to create a backup. version control also works well for rolling back the project directory (and database if you're using sqlite). 2009/9/7 María Paula Mariani paulamari...@gmail.com: Hello! I'd like to know which is the best way to freeze or to make a backup of my project made in Radiant. I'd like to try some extensions and I'd like to have a backup just in case something goes wrong. How is the best way to restore the project and database (from a backup)? Thanks very much! -- Paula ___ 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] radiant keyword list is too small
On Tue, Sep 1, 2009 at 12:41 PM, dave4c03dave4...@greatchiro.com wrote: The quote is in a new book I bought about HTML 4.01 strict. HTML in easy steps sixth edition (2009) by Mike McGrath page 28 says: Promotion of the page by keywords is best achieved by following some simple guidelines: Use only lowercase characters Keep all keywords on a simple line Never repeat a keyword in the list Limit the keywords list to 1,000 characters or less Try to use the plural form for keywords - to match searches made with both the single and plural forms of that word Hypertext-Matching Analysis: Our search engine also analyzes page content. However, instead of simply scanning for page-based text (which can be manipulated by site publishers through meta-tags), our technology analyzes the full content of a page and factors in fonts, subdivisions and the precise location of each word. We also analyze the content of neighboring web pages to ensure the results returned are the most relevant to a user's query. [1] Don't load pages with irrelevant keywords. [2] Keyword stuffing refers to the practice of loading a webpage with keywords in an attempt to manipulate a site's ranking in Google's search results. Filling pages with keywords results in a negative user experience, and can harm your site's ranking. Focus on creating useful, information-rich content that uses keywords appropriately and in context. [3] Use a keyword meta-tag to list key words for the document. Use a distinct list of keywords that relate to the specific page on your site instead of using one broad set of keywords for every page. [4] none of those sources suggest to me that 1000 characters of keywords is going to be any more useful in page ranking than 200 characters. [1] http://www.google.com/corporate/tech.html [2] http://www.google.com/support/webmasters/bin/answer.py?answer=35769 [3] http://www.google.com/support/webmasters/bin/answer.py?answer=66358 [4] http://help.yahoo.com/l/us/yahoo/search/ranking/ranking-02.html ___ 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: Condition in Page Attachments extension
i think the r:if_attachments name=image.png.../r:if_attachments might be what you're looking for. On Wed, Aug 19, 2009 at 3:54 PM, Rafael Carvalhorafaelmcarva...@gmail.com wrote: I resolved it just adding if page.attachment(name) != nil in tag attachment:image do |tag| -- Rafael Carvalho ___ 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: Condition in Page Attachments extension
don't forget the available tags link in the page edit interface. open that and type attachment into the search most if not all of page_attachments tags should be documented in there. On Wed, Aug 19, 2009 at 6:36 PM, Rafael Carvalhorafaelmcarva...@gmail.com wrote: hmm... i'm starting to use the page attachments now... i didn't know about this tag! i'm shine... ehhe thanks! -- Rafael Carvalho ___ 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] Comments Extension and Notifications
you can set `Radiant::Config['comments.auto_approve'] = true` through the console, your environment or the settings extension and it will auto-approve comments. On Thu, Aug 13, 2009 at 12:02 PM, subsor...@gmail.com wrote: Hi, Firstly thanks to all those who developed this extension, it seems like quite a roll call. Is this feature supported? I can see in TODO a note about stating that something similar is pending, but a quick glance through the code suggests it is in place. If it isn't implemented is it possible to auto approve comments that pass the simple spam test? Thanks , ___ 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] Problem installing mailer extension
you must be looking at old documentation - there is no longer any mailer page type. http://wiki.github.com/radiant/radiant/mailer-extension On Sun, Aug 9, 2009 at 9:05 AM, exitsevenexitse...@gmail.com wrote: Well okay, I just disabled other extensions and git cloned the mailer extension. Mailer extension shows up under extensions in radiant. But I am unable to set the page type to mailer, because it is not listed in the dropdown. What can I do? Why is mailer not listed in the dropdown? Best wishes, rainer On Thu, Aug 6, 2009 at 10:11 PM, john muhljohnm...@gmail.com wrote: `script/extension install` runs both the migrate and update tasks regardless just to be safe. extensions that plan for this include empty migrate/update task to keep these messages from confusing users. On Thu, Aug 6, 2009 at 1:11 PM, exitsevenexitse...@gmail.com wrote: Hm, thanks for the answer. But I run the provided installer script (./script/extension install mailer). This script is running the update. Why is it doing this, if it is not needed? I did not touched the script. I know that the mailer extension needs to get configured in the mailer page part. But what do you mean with: You just need to clone the extension and config the mailer in the mailer page part. To clone? You mean copy? What do I have to copy? Your help will be very appreciated! Thanks! rainer On Thu, Aug 6, 2009 at 12:23 PM, Cristi Dumacristi.d...@aissac.ro wrote: The thing is that you don't need to run update on mailer extension. There's nothing to update. As there is nothing to migrate. You just need to clone the extension and config the mailer in the mailer page part. And you get that error, because the update task is not present in the extension. Cristi On 06.08.2009 12:29, Mamed Mamedov wrote: Does anyone knows if it compatible with last version of radiant (0.8)? I'am using it on 0.7.1 without any problem. Regards, Mamed Mamedov Samuel Goldwynhttp://www.brainyquote.com/quotes/authors/s/samuel_goldwyn.html - I'm willing to admit that I may not always be right, but I am never wrong. On Thu, Aug 6, 2009 at 2:20 PM, exitsevenexitse...@gmail.com wrote: Hey Mamed, sure, thanks for the quick reply! ~$ ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [i686-linux] Ruby Enterprise Edition 20090610 ~$ rails -v Rails 2.3.3 ~$ radiant -v Radiant 0.8.0 Does it help? Best wishes, rainer On Thu, Aug 6, 2009 at 11:02 AM, Mamed Mamedovmamed.mame...@gmail.com wrote: I think there is problem with your radiant/rails/ruby versions cross-compatibility.. ha? Please give us your actual versions of radiant, rails and ruby. Thank you! Regards, Mamed Mamedov Mike Ditkahttp://www.brainyquote.com/quotes/authors/m/mike_ditka.html - If God had wanted man to play soccer, he wouldn't have given us arms. On Thu, Aug 6, 2009 at 1:45 PM, exitsevenexitse...@gmail.com wrote: Hello again, I just tried to install the mailer extension as described here: http://wiki.github.com/radiant/radiant/mailer-extension and here (manually): http://wiki.github.com/radiant/radiant/installing-extensions#manual Unfortunately the installation process (rake) exits with: $ rake radiant:extensions:mailer:update --trace (in /home/claude/DEV/freiraumart) rake aborted! Don't know how to build task 'radiant:extensions:mailer:update' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1728:in `[]' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2050:in `invoke_task' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /opt/ruby-enterprise-1.8.6-20090610/bin/rake:19:in `load' /opt/ruby-enterprise-1.8.6-20090610/bin/rake:19 What am I doing wrong? Could someone please help me? Thanks, rainer ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site:
Re: [Radiant] Problem installing mailer extension
`script/extension install` runs both the migrate and update tasks regardless just to be safe. extensions that plan for this include empty migrate/update task to keep these messages from confusing users. On Thu, Aug 6, 2009 at 1:11 PM, exitsevenexitse...@gmail.com wrote: Hm, thanks for the answer. But I run the provided installer script (./script/extension install mailer). This script is running the update. Why is it doing this, if it is not needed? I did not touched the script. I know that the mailer extension needs to get configured in the mailer page part. But what do you mean with: You just need to clone the extension and config the mailer in the mailer page part. To clone? You mean copy? What do I have to copy? Your help will be very appreciated! Thanks! rainer On Thu, Aug 6, 2009 at 12:23 PM, Cristi Dumacristi.d...@aissac.ro wrote: The thing is that you don't need to run update on mailer extension. There's nothing to update. As there is nothing to migrate. You just need to clone the extension and config the mailer in the mailer page part. And you get that error, because the update task is not present in the extension. Cristi On 06.08.2009 12:29, Mamed Mamedov wrote: Does anyone knows if it compatible with last version of radiant (0.8)? I'am using it on 0.7.1 without any problem. Regards, Mamed Mamedov Samuel Goldwynhttp://www.brainyquote.com/quotes/authors/s/samuel_goldwyn.html - I'm willing to admit that I may not always be right, but I am never wrong. On Thu, Aug 6, 2009 at 2:20 PM, exitsevenexitse...@gmail.com wrote: Hey Mamed, sure, thanks for the quick reply! ~$ ruby -v ruby 1.8.6 (2008-08-11 patchlevel 287) [i686-linux] Ruby Enterprise Edition 20090610 ~$ rails -v Rails 2.3.3 ~$ radiant -v Radiant 0.8.0 Does it help? Best wishes, rainer On Thu, Aug 6, 2009 at 11:02 AM, Mamed Mamedovmamed.mame...@gmail.com wrote: I think there is problem with your radiant/rails/ruby versions cross-compatibility.. ha? Please give us your actual versions of radiant, rails and ruby. Thank you! Regards, Mamed Mamedov Mike Ditkahttp://www.brainyquote.com/quotes/authors/m/mike_ditka.html - If God had wanted man to play soccer, he wouldn't have given us arms. On Thu, Aug 6, 2009 at 1:45 PM, exitsevenexitse...@gmail.com wrote: Hello again, I just tried to install the mailer extension as described here: http://wiki.github.com/radiant/radiant/mailer-extension and here (manually): http://wiki.github.com/radiant/radiant/installing-extensions#manual Unfortunately the installation process (rake) exits with: $ rake radiant:extensions:mailer:update --trace (in /home/claude/DEV/freiraumart) rake aborted! Don't know how to build task 'radiant:extensions:mailer:update' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1728:in `[]' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2050:in `invoke_task' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /opt/ruby-enterprise-1.8.6-20090610/bin/rake:19:in `load' /opt/ruby-enterprise-1.8.6-20090610/bin/rake:19 What am I doing wrong? Could someone please help me? Thanks, rainer ___ 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
Re: [Radiant] Problem unsolved: Multiple languages for content
could you just ask your snippet to give the right urls? r:if_url matches='^/de' r:navigation urls=home: /de/home | ueberuns: /de/ueber_uns/ | kontakt: /de/kontakt/ /r:if_url r:if_url matches='^/en' r:navigation urls=home: /en/home | aboutus: /en/about_us/ | contact: /en/contact/ /r:if_url still some duplication but much less and duplicating layouts On Thu, Aug 6, 2009 at 2:06 PM, exitsevenexitse...@gmail.com wrote: Hey again, sorry, I'm still looking around for a solution. I stumbled over an old post of someone having the same problem (http://www.ruby-forum.com/topic/133019). He writes exactly about what I need. But besides I am unable to install the Language Redirect extension, it is not exactly what I need. I have to page trees: 1) /de/page 2) /en/page The /de-tree is working fine. The user should now be able to hit a link English version on the site and should then get to the /en-tree-contents. So far not a problem. The user gets to for example /en/home. But from now on he should only get contents from the /en-tree: /en/home/ /en/about_us /en/contact /en/... I use a snippet to render the menu: r:navigation urls=home: /de/home | ueberuns: /de/ueber_uns/ | kontakt: /de/kontakt/ Do I have to double every layout I have into an /en- and an /de-version? I thought there is propably some extension that automatically routes every /de-request to the /en-tree if the user requested the english version of the site one time by clicking the English version link. Hopefully you understand the problem and there is an answer somewhere outside... Best wishes, rainer ___ 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] Radiant In Herolu
i've done this a few times and it was straightforward. could you be more specific about where you're running into issues? On Wed, Jul 29, 2009 at 7:15 AM, Mauricio Dulcemauricio.du...@gmail.com wrote: Hello, I need help to config paperclipped extension to use in heroku and s3. ___ 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] Radiant In Herolu
On Wed, Jul 29, 2009 at 9:09 AM, Charlie Robbinscharlie.robb...@gmail.com wrote: I had also had this thought. It seems that with an s3 (or cloudfiles) enabled paperclipped extension along with SnS, it could be possible to run Radiant seamlessly in the cloud. Anyone want to get down on this project? You fork? I fork? We all can fork fork. http://empty-river-61.heroku.com/ you can login with admin/radiant to see the paperclipped settings. obviously i am not giving away s3 credentials so you can't actually upload images but you can at least see how it works. i still haven't heard a real issue with running radiant in the cloud. i have a few production sites running completely on heroku and s3 and haven't had any trouble. Charlie On Wed, Jul 29, 2009 at 9:15 AM, Mauricio Dulce mauricio.du...@gmail.comwrote: Hello, I need help to config paperclipped extension to use in heroku and s3. ___ 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] Radiant In Herolu
On Wed, Jul 29, 2009 at 2:11 PM, Keith Bingmanke...@keithbingman.com wrote: Paperclip actually has a 0.7.1 branch and I think the current version works with 0.7.1 as well. Settings does not, but I have so many lying around.. there are some very minor changes to make it work though. turns out i was looking at paperclipped-multi-site (for whatever reason github put it at the top of the search for radiant+paperclipped). sorry for the confusion. Keith On Jul 29, 2009, at 10:21 AM, john muhl wrote: On Wed, Jul 29, 2009 at 10:51 AM, Mauricio Dulcemauricio.du...@gmail.com wrote: Thanks, but the problem is that I'm using the previous version of radiant, one can say where I get the two paperclipped extensions and settings for this or that version 0.7.1 or extensions such as comments and poll event calendar work in 0.8 most extensions will have a branch or tag for the different incompatible versions...of course neither paperclipped or settings have a branch or tag for 0.7 compatibility so you'll have to go through the history looking for where they added the changes to go from 0.7 to 0.8 and checkout the appropriate commit. however comments has a 0.7.1 tag to use it you would use something like: git clone git://github.com/artofmission/radiant-comments.git vendor/extensions/comments cd vendor/extensions/comments git checkout -b 071 radiant0.7.1 ___ 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] Ray extension problem
actually, this looks like an error someone else had with dreamhost, you probably just need to delete the preferences file, then run rake ray:setup:download rake ray:setup:restart server=passenger then try installing extensions. i have no idea why this only happens with dreamhost. On Tue, Jul 28, 2009 at 9:27 AM, john muhljohnm...@gmail.com wrote: can you post the contents of vendor/extensions/ray/preferences.yml On Tue, Jul 28, 2009 at 5:25 AM, Jonathan Batchelorj...@atuin.co.uk wrote: I've been playing about with Radiant for a few days now and am really liking it's simplicity and flexibility. After installing on my MacBook and beginning some developmet I want to install on my Dreamhost account. I have been migrated to a newer server by Dreamhost and have Radiant 0.8.0 working now. I started to install install extensions and took the advice on the wiki page to use ray as it will automatically reload Passenger for me. However although the script/extensions install command works fine, as did setting the config for ray using rake ray:setup:restart server=passenger, when I come to install an extension it does not work. I have included the --trace output below - can anyone help? Thanks, Jonathan. $ rake production ray:extension:install name=dashboard --trace (in /home//_radiant) ** Invoke production (first_time) ** Execute production ** Invoke environment (first_time) ** Execute environment ** Invoke ray:extension:install (first_time) ** Execute ray:extension:install rake aborted! undefined method `strip' for nil:NilClass /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:807:in `get_download_preference' /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:151:in `install_extension' /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:20 /home//.gems/gems/rake-0.8.7/lib/rake.rb:636:in `call' /home//.gems/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /home//.gems/gems/rake-0.8.7/lib/rake.rb:631:in `each' /home//.gems/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /home//.gems/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /home//.gems/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /home//.gems/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /home//.gems/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /home//.gems/gems/rake-0.8.7/bin/rake:31 /home//.gems/bin/rake:19:in `load' /home//.gems/bin/rake:19 ___ 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] Ray extension problem
i've just fixed this, update ray and you shouldn't run into that anymore. On Tue, Jul 28, 2009 at 5:25 AM, Jonathan Batchelorj...@atuin.co.uk wrote: I've been playing about with Radiant for a few days now and am really liking it's simplicity and flexibility. After installing on my MacBook and beginning some developmet I want to install on my Dreamhost account. I have been migrated to a newer server by Dreamhost and have Radiant 0.8.0 working now. I started to install install extensions and took the advice on the wiki page to use ray as it will automatically reload Passenger for me. However although the script/extensions install command works fine, as did setting the config for ray using rake ray:setup:restart server=passenger, when I come to install an extension it does not work. I have included the --trace output below - can anyone help? Thanks, Jonathan. $ rake production ray:extension:install name=dashboard --trace (in /home//_radiant) ** Invoke production (first_time) ** Execute production ** Invoke environment (first_time) ** Execute environment ** Invoke ray:extension:install (first_time) ** Execute ray:extension:install rake aborted! undefined method `strip' for nil:NilClass /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:807:in `get_download_preference' /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:151:in `install_extension' /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:20 /home//.gems/gems/rake-0.8.7/lib/rake.rb:636:in `call' /home//.gems/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /home//.gems/gems/rake-0.8.7/lib/rake.rb:631:in `each' /home//.gems/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /home//.gems/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /home//.gems/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /home//.gems/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /home//.gems/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /home//.gems/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /home//.gems/gems/rake-0.8.7/bin/rake:31 /home//.gems/bin/rake:19:in `load' /home//.gems/bin/rake:19 ___ 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] multi_site
try `git clone git://github.com/radiant/radiant-multi-site-extension.git` all the extensions from the old svn repo have been moved to http://github.com/radiant and almost all 3rd party extension development has moved to git as well. although if you're trying to use 0.6.7 you may find the versions available on github incompatible it has after all been over a year since that release. On Sun, Jul 26, 2009 at 3:13 PM, Caleb Adam Hayeca...@firecollective.com wrote: I am using the multi-site extension, and am having trouble packaging my app up for deployment. The following command doesn’t work, because the SVN repo is Gone (410): svn export http://svn.radiantcms.org/radiant/tags/rel_0-6-7/extensions/multi_site/vendor/extensions/multi_site Any idea where it went? or how i can achieve my goal of being able to deploy my site w/ the multi_site extension encapsulated? ___ 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] New setup - How to get it right?
as jim points out it's probably your rubygems version, if you installed rubygems via apt-get then you have 1.2... which will not work and due to the way debian packages rubygems you cannot easily update the system version. so your best bet is to reinstall the latest rubygems from source and then reinstall all your gems using that version. On Wed, Jul 22, 2009 at 2:04 PM, Jim Gayj...@saturnflyer.com wrote: What version of rubygems do you have? gem --version Try updating rubygems and you should be good. Rails requires version 1.3.1 or greater I believe. gem update system Jim Gay http://www.saturnflyer.com On Jul 22, 2009, at 3:23 PM, exitseven wrote: On Wed, Jul 22, 2009 at 12:16 PM, Mamed Mamedov mamed.mame...@gmail.com wrote: Installation process of radiant is very simple. Feel free to try and ask if any questions ;) Sad to say... The installation seems not to be that very simple. That's why I asked before but I am in trouble again as every time I have to intall this thing... Would you please help? This is what I did: # gem install radiant (including dependencies) # export PATH=${PATH}:/var/lib/gems/1.8/bin (because radiant was not found by default install) This is what I get: # radiant --database mysql /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/../../activesupport/lib/active_support/dependencies.rb:55: uninitialized constant ActiveSupport::Dependencies::Mutex (NameError) from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require' from /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/../../activesupport/lib/active_support.rb:56 from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require' from /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/rails_generator.rb:28 from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require' from /var/lib/gems/1.8/gems/radiant-0.8.0/bin/radiant:18 from /var/lib/gems/1.8/bin/radiant:18:in `load' from /var/lib/gems/1.8/bin/radiant:18 Any ideas? Thanks, rainer ___ 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] New setup - How to get it right?
actually better yet is to probably just use ruby enterprise edition and forego debian's ruby packages completely. http://www.rubyenterpriseedition.com/download.html - i've always felt it was a much easier way to install ruby on any type of system. On Wed, Jul 22, 2009 at 2:15 PM, john muhljohnm...@gmail.com wrote: as jim points out it's probably your rubygems version, if you installed rubygems via apt-get then you have 1.2... which will not work and due to the way debian packages rubygems you cannot easily update the system version. so your best bet is to reinstall the latest rubygems from source and then reinstall all your gems using that version. On Wed, Jul 22, 2009 at 2:04 PM, Jim Gayj...@saturnflyer.com wrote: What version of rubygems do you have? gem --version Try updating rubygems and you should be good. Rails requires version 1.3.1 or greater I believe. gem update system Jim Gay http://www.saturnflyer.com On Jul 22, 2009, at 3:23 PM, exitseven wrote: On Wed, Jul 22, 2009 at 12:16 PM, Mamed Mamedov mamed.mame...@gmail.com wrote: Installation process of radiant is very simple. Feel free to try and ask if any questions ;) Sad to say... The installation seems not to be that very simple. That's why I asked before but I am in trouble again as every time I have to intall this thing... Would you please help? This is what I did: # gem install radiant (including dependencies) # export PATH=${PATH}:/var/lib/gems/1.8/bin (because radiant was not found by default install) This is what I get: # radiant --database mysql /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/../../activesupport/lib/active_support/dependencies.rb:55: uninitialized constant ActiveSupport::Dependencies::Mutex (NameError) from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require' from /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/../../activesupport/lib/active_support.rb:56 from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require' from /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/rails_generator.rb:28 from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require' from /var/lib/gems/1.8/gems/radiant-0.8.0/bin/radiant:18 from /var/lib/gems/1.8/bin/radiant:18:in `load' from /var/lib/gems/1.8/bin/radiant:18 Any ideas? Thanks, rainer ___ 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] mailer extension and 0.8
do you mean works with 0.8.0 as in being able to use mailer.post_to_page? = true without having to hack on it? as far as i can tell it still causes 500s in your new version. On Tue, Jul 14, 2009 at 12:23 AM, Cristi Dumacristi.d...@aissac.ro wrote: glad you figured it out. this means I can anounce the new version of mailer this version http://github.com/Aissac/radiant-mailer-extension/tree/master of Mailer Extension works on Radiant 0.8 and I added the mail attachments from Jomz's branch. Also there are some cucumber features and the specs have been fixed. Hasn't been tested on a production site yet, but locally it works pretty good. Pull requests have been sent. Cheers, Cristi On 7/14/09 12:24 AM, john muhl wrote: turns out the culprit is mailer.post_to_page? = true ___ 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] mailer extension and 0.8
turns out the culprit is mailer.post_to_page? = true On Wed, Jul 8, 2009 at 3:31 PM, john muhljohnm...@gmail.com wrote: the issue seems to have resolved itself with radiant edge. On Wed, Jul 8, 2009 at 2:20 PM, john muhljohnm...@gmail.com wrote: yes, of course. i'm just not convinced it's the proper fix, it just happened to be the most expedient one. here is the diff for the curious: diff --git a/lib/radiant/cache.rb b/lib/radiant/cache.rb index a82..2e16de9 100644 --- a/lib/radiant/cache.rb +++ b/lib/radiant/cache.rb @@ -48,7 +48,7 @@ module Radiant end private - def restore_response(hash, body) + def restore_response(hash, body=nil) # Cribbed from the Rack::Cache source status = hash.delete('X-Status').to_i response = Rack::Cache::Response.new(status, hash, body) On Wed, Jul 8, 2009 at 1:56 PM, Victor Elsendoornelsendo...@w3craft.nl wrote: Only mentioning you fixed it, won't do any help for the Radiant community. Please inform us about the solution or bugs you have found. Thanks in advance. On Jul 8, 2009, at 9:51 PM, john muhl wrote: i went down through the code and think i may have found the issue which appears to be at the radiant level. thanks again for all the help. On Wed, Jul 8, 2009 at 1:10 PM, Cristi Dumacristi.d...@aissac.ro wrote: I created a radiant project with the code from the gist you supplied, and after putting the config.after_initialize block in development.rb worked flawlessly. So is there the possibility that the problem is not in mailer_extension? On 7/8/09 9:58 PM, john muhl wrote: same error with the smtp settings in development.rb On Wed, Jul 8, 2009 at 12:01 PM, Istvan Hokaistvan.h...@gmail.com wrote: Could you try moving the contents of your config.after_initialize block to development.rb or production.rb? -- Istvan Hoka On Wed, Jul 8, 2009 at 8:47 PM, john muhljohnm...@gmail.com wrote: oh, and those results are the same with radiant/mailer or aissac/mailer On Wed, Jul 8, 2009 at 11:43 AM, john muhljohnm...@gmail.com wrote: this is running locally in the development environment. i've tested with webrick, mongrel, thin and passenger and they all have the same error message until you get to server specific part. the test site is the styled blog with only the mailer extension added. all the page parts and environment.rb are here: http://gist.github.com/142995 - i also have mailer.post_to_page? = true set. just to make sure it wasn't inherent in the system i setup a styled blog with 0.7.1 installed mailer, used the same parts and smtp settings and was able to send mail on all 4 servers. thanks for help. On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hokaistvan.h...@gmail.com wrote: John, it looks like you are getting this on your production machine where you are using Thin. Could you test with Passenger or Mongrel, perhaps locally and see if you get the same error? Also, could you provide some more context? For instance, are you trying to attach a file or is it a simple form you are mailing? Cheers! -- Istvan Hoka On Wed, Jul 8, 2009 at 7:34 PM, john muhljohnm...@gmail.com wrote: thanks but it gives the same error. On Wed, Jul 8, 2009 at 10:02 AM, Cristi Dumacristi.d...@aissac.ro wrote: Hi John, I'm playing with it right now, tried some fixes, features and stuff It works for me on a site I'm currently developing Check it out: http://github.com/Aissac/radiant-mailer-extension/tree/master On 7/8/09 6:05 PM, john muhl wrote: has anyone successfully used mailer on 0.8? whenever i try to send mail i get a 500 error page and the following: SQL (1.2ms) SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' SQL (1.9ms) SELECT DISTINCT class_name FROM pages WHERE class_name '' AND class_name IS NOT NULL /!\ FAILSAFE /!\ Wed Jul 08 09:01:58 -0600 2009 Status: 500 Internal Server Error wrong number of arguments (1 for 2) /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `restore_response' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `map' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in `call!' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call' /private/tmp
[Radiant] mailer extension and 0.8
has anyone successfully used mailer on 0.8? whenever i try to send mail i get a 500 error page and the following: SQL (1.2ms)SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' SQL (1.9ms) SELECT DISTINCT class_name FROM pages WHERE class_name '' AND class_name IS NOT NULL /!\ FAILSAFE /!\ Wed Jul 08 09:01:58 -0600 2009 Status: 500 Internal Server Error wrong number of arguments (1 for 2) /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `restore_response' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `map' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in `call!' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rewindable_input.rb:25:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:93:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/reloader.rb:9:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/failsafe.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `synchronize' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:106:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/cgi_process.rb:44:in `dispatch_cgi' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:102:in `dispatch_cgi' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:28:in `dispatch' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:81:in `call' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:69:in `call' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:76:in `pre_process' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:74:in `catch' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:74:in `pre_process' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:57:in `process' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:42:in `receive_data' /opt/ree/lib/ruby/gems/1.8/gems/eventmachine-0.12.8/lib/eventmachine.rb:242:in `run_machine' /opt/ree/lib/ruby/gems/1.8/gems/eventmachine-0.12.8/lib/eventmachine.rb:242:in `run' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/backends/base.rb:57:in `start' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/server.rb:156:in `start' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/controllers/controller.rb:80:in `start' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/runner.rb:174:in `send' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/runner.rb:174:in `run_command' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/runner.rb:140:in `run!' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/bin/thin:6 /opt/ree/bin/thin:19:in `load' /opt/ree/bin/thin:19 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] mailer extension and 0.8
this is running locally in the development environment. i've tested with webrick, mongrel, thin and passenger and they all have the same error message until you get to server specific part. the test site is the styled blog with only the mailer extension added. all the page parts and environment.rb are here: http://gist.github.com/142995 - i also have mailer.post_to_page? = true set. just to make sure it wasn't inherent in the system i setup a styled blog with 0.7.1 installed mailer, used the same parts and smtp settings and was able to send mail on all 4 servers. thanks for help. On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hokaistvan.h...@gmail.com wrote: John, it looks like you are getting this on your production machine where you are using Thin. Could you test with Passenger or Mongrel, perhaps locally and see if you get the same error? Also, could you provide some more context? For instance, are you trying to attach a file or is it a simple form you are mailing? Cheers! -- Istvan Hoka On Wed, Jul 8, 2009 at 7:34 PM, john muhl johnm...@gmail.com wrote: thanks but it gives the same error. On Wed, Jul 8, 2009 at 10:02 AM, Cristi Dumacristi.d...@aissac.ro wrote: Hi John, I'm playing with it right now, tried some fixes, features and stuff It works for me on a site I'm currently developing Check it out: http://github.com/Aissac/radiant-mailer-extension/tree/master On 7/8/09 6:05 PM, john muhl wrote: has anyone successfully used mailer on 0.8? whenever i try to send mail i get a 500 error page and the following: SQL (1.2ms) SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' SQL (1.9ms) SELECT DISTINCT class_name FROM pages WHERE class_name '' AND class_name IS NOT NULL /!\ FAILSAFE /!\ Wed Jul 08 09:01:58 -0600 2009 Status: 500 Internal Server Error wrong number of arguments (1 for 2) /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `restore_response' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `map' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in `call!' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rewindable_input.rb:25:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:93:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/reloader.rb:9:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/failsafe.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `synchronize' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:106:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/cgi_process.rb:44:in `dispatch_cgi' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:102:in `dispatch_cgi' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:28:in `dispatch' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:81:in `call' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:69:in `call' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:76:in `pre_process' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:74:in `catch' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:74:in `pre_process' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:57:in `process' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:42:in `receive_data' /opt/ree/lib/ruby/gems/1.8/gems/eventmachine-0.12.8/lib/eventmachine.rb:242:in `run_machine' /opt/ree/lib/ruby/gems/1.8/gems/eventmachine-0.12.8/lib/eventmachine.rb:242:in `run' /opt/ree/lib/ruby/gems
Re: [Radiant] mailer extension and 0.8
oh, and those results are the same with radiant/mailer or aissac/mailer On Wed, Jul 8, 2009 at 11:43 AM, john muhljohnm...@gmail.com wrote: this is running locally in the development environment. i've tested with webrick, mongrel, thin and passenger and they all have the same error message until you get to server specific part. the test site is the styled blog with only the mailer extension added. all the page parts and environment.rb are here: http://gist.github.com/142995 - i also have mailer.post_to_page? = true set. just to make sure it wasn't inherent in the system i setup a styled blog with 0.7.1 installed mailer, used the same parts and smtp settings and was able to send mail on all 4 servers. thanks for help. On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hokaistvan.h...@gmail.com wrote: John, it looks like you are getting this on your production machine where you are using Thin. Could you test with Passenger or Mongrel, perhaps locally and see if you get the same error? Also, could you provide some more context? For instance, are you trying to attach a file or is it a simple form you are mailing? Cheers! -- Istvan Hoka On Wed, Jul 8, 2009 at 7:34 PM, john muhl johnm...@gmail.com wrote: thanks but it gives the same error. On Wed, Jul 8, 2009 at 10:02 AM, Cristi Dumacristi.d...@aissac.ro wrote: Hi John, I'm playing with it right now, tried some fixes, features and stuff It works for me on a site I'm currently developing Check it out: http://github.com/Aissac/radiant-mailer-extension/tree/master On 7/8/09 6:05 PM, john muhl wrote: has anyone successfully used mailer on 0.8? whenever i try to send mail i get a 500 error page and the following: SQL (1.2ms) SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' SQL (1.9ms) SELECT DISTINCT class_name FROM pages WHERE class_name '' AND class_name IS NOT NULL /!\ FAILSAFE /!\ Wed Jul 08 09:01:58 -0600 2009 Status: 500 Internal Server Error wrong number of arguments (1 for 2) /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `restore_response' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `map' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in `call!' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rewindable_input.rb:25:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:93:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/reloader.rb:9:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/failsafe.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `synchronize' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:106:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/cgi_process.rb:44:in `dispatch_cgi' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:102:in `dispatch_cgi' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:28:in `dispatch' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:81:in `call' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:69:in `call' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:76:in `pre_process' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:74:in `catch' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:74:in `pre_process' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:57:in `process' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:42:in `receive_data' /opt/ree/lib/ruby/gems/1.8/gems/eventmachine-0.12.8/lib
Re: [Radiant] mailer extension and 0.8
same error with the smtp settings in development.rb On Wed, Jul 8, 2009 at 12:01 PM, Istvan Hokaistvan.h...@gmail.com wrote: Could you try moving the contents of your config.after_initialize block to development.rb or production.rb? -- Istvan Hoka On Wed, Jul 8, 2009 at 8:47 PM, john muhl johnm...@gmail.com wrote: oh, and those results are the same with radiant/mailer or aissac/mailer On Wed, Jul 8, 2009 at 11:43 AM, john muhljohnm...@gmail.com wrote: this is running locally in the development environment. i've tested with webrick, mongrel, thin and passenger and they all have the same error message until you get to server specific part. the test site is the styled blog with only the mailer extension added. all the page parts and environment.rb are here: http://gist.github.com/142995 - i also have mailer.post_to_page? = true set. just to make sure it wasn't inherent in the system i setup a styled blog with 0.7.1 installed mailer, used the same parts and smtp settings and was able to send mail on all 4 servers. thanks for help. On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hokaistvan.h...@gmail.com wrote: John, it looks like you are getting this on your production machine where you are using Thin. Could you test with Passenger or Mongrel, perhaps locally and see if you get the same error? Also, could you provide some more context? For instance, are you trying to attach a file or is it a simple form you are mailing? Cheers! -- Istvan Hoka On Wed, Jul 8, 2009 at 7:34 PM, john muhl johnm...@gmail.com wrote: thanks but it gives the same error. On Wed, Jul 8, 2009 at 10:02 AM, Cristi Dumacristi.d...@aissac.ro wrote: Hi John, I'm playing with it right now, tried some fixes, features and stuff It works for me on a site I'm currently developing Check it out: http://github.com/Aissac/radiant-mailer-extension/tree/master On 7/8/09 6:05 PM, john muhl wrote: has anyone successfully used mailer on 0.8? whenever i try to send mail i get a 500 error page and the following: SQL (1.2ms) SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' SQL (1.9ms) SELECT DISTINCT class_name FROM pages WHERE class_name '' AND class_name IS NOT NULL /!\ FAILSAFE /!\ Wed Jul 08 09:01:58 -0600 2009 Status: 500 Internal Server Error wrong number of arguments (1 for 2) /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `restore_response' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `map' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in `call!' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rewindable_input.rb:25:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:93:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/reloader.rb:9:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/failsafe.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `synchronize' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:106:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/cgi_process.rb:44:in `dispatch_cgi' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:102:in `dispatch_cgi' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:28:in `dispatch' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:81:in `call' /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:69:in `call' /opt/ree/lib/ruby/gems/1.8/gems
Re: [Radiant] mailer extension and 0.8
i went down through the code and think i may have found the issue which appears to be at the radiant level. thanks again for all the help. On Wed, Jul 8, 2009 at 1:10 PM, Cristi Dumacristi.d...@aissac.ro wrote: I created a radiant project with the code from the gist you supplied, and after putting the config.after_initialize block in development.rb worked flawlessly. So is there the possibility that the problem is not in mailer_extension? On 7/8/09 9:58 PM, john muhl wrote: same error with the smtp settings in development.rb On Wed, Jul 8, 2009 at 12:01 PM, Istvan Hokaistvan.h...@gmail.com wrote: Could you try moving the contents of your config.after_initialize block to development.rb or production.rb? -- Istvan Hoka On Wed, Jul 8, 2009 at 8:47 PM, john muhljohnm...@gmail.com wrote: oh, and those results are the same with radiant/mailer or aissac/mailer On Wed, Jul 8, 2009 at 11:43 AM, john muhljohnm...@gmail.com wrote: this is running locally in the development environment. i've tested with webrick, mongrel, thin and passenger and they all have the same error message until you get to server specific part. the test site is the styled blog with only the mailer extension added. all the page parts and environment.rb are here: http://gist.github.com/142995 - i also have mailer.post_to_page? = true set. just to make sure it wasn't inherent in the system i setup a styled blog with 0.7.1 installed mailer, used the same parts and smtp settings and was able to send mail on all 4 servers. thanks for help. On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hokaistvan.h...@gmail.com wrote: John, it looks like you are getting this on your production machine where you are using Thin. Could you test with Passenger or Mongrel, perhaps locally and see if you get the same error? Also, could you provide some more context? For instance, are you trying to attach a file or is it a simple form you are mailing? Cheers! -- Istvan Hoka On Wed, Jul 8, 2009 at 7:34 PM, john muhljohnm...@gmail.com wrote: thanks but it gives the same error. On Wed, Jul 8, 2009 at 10:02 AM, Cristi Dumacristi.d...@aissac.ro wrote: Hi John, I'm playing with it right now, tried some fixes, features and stuff It works for me on a site I'm currently developing Check it out: http://github.com/Aissac/radiant-mailer-extension/tree/master On 7/8/09 6:05 PM, john muhl wrote: has anyone successfully used mailer on 0.8? whenever i try to send mail i get a 500 error page and the following: SQL (1.2ms) SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' SQL (1.9ms) SELECT DISTINCT class_name FROM pages WHERE class_name '' AND class_name IS NOT NULL /!\ FAILSAFE /!\ Wed Jul 08 09:01:58 -0600 2009 Status: 500 Internal Server Error wrong number of arguments (1 for 2) /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `restore_response' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `map' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in `call!' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rewindable_input.rb:25:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:93:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/reloader.rb:9:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/failsafe.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `synchronize' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:106:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/cgi_process.rb:44:in `dispatch_cgi' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib
Re: [Radiant] mailer extension and 0.8
yes, of course. i'm just not convinced it's the proper fix, it just happened to be the most expedient one. here is the diff for the curious: diff --git a/lib/radiant/cache.rb b/lib/radiant/cache.rb index a82..2e16de9 100644 --- a/lib/radiant/cache.rb +++ b/lib/radiant/cache.rb @@ -48,7 +48,7 @@ module Radiant end private - def restore_response(hash, body) + def restore_response(hash, body=nil) # Cribbed from the Rack::Cache source status = hash.delete('X-Status').to_i response = Rack::Cache::Response.new(status, hash, body) On Wed, Jul 8, 2009 at 1:56 PM, Victor Elsendoornelsendo...@w3craft.nl wrote: Only mentioning you fixed it, won't do any help for the Radiant community. Please inform us about the solution or bugs you have found. Thanks in advance. On Jul 8, 2009, at 9:51 PM, john muhl wrote: i went down through the code and think i may have found the issue which appears to be at the radiant level. thanks again for all the help. On Wed, Jul 8, 2009 at 1:10 PM, Cristi Dumacristi.d...@aissac.ro wrote: I created a radiant project with the code from the gist you supplied, and after putting the config.after_initialize block in development.rb worked flawlessly. So is there the possibility that the problem is not in mailer_extension? On 7/8/09 9:58 PM, john muhl wrote: same error with the smtp settings in development.rb On Wed, Jul 8, 2009 at 12:01 PM, Istvan Hokaistvan.h...@gmail.com wrote: Could you try moving the contents of your config.after_initialize block to development.rb or production.rb? -- Istvan Hoka On Wed, Jul 8, 2009 at 8:47 PM, john muhljohnm...@gmail.com wrote: oh, and those results are the same with radiant/mailer or aissac/mailer On Wed, Jul 8, 2009 at 11:43 AM, john muhljohnm...@gmail.com wrote: this is running locally in the development environment. i've tested with webrick, mongrel, thin and passenger and they all have the same error message until you get to server specific part. the test site is the styled blog with only the mailer extension added. all the page parts and environment.rb are here: http://gist.github.com/142995 - i also have mailer.post_to_page? = true set. just to make sure it wasn't inherent in the system i setup a styled blog with 0.7.1 installed mailer, used the same parts and smtp settings and was able to send mail on all 4 servers. thanks for help. On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hokaistvan.h...@gmail.com wrote: John, it looks like you are getting this on your production machine where you are using Thin. Could you test with Passenger or Mongrel, perhaps locally and see if you get the same error? Also, could you provide some more context? For instance, are you trying to attach a file or is it a simple form you are mailing? Cheers! -- Istvan Hoka On Wed, Jul 8, 2009 at 7:34 PM, john muhljohnm...@gmail.com wrote: thanks but it gives the same error. On Wed, Jul 8, 2009 at 10:02 AM, Cristi Dumacristi.d...@aissac.ro wrote: Hi John, I'm playing with it right now, tried some fixes, features and stuff It works for me on a site I'm currently developing Check it out: http://github.com/Aissac/radiant-mailer-extension/tree/master On 7/8/09 6:05 PM, john muhl wrote: has anyone successfully used mailer on 0.8? whenever i try to send mail i get a 500 error page and the following: SQL (1.2ms) SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' SQL (1.9ms) SELECT DISTINCT class_name FROM pages WHERE class_name '' AND class_name IS NOT NULL /!\ FAILSAFE /!\ Wed Jul 08 09:01:58 -0600 2009 Status: 500 Internal Server Error wrong number of arguments (1 for 2) /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `restore_response' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `map' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in `call!' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rewindable_input.rb:25:in `call' /private/tmp/mailer/vendor
Re: [Radiant] mailer extension and 0.8
the issue seems to have resolved itself with radiant edge. On Wed, Jul 8, 2009 at 2:20 PM, john muhljohnm...@gmail.com wrote: yes, of course. i'm just not convinced it's the proper fix, it just happened to be the most expedient one. here is the diff for the curious: diff --git a/lib/radiant/cache.rb b/lib/radiant/cache.rb index a82..2e16de9 100644 --- a/lib/radiant/cache.rb +++ b/lib/radiant/cache.rb @@ -48,7 +48,7 @@ module Radiant end private - def restore_response(hash, body) + def restore_response(hash, body=nil) # Cribbed from the Rack::Cache source status = hash.delete('X-Status').to_i response = Rack::Cache::Response.new(status, hash, body) On Wed, Jul 8, 2009 at 1:56 PM, Victor Elsendoornelsendo...@w3craft.nl wrote: Only mentioning you fixed it, won't do any help for the Radiant community. Please inform us about the solution or bugs you have found. Thanks in advance. On Jul 8, 2009, at 9:51 PM, john muhl wrote: i went down through the code and think i may have found the issue which appears to be at the radiant level. thanks again for all the help. On Wed, Jul 8, 2009 at 1:10 PM, Cristi Dumacristi.d...@aissac.ro wrote: I created a radiant project with the code from the gist you supplied, and after putting the config.after_initialize block in development.rb worked flawlessly. So is there the possibility that the problem is not in mailer_extension? On 7/8/09 9:58 PM, john muhl wrote: same error with the smtp settings in development.rb On Wed, Jul 8, 2009 at 12:01 PM, Istvan Hokaistvan.h...@gmail.com wrote: Could you try moving the contents of your config.after_initialize block to development.rb or production.rb? -- Istvan Hoka On Wed, Jul 8, 2009 at 8:47 PM, john muhljohnm...@gmail.com wrote: oh, and those results are the same with radiant/mailer or aissac/mailer On Wed, Jul 8, 2009 at 11:43 AM, john muhljohnm...@gmail.com wrote: this is running locally in the development environment. i've tested with webrick, mongrel, thin and passenger and they all have the same error message until you get to server specific part. the test site is the styled blog with only the mailer extension added. all the page parts and environment.rb are here: http://gist.github.com/142995 - i also have mailer.post_to_page? = true set. just to make sure it wasn't inherent in the system i setup a styled blog with 0.7.1 installed mailer, used the same parts and smtp settings and was able to send mail on all 4 servers. thanks for help. On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hokaistvan.h...@gmail.com wrote: John, it looks like you are getting this on your production machine where you are using Thin. Could you test with Passenger or Mongrel, perhaps locally and see if you get the same error? Also, could you provide some more context? For instance, are you trying to attach a file or is it a simple form you are mailing? Cheers! -- Istvan Hoka On Wed, Jul 8, 2009 at 7:34 PM, john muhljohnm...@gmail.com wrote: thanks but it gives the same error. On Wed, Jul 8, 2009 at 10:02 AM, Cristi Dumacristi.d...@aissac.ro wrote: Hi John, I'm playing with it right now, tried some fixes, features and stuff It works for me on a site I'm currently developing Check it out: http://github.com/Aissac/radiant-mailer-extension/tree/master On 7/8/09 6:05 PM, john muhl wrote: has anyone successfully used mailer on 0.8? whenever i try to send mail i get a 500 error page and the following: SQL (1.2ms) SELECT name FROM sqlite_master WHERE type = 'table' AND NOT name = 'sqlite_sequence' SQL (1.9ms) SELECT DISTINCT class_name FROM pages WHERE class_name '' AND class_name IS NOT NULL /!\ FAILSAFE /!\ Wed Jul 08 09:01:58 -0600 2009 Status: 500 Internal Server Error wrong number of arguments (1 for 2) /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `restore_response' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `map' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in `invalidate' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in `call!' /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call' /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call' /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call' /private/tmp
Re: [Radiant] xhtml upgrade path
it means nothing for radiant so far as i can tell, or am i missing something? the admin interface's html is not important (to me at least) and you've always been able to build the front end of your site using any markup language you like. On Tue, Jul 7, 2009 at 4:21 AM, Jan M.J. Stormsj...@storms.org wrote: Taken from An Unofficial QA about the Discontinuation of the XHTML2 WG at http://hsivonen.iki.fi/xhtml2-html5-q-and-a/: What’s the upgrade path from XHTML 1.x? For the technical kind of XHTML 1.x—that is, XHTML served as application/ xhtml+xml—the upgrade path is to XHTML5. For the marketing kind of XHTML 1.x—that is, XHTML served as text/html—the upgrade path is to HTML5. Moreover, “HTML5” replaces “XHTML” (and “Ajax”!) as the coolest marketing buzzword. I wonder what this means for Radiant CMS pages. Jan ___ 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