Re: [development] Change order of title and body fields
BTW, it would be so easy to be able to move body and title (and taxonomy) in the CCK configuration screen (they have fixed weight)
[moved to dev] Answering to myself, I looked in the CCK code, and the weights of body and title are not managed there. I think this is the responsibility of core, but where is it ? I couldn't find documentation on this. Currently, the weights are hardcoded title : -5 taxonomy : -3 body: 0 and you can't put those inside cck groups. Is there plan to change this / is it possible ? Thank you Philippe
adrian rossouw wrote:
On 27 Nov 2007, at 11:27 AM, Philippe Jadin wrote:
Is there plan to change this / is it possible ?
check out panels and it's new context feature.
That's a little more fine grained than Panels lets you do right now, unfortunately.
On Nov 28, 2007 5:14 AM, Earl Miles <merlin@logrus.com> wrote:
check out panels and it's new context feature.
That's a little more fine grained than Panels lets you do right now, unfortunately.
I think in a perfect world, those weights dropdown menu should not be disabled (and should not require an additional module). I'd like to help fix this, but I need some pointers as this seems deeply rooted in core. Is it a good idea to try to fix this, or is it something not desirable ? Thank you Philippe
Philippe, just a warning As I understand it, on node pages, eg. node/x, the title is applied as part of the page template - which therefore will not be altered by weight only. I always assumed that this is why title is greyed out. .s On Nov 28, 2007 7:42 PM, Philippe Jadin <philippe.jadin@gmail.com> wrote:
On Nov 28, 2007 5:14 AM, Earl Miles <merlin@logrus.com> wrote:
check out panels and it's new context feature.
That's a little more fine grained than Panels lets you do right now, unfortunately.
I think in a perfect world, those weights dropdown menu should not be disabled (and should not require an additional module). I'd like to help fix this, but I need some pointers as this seems deeply rooted in core.
Is it a good idea to try to fix this, or is it something not desirable ?
Thank you
Philippe
participants (4)
-
adrian rossouw -
Earl Miles -
Philippe Jadin -
Simon Hobbs