disable the extension in environment.rb
What's the easiest way to remove, say, Textile as a supported markup
language?
-dan
On Tue, Feb 1, 2011 at 8:28 AM, William Ross wrote:
If I was trying to give it a sane IA I wouldn't publish the calendar using a
> blog-history extension in the first place :)
>
Yeah, well we do what we can with what we've been handed. :-\
I do think there's an architectural flaw in the Archiv
On 1 Feb 2011, at 15:50, D.Kreft wrote:
> On Tue, Feb 1, 2011 at 6:43 AM, William Ross wrote:
>
> I don't use the archive extension but my feeling here is that the logic in
> the model is right and your url scheme is twisting things a bit out of shape.
> Any reason not to use /events/city/
On Tue, Feb 1, 2011 at 6:43 AM, William Ross wrote:
I don't use the archive extension but my feeling here is that the logic in
> the model is right and your url scheme is twisting things a bit out of
> shape. Any reason not to use /events/city//MM/DD? Then the slug
> constraint would be helpi
On 1 Feb 2011, at 14:13, D.Kreft wrote:
> I'm using an old version of Radiant (0.6.7) [1] but I think this behavior
> still exists in tip as well based upon what I see in github [2].
>
> My customer has a bunch of events in various cities across the world this
> year that they want to publish v
I'm using an old version of Radiant (0.6.7) [1] but I think this behavior
still exists in tip as well based upon what I see in github [2].
My customer has a bunch of events in various cities across the world this
year that they want to publish via our CMS. So the natural and most
convenient thing
I eventually found a solution that worked better for me.
The subdomain-fu gem seems like the best way to go. That gave me
access to a method called "current_subdomain" which I then used in a
custom tag to conditionally display my header graphic, based on
subdomain. Works great if you need to brand
