So, given the above, if anyone wants to elaborate on the page just go
ahead. There's lots missing (e.g. better examples of tags and
Behavior-dependent tag descriptions).
It might be better to split it into a series of sub-section pages rather
than all collected together. At least as it stands
Andrew Hodgkinson wrote:
Now for the catch.
Provided all pages using the snippet (via a layout or directly) use the
ERB behaviour, all is well. However, what about a Not Found page or an
archive? That would probably use the same layout as other pages in a
site, which wants directly or via a
Thanks for the clarification. I see now that there was previous
discussion about this not too long ago (in the Informal Competition
thread), so my apologies for that bit of redundancy.
It looks like it would be pretty straightforward to write an export
script which makes
Andrew wrote:
This is what happens when I try to run the database set up.
C:\ruby\lib\ruby\gems\1.8\gems\radiant-0.5.0ruby script/setup_database
production
Run `setup_database --help` for information on additional options.
Loading production environment...OK
WARNING! This script will
Working on the 0.5.1 release this week and scanning through various
patches today.
A patch on ticket 83 adds two filters to Radiant:
* A SmartyPants filter for curling quotes (via RubyPants)
* A Markdown+SmartyPants filter which combines the two
Since Textile curls quotes automatically, my
Sort of unrelated, but you may want to note that right now the Textile filter also filters some Markdown. This is because BlueCloth features some limited support for Markdown syntax, such as links. For example, if you create a page with content
This post uses [textile][1].[1]:
So what you are saying is that by default Redcloth filters both Textile*and* Markdown? And the fix is to use Redcloth::
Textile.new rather thanRedcloth.new ?That'd be it. I'm not sure if Redcloth does *all* of the Markdown
syntax, but it does do some of it (links being the one I know for sure).
I
Let's say I have a page
hierarchy like this:
- about
- publications
- css
- webdesign
- contact
and I use navigation tag in
order to produce top navigation like this:
ul id=topmenu
r:navigation urls=About:
/about; Publications: /publications; Contact: /contact
Here's the relevant parts of a navigation-tab plugin I'm in the process
of hacking together... and I have just successfully called image_path
from it. Hope this helps someone.
class Behavior::Base
define_tags do
tag navtab do |tag|
tab = NavTab.new(tag.attr['label'], @request)
From http://dev.radiantcms.org/radiant/browser/trunk/radiant/app/models/page_context.rb :## r:navigation urls="[Title: url; Title: url; ...]"# r:normala href=""r:title //a/r:normal# r:herestrongr:title //strong/r:here# r:selectedstronga href=""r:title //a/strong/r:selected# r:between |
Hi All,
At my office we have decided to use Radiant for a client's CMS system,
and one of the features we are definitely going to need is page
attachments (or an asset store, either way works). I think John Long
mentioned that Xavier was working on it? I'm just wondering what stage
it's at.
11 matches
Mail list logo
