| # |
Aug 6th 2008, 22:12 |
cobol |
if it has sub-children, change behavior, or vice versa |
| # |
Aug 6th 2008, 22:12 |
cobol |
i'd just run checks on the data array |
| # |
Aug 6th 2008, 22:12 |
nymacro |
no worries |
| # |
Aug 6th 2008, 22:12 |
cobol |
sorry, it took me a while to get your problem |
| # |
Aug 6th 2008, 22:12 |
cobol |
the nesting behavior is explicit to support the automatic relationships |
| # |
Aug 6th 2008, 22:12 |
cobol |
really only with a custom query, from what i know |
| # |
Aug 6th 2008, 22:11 |
nymacro |
Just wondering if there is a way to make it keep the same form |
| # |
Aug 6th 2008, 22:11 |
nymacro |
basically, from one place, i use $post['id'], and another it is $post['Post']['id'] |
| # |
Aug 6th 2008, 22:11 |
nymacro |
post element: http://bin.cakephp.org/view/65675558 |
| # |
Aug 6th 2008, 22:10 |
nymacro |
*element |
| # |
Aug 6th 2008, 22:10 |
nymacro |
oh, forgot to put in the elemtn |
| # |
Aug 6th 2008, 22:10 |
nymacro |
that is the views |
| # |
Aug 6th 2008, 22:10 |
nymacro |
http://bin.cakephp.org/view/432638033 |
| # |
Aug 6th 2008, 22:08 |
cobol |
code? |
| # |
Aug 6th 2008, 22:07 |
nymacro |
I can't use the same template unless I manually modify the representation |
| # |
Aug 6th 2008, 22:06 |
nymacro |
So I want to reuse the one element for both controllers/views |
| # |
Aug 6th 2008, 22:06 |
nymacro |
Sorry, let me clarify; I have an element which renders a post, and I want to use it both for post view, and for topic viewing all posts |
| # |
Aug 6th 2008, 22:06 |
cobol |
i dont really know |
| # |
Aug 6th 2008, 22:06 |
cobol |
i think? |
| # |
Aug 6th 2008, 22:05 |
cobol |
i would wager because your controller explicitly uses('Post')? |
| # |
Aug 6th 2008, 22:05 |
Jezek |
gotcha |
| # |
Aug 6th 2008, 22:05 |
nymacro |
in regards to [Post] |
| # |
Aug 6th 2008, 22:05 |
nymacro |
can anyone tell my why CakePHP behaves like this: http://bin.cakephp.org/view/1570690605 |
| # |
Aug 6th 2008, 22:04 |
cobol |
the action takes the data and passes it to the view |
| # |
Aug 6th 2008, 22:04 |
cobol |
from the action |
| # |
Aug 6th 2008, 22:04 |
cobol |
and calling on that component |
| # |
Aug 6th 2008, 22:04 |
cobol |
Jezek: by putting the application logic that fetches it into a component |
| # |
Aug 6th 2008, 22:04 |
achew22 |
rar.... |
| # |
Aug 6th 2008, 22:03 |
Jezek |
but how do i get the data into the element without using requestAction |
| # |
Aug 6th 2008, 22:03 |
cobol |
and the component is application logic |
| # |
Aug 6th 2008, 22:03 |
cobol |
so helpers and elements become the view logic code |
| # |
Aug 6th 2008, 22:03 |
nymacro |
hmmm |
| # |
Aug 6th 2008, 22:03 |
cobol |
it's basically the same thing, except for reusable code |
| # |
Aug 6th 2008, 22:03 |
Jezek |
yes |
| # |
Aug 6th 2008, 22:03 |
cobol |
well you know how in MVC, application logic goes in the controller, and view logic in the views? |
| # |
Aug 6th 2008, 22:02 |
Jezek |
not really |
| # |
Aug 6th 2008, 22:02 |
cobol |
does that all make sense? |
| # |
Aug 6th 2008, 22:02 |
Jezek |
oh ok |
| # |
Aug 6th 2008, 22:02 |
cobol |
*becomes |
| # |
Aug 6th 2008, 22:02 |
cobol |
and it because a black box to the controller's action |
| # |
Aug 6th 2008, 22:01 |
cobol |
you could then also easily integrate data caching in the component |