On Jan 5, 9:11 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
Thanks AD7six - just for my education, is this:
> On Jan 4, 10:07 am, "[EMAIL PROTECTED]"
> <[EMAIL PROTECTED]> wrote:
> > other parts of each layout can contain different
> > static content, elements (echo $this->renderElement
Thanks AD7six - just for my education, is this:
On Jan 4, 10:07 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> other parts of each layout can contain different
> static content, elements (echo $this->renderElement('my_element') ) ,
> request actions (echo $this->requestAction(params) ) or
Hi All,
On Jan 4, 10:07 am, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
other parts of each layout can contain different
static content, elements (echo $this->renderElement('my_element') ) ,
request actions (echo $this->requestAction(params) ) or plain old php.
Not strictly accurate ;) So
Daniel Gomes wrote:
you just have to create one layout, the default layout. Then you just
to have to create the views files that only have the content.
It's perfectly OK to have multiple layouts. Although the 'interesting'
bit (from a user perspective) can only be rendered by echo
$content_fo
Hi,
I think you're looking for elements. You can render elements within your
layout, such as a menu, search, etc. Your $content-for_layout is the content
that is to go within the layout for the page. That variable will be set to
the content of the view that was rendered.
Only make new layouts w
Hi, i hope help you lets see:
-> When do I need to create new layouts?
you just have to create one layout, the default layout. Then you just
to have to create the views files that only have the content.
-> How is the $content_for_layout supposed to work?
the $content_for_layout works like a c
Sorry for not being clear!
What I really am looking for, is a way to substitute the "usual
(old-fashioned) php practice" of including content based on i.e. GET
variables.
What is the counterpart in CakePHP and what is the BEST practice (...
or at least a good one ...)?
In detail:
-> When shou
As aforementioned, more info is really needed. But I think you will
only need one layout, you can use two views. One with two columns and
one with three.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" g
The layout should be based on which page they navigate to.
But there must me an option to have dynamic content in several columns
etc.
On 3 Jan, 22:25, "ShepherdWeb" <[EMAIL PROTECTED]> wrote:
Are you saying that the user would get to choose which layout they
wanted, or is the layout chosen for
Are you saying that the user would get to choose which layout they
wanted, or is the layout chosen for them based on which page they
navigate to?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To
As a newbie, I am having a hard time grasping "MVC thinking" and how to
structure my application.
Lets say I would like a website with this structure:
???
... where "???" could be i.e. a 2 or 3 column layout with dynamic data
in each column.
Which is the best al
11 matches
Mail list logo
