To those interested, I've found a solution after being hit on the head
one time too much by the sentence "if the body page part is not found
here, radiant will try to find it in the parent"...
It seems also to "fix" the ruby calls stack overflow caused by the way
I did the thing before.
I now hav
On 9/1/06, Ollivier Robert <[EMAIL PROTECTED]> wrote:
> I'm now getting repeatable ruby/mongrel crashes while rendering my
> pages. Only the "test" one but instant mongrel death with
>
> zsh: illegal hardware
> instruction (core dumped) mongrel_rails start -e production
> -B
Wit
On 9/1/06, Sean Cribbs <[EMAIL PROTECTED]> wrote:
> You can specify by="attribute" on the children:each tag, which lets you pick
> the attribute to sort by, which I'm assuming are any attributes of the Page
> model.
Found that by looking at the code but...
I'm now getting repeatable ruby/mongrel
Ollivier,You can specify by="attribute" on the children:each tag, which lets you pick the attribute to sort by, which I'm assuming are any attributes of the Page model.Sean Cribbs
seancribbs.comOn 9/1/06, Ollivier Robert <[EMAIL PROTECTED]> wrote:
On 9/1/06, Ollivier Robert <[EMAIL PROTECTED]> wrot
On 9/1/06, Ollivier Robert <[EMAIL PROTECTED]> wrote:
> When using such code as
>
> -
> -
Make that
-
-
Sorry.
--
Ollivier Robert -
___
Radiant mailing list
Radiant@lists.radiantcms.org
http://lists.radiantcms.org/mailman/listi
When using such code as
-
-
I can specify order="asc" or order="desc" but what if I want an
arbitrary order? In the admin section, pages are ordered according to
what I guess is the order of creation (page ID). I can not change the
order itself (which would solve my problem).
Any idea?
