John W. Long wrote:
Keith Bingman wrote:
_why seems to have other feelings, but this is how it would ideally work
for me.
Could you point me to a url about this?
--
John Long
http://wiseheartdesign.com
I meant to include this, but forgot:
Keith Bingman wrote:
I meant to include this, but forgot:
http://redhanded.hobix.com/inspect/usingRedcloth3.html
He states that you can switch hard breaks on, but when I try this, it
disables paragraphs. Oh well...
I think I'm going to side with _why for now. In the meantime you can
I will be out of the office from Friday August 18th through Wednesday August
23rd, returning on August 24th.
If this is an urgent issue, please contact Jenny Kim:
434-296-1500
[EMAIL PROTECTED]
I will respond to your e-mail on Thursday August 24th.
Thank you,
-Ryan Casey
Hi,
I realize this is a stupid n00b question but I haven't the time this
summer to dedicate towards learning Ruby, RoR, and Radiant that I was
hoping for; I'm hoping kind soul will answer my question instead.
If I use Dreamhost do I need to upgrade to 0.5.2 because of the RoR
security updates?
Erik Mallinson wrote:
I realize this is a stupid n00b question but I haven't the time this
summer to dedicate towards learning Ruby, RoR, and Radiant that I was
hoping for; I'm hoping kind soul will answer my question instead.
If I use Dreamhost do I need to upgrade to 0.5.2 because of the
The hard_breaks bug is even worse than this, I think. When you turn on
hard_breaks it totally ignores all block specifiers except the first one
(http://rubyforge.org/pipermail/redcloth-upwards/2006-June/49.html).
When hard_breaks is on this:
p. 703.289.3820 *tel*
703.359.0952 *fax*
p.
On Aug 18, 2006, at 10:33 AM, Paul Stadig wrote:I for one would rather not insert br/ tags all over my mark up. If Iwas gonna do that I'd just do everything in straight HTML. I like thesimplicity of Textile.I'm with Paul. _why might be wrong in this case.Maybe we could relax the gem spec
John W. Long wrote:
Keith Bingman wrote:
I meant to include this, but forgot:
http://redhanded.hobix.com/inspect/usingRedcloth3.html
He states that you can switch hard breaks on, but when I try this, it
disables paragraphs. Oh well...
I think I'm going to side with _why for now. In
Hi,I don´t know if it works with 0.5.2 simply because I didn´t try it yet, I just upgraded the rails version but still working on an old radiant version.Keith - errors like you get for not attaching a file can be easily taken care of in the code, the code you´re using is more of an example then
John,+1 - Fragment caching would be great!AEMOn 8/17/06, John W. Long [EMAIL PROTECTED] wrote:
Daniel Lyons wrote: Interesting. I wonder if it would be possible to implement a caching
system that could take this into account. Obviously, this isn't a deal breaker. Back to hacking...I'm considering
MarsHall wrote:
RedCloth is focused on Textile formatting (with Markdown practically
as an aside).
I suggest using BlueCloth for Markdown:
http://www.deveiate.org/projects/BlueCloth
Radiant does use BlueCloth for Markdown. We were discussing some
differences between the way RedCloth
Hey guys,
I looked around and it seems like this hasn't been asked before, but
one of my major concerns with Radiant (which I've been using for quite
some time now) is its caching mechanism. Here's my problem:
I plan on deploying RadiantCMS on websites with content that doesn't
change often - it
Frederico Oliveira wrote:
Now for the question: is there a plan to make the caching method used
by Radiant change, or should I patch the application myself? I can
predict many others will be in this situation soon as the application
is considered for real-world use by more and more developers
Erik,
You shouldn't be dependent on Dreamhost (or any other host's) install
of rails as Radiant includes it in the vendor directory by default.
That's a Good Thing and you should follow that practice no matter
where you host to be sure the environment doesn't change out from
under you.
I do host
Hi, I installed the patch yesterday against 0.5.2 and it seemed to
work just fine. Thanks, by the way, it looks like it should work
great.
-Tom
On 8/18/06, dror tirosh [EMAIL PROTECTED] wrote:
Hi,
I don´t know if it works with 0.5.2 simply because I didn´t try it yet, I
just upgraded the
Frederico Oliveira wrote:
Still, giving users the chance to change the ResponseCache expiry
times in, say, a config file would be a safe bet.
Actually, you can do that. Just drop the following in config/environment.rb:
ResponseCache.defaults[:expire_time] = 2.days
There are a couple of
dror tirosh wrote:
Hi,
I don´t know if it works with 0.5.2 simply because I didn´t try it yet,
I
just upgraded the rails version but still working on an old radiant
version.
Keith - errors like you get for not attaching a file can be easily taken
care of in the code, the code you´re using
17 matches
Mail list logo
