I'd also like to see the option of leaving
behind a redirect action to maintain cool uris.
I think it should be easy enough to write a tag for doing redirects...
(You don't need a special kind of redirect page, you can just create a
new page and insert this tag). Or perhaps this tag should
If you start typing into this box, it becomes an AJAX-y auto-complete
box with the names of pages whose page name or url matches what you are
typing...
when you select a parent, the full url is shown in the text box.
The issue with separating parenting from ordering is twofold:
1.) Two
Do we all think that re-ordering and re-parenting should be part of the
core of radiant, or an extension?
How, in general, do we ever decide this sort of thing?
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post:
Jacob Burkhart wrote:
Do we all think that re-ordering and re-parenting should be part of the
core of radiant, or an extension?
How, in general, do we ever decide this sort of thing?
Generally, I just make a decision and people live with it. :-)
Specifically, I try and listen to other
I think it should be easy enough to write a tag for doing
redirects...
(You don't need a special kind of redirect page, you can
just create a
new page and insert this tag). Or perhaps this tag should
actually be
provided by a custom page type...
Since the changes that we're
Hi Adam,
A couple of thoughts-
I think you described something similar to what acts_as_list does - adds a
position int field.
Drag-n-drop-
In mental, front-end drag can be accomplished by making two changes to
views/admin/page/index.rhtml:
tbody id=list
and anywhere at the bottom of the page:
With all due respect, I agree with Jacob. Everything discussed so far
sounds like a hack. Let's bat around what the right solution is a
little longer before worrying about how it's going to be done. Here
are the possible ways I see, in order of preference (see that's an
arbitrary ordering
Ahh, attempting to implement 2 features at once? re-ordering as well as
parent/hierarchy changing?
While we're solving other problems at the same time, what about the
problem of too many pages? The secondary screen we use for re-ordering,
could also be the secondary screen we use to display
On 1/30/07, Jacob Burkhart [EMAIL PROTECTED] wrote:
Ahh, attempting to implement 2 features at once? re-ordering as well as
parent/hierarchy changing?
(snipped a bunch)
#199 actually has a patch that does re-ordering quite well (some
assembly required, but I'm using it on a few sites). As it
Does anyone else appreciate the ability to re-parent nodes as a great
asset for Radiant as a site planning tool (http://
www.sparrowstyle.com/blog/comments/radiant_as_a_site_planning_tool --
not my article, but I agree).
I had used the patch initially and got so annoyed with the
John W. Long wrote:
Loren Johnson wrote:
I don't currently feel qualified to work-up a new patch nor improve
the existing one, but I've got $$$ (seriously) for the first one to
do it well enough to get it included in a core release.
I have a client who wants to help foot the bill for
John,
This looks good to me. I may have preferred to not going to a
separate screen but don't really have any objection to it either --
this works for me.
I'm very happy to see the default sort order priority beginning with
position.
Thanks for putting this out there, it's great to see
Daniel Sheppard wrote:
What happened to the original work of changing the page list to be
ul's and li's and just directly allowing sorting there? I remember
things moving enthusiastically in that direction but then falling off
the radar. Were there issues with making it render properly
I know there is a lot of built in support for sorting lists in Rails,
but I'm still hoping a solution can be pulled together that's not too
complicated and uses a tables.
I've looked at some of the other sorting patches, but they seem to be
incompatible with mental.
Well, the changing
How can you order pages under a r:children:each ?
I can see the by parameter but what does that amount to?
I can see that it could be the title or the publication date, but what I'm
trying to do is a a bit different that that.
Let me express it as a general problem.
Can I do something like
Sean Cribbs said the following on 01/26/2007 08:08 AM:
You can order by any field on the 'pages' table/ Page model.
Right.
I see that in the documentation, but beyond 'title' and when it was
published, what constitutes a field? I really don't want to pour
backwards and forwards though the
Anton,
Even though Radiant has evolved fairly quickly, the fact is that it is
a work in process which, in turn, means that many times people have to
hack their work-arounds to get stuff working the way they want. So, if
there's a specific task that you cannot concieveably accomplish with
existing
+1 on ordering.
More about my need:
Creating a product catalog site. Using f:find, r:children:each throughout the
site to produce HTML and XML pages. Client really particular about ordering of
the Product pages. Unfortunately, product pages cannot use existing fields for
ordering, e.g.
On 1/26/07, Anton J Aylward [EMAIL PROTECTED] wrote:
How can you order pages under a r:children:each ?
WhatI've done is to (ab)use the slug field and putting a number there.
Then by=slug order=asc does the sorting.
--
Ollivier Robert -
___
Radiant
This has got my fervent vote.
I'll try and not go on and on... but...
For every of the 5 or 6 sites I've now put up in Radiant sorting was
a requirement that I have had to work around not having. It seems
like it'd be a very natural addition to what Radiant is.
Mostly the workarounds have
Would like to add my vote for this too, there have been a few cases where
I've had to use the numbered slug workaround even though it produces ugly
urls.
Kev
On 1/26/07, Loren Johnson [EMAIL PROTECTED] wrote:
This has got my fervent vote.
I'll try and not go on and on... but...
For every
Loren Johnson wrote:
I don't currently feel qualified to work-up a new patch nor improve
the existing one, but I've got $$$ (seriously) for the first one to
do it well enough to get it included in a core release.
I have a client who wants to help foot the bill for this. Contact me
22 matches
Mail list logo
