order in which regions are rendered
Hello all, I would like to ask what order regions are rendered and how I may be able to control this. In my case, they're not rendering in the order defined in the .info file or the order they're printed in page.tpl.php The reason behind this is that I want a certain block that is generated by a certain module to be numbered based on its appearance inside a page. I'm surprised however, that the block rendered in the body gets a #1 and the one in the header gets #2 although the one in the header was printed before the one in the body and although the header region was declared before the body region in the theme .info file. Would be glad if someone could shed the light on this issue. -- Best Regards, Ashraf Amayreh CEO | O-Minds Cell. 962 78 8099997 Tel. 962 6 5655150 Fax. 962 6 5675150 http://www.o-minds.com web development | web design user experience | branding design
On Thu, Mar 18, 2010 at 5:08 PM, Ashraf Amayreh <mistknight@gmail.com>wrote:
Hello all,
I would like to ask what order regions are rendered and how I may be able to control this. In my case, they're not rendering in the order defined in the .info file or the order they're printed in page.tpl.php
The reason behind this is that I want a certain block that is generated by a certain module to be numbered based on its appearance inside a page. I'm surprised however, that the block rendered in the body gets a #1 and the one in the header gets #2 although the one in the header was printed before the one in the body and although the header region was declared before the body region in the theme .info file.
Have you tried clearing the cache after making changes to the .info file? Just clearing the theme registry is not enough (If I remember correctly) --Jørn
Would be glad if someone could shed the light on this issue.
-- Best Regards, Ashraf Amayreh CEO | O-Minds Cell. 962 78 8099997 Tel. 962 6 5655150 Fax. 962 6 5675150
http://www.o-minds.com web development | web design user experience | branding design
This largely depends on the theme you are using. By default template_preprocess_page(http://api.lullabot.com/template_preprocess_page) should render them in the order in which they are defined on the info file. But your theme may do it differently. ----- ***NEW CELL PHONE # Please Update(See Below)*** Adam A. Gregory Drupal Developer & Consultant Web: AdamAGregory.com Twitter: twitter.com/adamgregory Phone: 910.808.1717 Cell: 919.306.6138 On Thu, Mar 18, 2010 at 2:15 PM, Jørn Fauske <jfauske@gmail.com> wrote:
On Thu, Mar 18, 2010 at 5:08 PM, Ashraf Amayreh <mistknight@gmail.com>wrote:
Hello all,
I would like to ask what order regions are rendered and how I may be able to control this. In my case, they're not rendering in the order defined in the .info file or the order they're printed in page.tpl.php
The reason behind this is that I want a certain block that is generated by a certain module to be numbered based on its appearance inside a page. I'm surprised however, that the block rendered in the body gets a #1 and the one in the header gets #2 although the one in the header was printed before the one in the body and although the header region was declared before the body region in the theme .info file.
Have you tried clearing the cache after making changes to the .info file? Just clearing the theme registry is not enough (If I remember correctly)
--Jørn
Would be glad if someone could shed the light on this issue.
-- Best Regards, Ashraf Amayreh CEO | O-Minds Cell. 962 78 8099997 Tel. 962 6 5655150 Fax. 962 6 5675150
http://www.o-minds.com web development | web design user experience | branding design
Hi The number in the block id comes from the 'delta' used to define the block by the module in hook_block, not the order in which they are rendered. Lee
The reason behind this is that I want a certain block that is generated by a certain module to be numbered based on its >appearance inside a page. I'm surprised however, that the block rendered in the body gets a #1 and the one in the >header gets #2 although the one in the header was printed before the one in the body and although the header region >was declared before the body region in the theme .info file.
Which isn't always even a number... in some modules anyway.... Dave On Mar 18, 2010, at 2:40 PM, Lee Rowlands wrote:
Hi The number in the block id comes from the ‘delta’ used to define the block by the module in hook_block, not the order in which they are rendered. Lee
The reason behind this is that I want a certain block that is generated by a certain module to be numbered based on its appearance inside a page. I'm surprised however, that the block rendered in the body gets a #1 and the one in the >header gets #2 although the one in the header was printed before the one in the body and although the header region >was declared before the body region in the theme .info file.
participants (6)
-
Aaron Winborn -
Adam Gregory -
Ashraf Amayreh -
David Metzler -
Jørn Fauske -
Lee Rowlands