[Radiant] New RedCloth
Have you seen this announcement? http://feeds.feedburner.com/~r/RubyInside/~3/342732232/redcloth-4-released-962.html Apart from dropping of Markdown support (does radiant use it?), it could be interesting to update it. -- Ollivier Robert - ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
OK Chris, I get it now. Ready for you to take a look. Thanks for all of this, by the way. Much appreciated. On Wed, Jul 23, 2008 at 7:14 PM, Chris Parrish [EMAIL PROTECTED] wrote: Marshal Linfoot wrote: Chris, I hope this is what you had in mind...a slimmed down version of what I currently use for the live site. Not quite. That looks like a regular html page and not a css one. To create what I was talking about, do the following: 1. Create a new template\ * Name it: CSS * Expand the more button and change the content-type to: text/css * In the body of the layout, put nothing but: r:content * save the layout 2. Go to your tester page and change its layout to: CSS This should serve up your tester page using text/css mime type and without all the header/footer layout stuff. -Chris -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New RedCloth
How would people feel about switching to a gem dependency on the latest RedCloth (instead of packaging it)? Sean Ollivier Robert wrote: Have you seen this announcement? http://feeds.feedburner.com/~r/RubyInside/~3/342732232/redcloth-4-released-962.html Apart from dropping of Markdown support (does radiant use it?), it could be interesting to update it. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] potential bug in radiant:update on github edge
Yeah, the generator is good about interpreting the ERb but I haven't
added it to the update task yet. We'll definitely fix that before 0.6.8
release.
Sean
Oli Studholme wrote:
Hi All,
Summary: freezing a current project to github edge then doing 'rake
radiant:update' generates a config/environment.rb that contains the
uninterpreted :secret code - apparently this would be a bug in
radiant:update. This also happens with freezing a fresh 0.6.7 to
github edge, but doesn’t with a instance generated from a github clone
(ie clone then bin/radiant -d sqlite3)
On Jul 23, 2008, at 2:49 PM, Alex Wayne wrote:
This has been added to Radiant edge. If you freeze your
vendor/radiant to edge you should have a new defaults.page.filter
config setting you can set to whatever you like.
I froze to Rev 881, but it lacks the changes of the
defaults.page.filter patch[1] from a month ago. Looks like svn is dead
huh. So it’s off to github and a clone into radiant/vendor/radiant.
However doing
rake radiant:update
gave me a config/environment.rb that has this on line 42:
config.action_controller.session = {
:session_key = '_radiant_session',
:secret = % require 'digest/sha1' -%'%=
Digest::SHA1.hexdigest(--#{app_name}--#{Time.now.to_s}--#{rand(1000)}--)
%'
}
which is straight out of the generator[2]. Of course trying 'rake
db:update' after that fails.
My workaround was to copy my old :secret key from environment.bak and
delete the _radiant_session cookies in my browser (I got the error
“CGI::Session::CookieStore::TamperedWithCookie”). 'rake db:update'
then worked as expected. You could also generate a new key using irb[3]
Awaiting flames and being told to fix it my damn self… ;-)
peace - oli
PS the download page is still not in the wiki, and could do with info
on getting edge from github. I also seem to need to do 'rake
production db:migrate' over the mentioned 'rake db:migrate', which
would also be worth noting.
[1]
http://github.com/radiant/radiant/commit/318687e9be167f5b6549a28557ea039bd4651241
[2]
http://github.com/radiant/radiant/tree/master/lib/generators/instance/templates/instance_environment.rb
[3] http://pastie.textmate.org/239873
___
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] SnS extension problem
Yes, you got it right. But I need some help from other Radiant users out there. And, as I mentioned in my other email. This one's serving up with a HTTP/1.1 200 OK response so it looks like SnS could be the culprit. But I have *no* idea where to look in LiteSpeed to find out why it thinks the response should be 404 -- I've never used it. Anyone? Does it have some sort of log or is there a debugging tool? TextAssetResponseCache must be handing over something different than the standard ResponseCache that pages use and LiteSpeed is choking on this difference. But I'm not getting this behavior on my development machine (which uses mongrel to serve up the content). -Chris Marshal Linfoot wrote: OK Chris, I get it now. Ready for you to take a look. Thanks for all of this, by the way. Much appreciated. On Wed, Jul 23, 2008 at 7:14 PM, Chris Parrish [EMAIL PROTECTED] wrote: Marshal Linfoot wrote: Chris, I hope this is what you had in mind...a slimmed down version of what I currently use for the live site. Not quite. That looks like a regular html page and not a css one. To create what I was talking about, do the following: 1. Create a new template\ * Name it: CSS * Expand the more button and change the content-type to: text/css * In the body of the layout, put nothing but: r:content * save the layout 2. Go to your tester page and change its layout to: CSS This should serve up your tester page using text/css mime type and without all the header/footer layout stuff. -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Forum extension?
On Sat, Jul 12, 2008 at 12:05 PM, Casper Fabricius [EMAIL PROTECTED] wrote: Now I remember the other reason I never got around to making the Beast extension ready for public use. I wrote it for a community site, and I put most of the user stuff and all the login/session stuff in another extension, which is specific to the application. So the extension is nowhere near to drop-in usage in a standard Radiant installation, but feel free to look at it here: http://casperfabricius.com/files/beast.zip I can provide samples of users- and session-controllers as well as further needed extensions of the Radiant login system if needed, but it will still take a fair amount of work to get it running. Cheers, Casper So I wasn't able to use Beast, and rolling my own was too much of a headache. I just setup a invitation-only Google Group and called it a day. Thanks for the suggestions, everyone. -- Tim ___ 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 RedCloth
I'm fine with it. Looks like a good improvement too. Now all we need is a better Markdown parser. -Chris Sean Cribbs wrote: How would people feel about switching to a gem dependency on the latest RedCloth (instead of packaging it)? Sean Ollivier Robert wrote: Have you seen this announcement? http://feeds.feedburner.com/~r/RubyInside/~3/342732232/redcloth-4-released-962.html Apart from dropping of Markdown support (does radiant use it?), it could be interesting to update 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] New RedCloth
Someone was working on a branch that uses rdiscount, an improved Markdown parser. Sean Chris Parrish wrote: I'm fine with it. Looks like a good improvement too. Now all we need is a better Markdown parser. -Chris Sean Cribbs wrote: How would people feel about switching to a gem dependency on the latest RedCloth (instead of packaging it)? Sean Ollivier Robert wrote: Have you seen this announcement? http://feeds.feedburner.com/~r/RubyInside/~3/342732232/redcloth-4-released-962.html Apart from dropping of Markdown support (does radiant use it?), it could be interesting to update 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 ___ 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 RedCloth
It's a bit of a detour from Radiant being geared toward shared hosting. John Muhl is working on a branch than uses RDiscount (which is a better Markdown parser). http://github.com/johnmuhl/radiant/tree/markdown On Jul 24, 2008, at 11:05 AM, Chris Parrish wrote: I'm fine with it. Looks like a good improvement too. Now all we need is a better Markdown parser. -Chris Sean Cribbs wrote: How would people feel about switching to a gem dependency on the latest RedCloth (instead of packaging it)? Sean Ollivier Robert wrote: Have you seen this announcement? http://feeds.feedburner.com/~r/RubyInside/~3/342732232/redcloth-4- released-962.html Apart from dropping of Markdown support (does radiant use it?), it could be interesting to update it. Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New RedCloth
I understood discoount to be *nix only (no Windows). I'll have to look into it further. -Chris Jim Gay wrote: It's a bit of a detour from Radiant being geared toward shared hosting. John Muhl is working on a branch than uses RDiscount (which is a better Markdown parser). http://github.com/johnmuhl/radiant/tree/markdown On Jul 24, 2008, at 11:05 AM, Chris Parrish wrote: I'm fine with it. Looks like a good improvement too. Now all we need is a better Markdown parser. -Chris Sean Cribbs wrote: How would people feel about switching to a gem dependency on the latest RedCloth (instead of packaging it)? Sean Ollivier Robert wrote: Have you seen this announcement? http://feeds.feedburner.com/~r/RubyInside/~3/342732232/redcloth-4-released-962.html Apart from dropping of Markdown support (does radiant use it?), it could be interesting to update it. Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New RedCloth
That was my main concern... I'd like to continue packaging the library with Radiant, but it is no longer pure-Ruby and must be compiled. That said, RubyGems has greatly improved since we started down this road. Sean Jim Gay wrote: It's a bit of a detour from Radiant being geared toward shared hosting. John Muhl is working on a branch than uses RDiscount (which is a better Markdown parser). http://github.com/johnmuhl/radiant/tree/markdown On Jul 24, 2008, at 11:05 AM, Chris Parrish wrote: I'm fine with it. Looks like a good improvement too. Now all we need is a better Markdown parser. -Chris Sean Cribbs wrote: How would people feel about switching to a gem dependency on the latest RedCloth (instead of packaging it)? Sean Ollivier Robert wrote: Have you seen this announcement? http://feeds.feedburner.com/~r/RubyInside/~3/342732232/redcloth-4-released-962.html Apart from dropping of Markdown support (does radiant use it?), it could be interesting to update it. Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New RedCloth
On 2008/07/24, at 07:44, Sean Cribbs wrote: How would people feel about switching to a gem dependency on the latest RedCloth (instead of packaging it)? I think it's going to have to happen at some point unless Radiant wants to keep using the same old text parsing libraries from 2004/2005. Waiting for the pure ruby libraries catch back up is the other (wishful) option. On 2008/07/24, at 09:31, Chris Parrish wrote: I understood discoount to be *nix only (no Windows). I'll have to look into it further. That's right. Although there isn't anything really stopping it from being compiled for windows with mingw just like they did RedCloth 4; except of course finding people who use windows to do the work :) There is also PEG markdown (rpeg-markdown in ruby land) but right now it is completely unusable on big (huge?) spans of text and I'm not sure it's any easier to get running in windows. Personally, I'd rather have a PEG based Markdown than a Discount based one. As far as getting a new Markdown parser into core I'd say don't even bother yet. As has been stated Discount doesn't (yet) run on windows, and PEG Markdown is crashy (and probably doesn't run on windows either). I would definitely like to see Radiant upgrade to RedCloth 4 sometime soon. If no one jumps up to take it on in the next week, I'll try to get it running then. p.s. I did put together a standalone Markdown filter that uses rdiscount, so if you can install gems and don't run windows you can use that until something better is in the core. I use it on live sites with no problems (some were even started with the standard Markdown filter and upgraded without issue). http://github.com/johnmuhl/radiant-markdown-extension ___ 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 RedCloth
I saw somewhere that Luis Lavena was researching porting rDiscount to Windows but also that it didn't look good (discount depends on some *nix only libraries, I think) Hopefully I'm wrong, though. Either way, I didn't mean to hijack a thread. New Redcloth for all! -Chris john muhl wrote: On 2008/07/24, at 07:44, Sean Cribbs wrote: How would people feel about switching to a gem dependency on the latest RedCloth (instead of packaging it)? I think it's going to have to happen at some point unless Radiant wants to keep using the same old text parsing libraries from 2004/2005. Waiting for the pure ruby libraries catch back up is the other (wishful) option. On 2008/07/24, at 09:31, Chris Parrish wrote: I understood discoount to be *nix only (no Windows). I'll have to look into it further. That's right. Although there isn't anything really stopping it from being compiled for windows with mingw just like they did RedCloth 4; except of course finding people who use windows to do the work :) There is also PEG markdown (rpeg-markdown in ruby land) but right now it is completely unusable on big (huge?) spans of text and I'm not sure it's any easier to get running in windows. Personally, I'd rather have a PEG based Markdown than a Discount based one. As far as getting a new Markdown parser into core I'd say don't even bother yet. As has been stated Discount doesn't (yet) run on windows, and PEG Markdown is crashy (and probably doesn't run on windows either). I would definitely like to see Radiant upgrade to RedCloth 4 sometime soon. If no one jumps up to take it on in the next week, I'll try to get it running then. p.s. I did put together a standalone Markdown filter that uses rdiscount, so if you can install gems and don't run windows you can use that until something better is in the core. I use it on live sites with no problems (some were even started with the standard Markdown filter and upgraded without issue). http://github.com/johnmuhl/radiant-markdown-extension ___ 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] Need Radiant Consultants
Hello: I am looking for experienced radiant developer for building extensions. I would appreciate if you could send me some information about your day rate, reference and availability directly to me. We need to build 2 extension. I look forward to hear from you. Regards Zaheed Haque [EMAIL PROTECTED] -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: [ANN] Summer Reboot Documentation
Mohit: I looked at the existing documentation! Great work. I am willing to fund some of the activity if that will speed up things. I have a need of such documentation in September. Feel free to contact if you are interested. Cheers Zaheed Haque [EMAIL PROTECTED] -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
