subject:"Understanding"

3.0 Tree Behavior - understanding find('treeList')

2014-07-11 Thread Michael Houghton

I am using the 3.0 Tree Behavior.

I have the following from the docs:

$pages = $this-Pages-find('treeList');

http://book.cakephp.org/3.0/en/core-libraries/behaviors/tree.html

This just doesn't feel right.  It isn't returning a list at all.  Should I 
be doing something else, like:

$pages = $this-Pages-find('treeList')-all();

It just feels like I am missing something here.

When I put my $pages variable into my 'options' = $pages for my form 
select, I get the following error:

*Error: * Function name must be a string 
*File* 
/home/michael/public_html/bettornet/vendor/cakephp/cakephp/src/Collection/Iterator/TreePrinter.php
 

*Line: * 77

Any help with this would be appreciated.

Thanks in advance.
Michael

-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.

Re: 3.0 Tree Behavior - understanding find('treeList')

2014-07-11 Thread José Lorenzo

Not sure what you mean with  It isn't returning a list at all. Can you 
explain?

On Friday, July 11, 2014 9:47:27 AM UTC+2, Michael Houghton wrote:

 I am using the 3.0 Tree Behavior.

 I have the following from the docs:

 $pages = $this-Pages-find('treeList');

 http://book.cakephp.org/3.0/en/core-libraries/behaviors/tree.html

 This just doesn't feel right.  It isn't returning a list at all.  Should I 
 be doing something else, like:

 $pages = $this-Pages-find('treeList')-all();

 It just feels like I am missing something here.

 When I put my $pages variable into my 'options' = $pages for my form 
 select, I get the following error:

 *Error: * Function name must be a string 
 *File* 
 /home/michael/public_html/bettornet/vendor/cakephp/cakephp/src/Collection/Iterator/TreePrinter.php
  

 *Line: * 77

 Any help with this would be appreciated.

 Thanks in advance.
 Michael


-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.

Re: 3.0 Tree Behavior - understanding find('treeList')

2014-07-11 Thread Michael Houghton

Hey Jose

Sure thing.  This seems like a similar issue that I had with:

$this-Models-findByField($name)-first();

If you recall, I missed the - first() and was trying:

$this-Models-findByField($name);

Which just gives a whole lot of data on the schema.

With the tree behavior, I am calling:

$pages = $this-Pages-find('treeList');
pr($pages); die;

But again, it is giving me a lot of schema stuff.  I checked the docs, but 
it only mentions what I did - how to a build the list here - in 2.x we 
would do:

$this-Page-generateTreeList();

I want to build the same list in 3.0!

Do you have any idea what I could be missing?

Thanks again for your help - I am slowly getting my head around this!

On Friday, July 11, 2014 9:18:08 AM UTC+1, José Lorenzo wrote:

 Not sure what you mean with  It isn't returning a list at all. Can you 
 explain?



-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.

Re: 3.0 Tree Behavior - understanding find('treeList')

2014-07-11 Thread José Lorenzo

All find() methods returns a query object. All query objects have a first() 
and toArray() method. If you want to see the results of your find you can 
do:

$pages = $this-Pages-find('treeList')-toArray();

On Friday, July 11, 2014 10:28:58 AM UTC+2, Michael Houghton wrote:

 Hey Jose

 Sure thing.  This seems like a similar issue that I had with:

 $this-Models-findByField($name)-first();

 If you recall, I missed the - first() and was trying:

 $this-Models-findByField($name);

 Which just gives a whole lot of data on the schema.

 With the tree behavior, I am calling:

 $pages = $this-Pages-find('treeList');
 pr($pages); die;

 But again, it is giving me a lot of schema stuff.  I checked the docs, but 
 it only mentions what I did - how to a build the list here - in 2.x we 
 would do:

 $this-Page-generateTreeList();

 I want to build the same list in 3.0!

 Do you have any idea what I could be missing?

 Thanks again for your help - I am slowly getting my head around this!

 On Friday, July 11, 2014 9:18:08 AM UTC+1, José Lorenzo wrote:

 Not sure what you mean with  It isn't returning a list at all. Can you 
 explain?



-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.

Re: 3.0 Tree Behavior - understanding find('treeList')

2014-07-11 Thread Michael Houghton

Thanks Jose - that seems to be it! It might be worth updating the Tree docs 
to show this.

Unfortunately, that is still giving me the error:

*Error: * Function name must be a string 
*File* 
/home/michael/public_html/bettornet/vendor/cakephp/cakephp/src/Collection/Iterator/TreePrinter.php
 


Any idea what this could be?

Thanks again.

On Friday, July 11, 2014 10:24:30 AM UTC+1, José Lorenzo wrote:

 All find() methods returns a query object. All query objects have a 
 first() and toArray() method. If you want to see the results of your find 
 you can do:

 $pages = $this-Pages-find('treeList')-toArray();




-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.

Re: 3.0 Tree Behavior - understanding find('treeList')

2014-07-11 Thread José Lorenzo

Can you gist your full code, I have no idea what that error is.

On Friday, July 11, 2014 11:49:40 AM UTC+2, Michael Houghton wrote:

 Thanks Jose - that seems to be it! It might be worth updating the Tree 
 docs to show this.

 Unfortunately, that is still giving me the error:

 *Error: * Function name must be a string 
 *File* 
 /home/michael/public_html/bettornet/vendor/cakephp/cakephp/src/Collection/Iterator/TreePrinter.php
  


 Any idea what this could be?

 Thanks again.

 On Friday, July 11, 2014 10:24:30 AM UTC+1, José Lorenzo wrote:

 All find() methods returns a query object. All query objects have a 
 first() and toArray() method. If you want to see the results of your find 
 you can do:

 $pages = $this-Pages-find('treeList')-toArray();




-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.

Re: 3.0 Tree Behavior - understanding find('treeList')

2014-07-11 Thread Michael Houghton

Hey Jose

Here it is:
https://gist.github.com/cakecoded/59511a440dfb9c5c7628

On Friday, July 11, 2014 12:44:56 PM UTC+1, José Lorenzo wrote:

 Can you gist your full code, I have no idea what that error is.

 On Friday, July 11, 2014 11:49:40 AM UTC+2, Michael Houghton wrote:

 Thanks Jose - that seems to be it! It might be worth updating the Tree 
 docs to show this.

 Unfortunately, that is still giving me the error:

 *Error: * Function name must be a string 
 *File* 
 /home/michael/public_html/bettornet/vendor/cakephp/cakephp/src/Collection/Iterator/TreePrinter.php
  


 Any idea what this could be?

 Thanks again.

 On Friday, July 11, 2014 10:24:30 AM UTC+1, José Lorenzo wrote:

 All find() methods returns a query object. All query objects have a 
 first() and toArray() method. If you want to see the results of your find 
 you can do:

 $pages = $this-Pages-find('treeList')-toArray();




-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.

Re: 3.0 Tree Behavior - understanding find('treeList')

2014-07-11 Thread José Lorenzo

I cannot reproduce this issue. What PHP version do you have? Can you paste 
the the contents of the line where it is throwing the fatal error?

On Friday, July 11, 2014 2:28:11 PM UTC+2, Michael Houghton wrote:

 Hey Jose

 Here it is:
 https://gist.github.com/cakecoded/59511a440dfb9c5c7628

 On Friday, July 11, 2014 12:44:56 PM UTC+1, José Lorenzo wrote:

 Can you gist your full code, I have no idea what that error is.

 On Friday, July 11, 2014 11:49:40 AM UTC+2, Michael Houghton wrote:

 Thanks Jose - that seems to be it! It might be worth updating the Tree 
 docs to show this.

 Unfortunately, that is still giving me the error:

 *Error: * Function name must be a string 
 *File* 
 /home/michael/public_html/bettornet/vendor/cakephp/cakephp/src/Collection/Iterator/TreePrinter.php
  


 Any idea what this could be?

 Thanks again.

 On Friday, July 11, 2014 10:24:30 AM UTC+1, José Lorenzo wrote:

 All find() methods returns a query object. All query objects have a 
 first() and toArray() method. If you want to see the results of your find 
 you can do:

 $pages = $this-Pages-find('treeList')-toArray();




-- 
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP

--- 
You received this message because you are subscribed to the Google Groups 
CakePHP group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cake-php+unsubscr...@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/d/optout.

Re: Understanding MVC Architecture

2012-04-24 Thread lowpass

I think there are no hard and fast rules for this. I've done that in
the past where it seems to make sense to list the associated model
data from a particular controller. If all you want to do is list the
Members of a given Organization -- and not provide links to do
anything further with a given Member -- then it might be fine to put
the action in OrganizationsController. However, I'll generally create
a controller for the other model(s), if only for admin functions. In
your case, you may have a need for an admin to create a new
OrganizationRole, for example.

On Sun, Apr 22, 2012 at 12:45 PM, bs28723
bill.sto...@boosterwebsolutions.com wrote:
 My question is - Is it a better MVC architecture to have a 1 to 1
 relationship for a controller to access the model and the view, or since
 in a case where all relationships stem from a single model - just make
 the one controller have all the actions, but pull data from the related
 models needed together to then send to a view.

 Here is some code to help illustrate what I am talking about. ( I
 removed a lot of configuration details, because it is not relevant for
 the architecture discussion)

 Organization Model
      $hasMany = array('OrganizationRole', 'Address', 'MemberRelationship');
      $belongsTo = array('User');

 OrganizationRole Model
      $hasMany = array('OrganizationPermission', 'MemberRelationship');
      $belongsTo = array('Organization');

 MemberRelationship Model
      $belongsTo = array('Organization', 'User', 'MembershipLevel',
 'OrganizationRole');

 OrganizationPermission Model
     $belongsTo = array('OrganizationRole');

 User Model
      $hasMany = array('Organization', 'MemberRelationship', 'Address');


 So, as you can see, everything is related to Organization either
 directly or indirectly.  So, I am thinking of adding actions to
 OrganizationsController to do things like viewMembers, editMembers,
 deleteMembers, viewRoles, editRoles, assignRoles, etc
 rather than putting calling view, edit, delete actions in
 MemberRelationshipsController and OrganizationRolesControllers.

 Any thoughts? Opinions? Suggestions?

 Thanks,
 Bill

 
 View this message in context: Understanding MVC Architecture
 Sent from the CakePHP mailing list archive at Nabble.com.

 --
 Our newest site for the community: CakePHP Video Tutorials
 http://tv.cakephp.org
 Check out the new CakePHP Questions site http://ask.cakephp.org and help
 others with their CakePHP related questions.


 To unsubscribe from this group, send email to
 cake-php+unsubscr...@googlegroups.com For more options, visit this group at
 http://groups.google.com/group/cake-php

-- 
Our newest site for the community: CakePHP Video Tutorials 
http://tv.cakephp.org 
Check out the new CakePHP Questions site http://ask.cakephp.org and help others 
with their CakePHP related questions.


To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
http://groups.google.com/group/cake-php

Re: Understanding MVC Architecture

2012-04-24 Thread bs28723

Thanks for the reply.  It just seems like I am putting 100 functions in 
the one controller and a 100 views in the one folder. Just managing the 
code and the single file could get complicated.
But from a user experience, they are managing the organization. These 
are just areas to manage.
So, maybe my question should be...

What is a better way to manage the code?  Maybe I should create 
components to manage the code related to a Model?

On 4/24/2012 3:08 PM, lowpass [via CakePHP] wrote:
 I think there are no hard and fast rules for this. I've done that in
 the past where it seems to make sense to list the associated model
 data from a particular controller. If all you want to do is list the
 Members of a given Organization -- and not provide links to do
 anything further with a given Member -- then it might be fine to put
 the action in OrganizationsController. However, I'll generally create
 a controller for the other model(s), if only for admin functions. In
 your case, you may have a need for an admin to create a new
 OrganizationRole, for example.

 On Sun, Apr 22, 2012 at 12:45 PM, bs28723
 [hidden email] /user/SendEmail.jtp?type=nodenode=5663027i=0 wrote:

  My question is - Is it a better MVC architecture to have a 1 to 1
  relationship for a controller to access the model and the view, or 
 since
  in a case where all relationships stem from a single model - just make
  the one controller have all the actions, but pull data from the related
  models needed together to then send to a view.
 
  Here is some code to help illustrate what I am talking about. ( I
  removed a lot of configuration details, because it is not relevant for
  the architecture discussion)
 
  Organization Model
   $hasMany = array('OrganizationRole', 'Address', 
 'MemberRelationship');
   $belongsTo = array('User');
 
  OrganizationRole Model
   $hasMany = array('OrganizationPermission', 'MemberRelationship');
   $belongsTo = array('Organization');
 
  MemberRelationship Model
   $belongsTo = array('Organization', 'User', 'MembershipLevel',
  'OrganizationRole');
 
  OrganizationPermission Model
  $belongsTo = array('OrganizationRole');
 
  User Model
   $hasMany = array('Organization', 'MemberRelationship', 'Address');
 
 
  So, as you can see, everything is related to Organization either
  directly or indirectly.  So, I am thinking of adding actions to
  OrganizationsController to do things like viewMembers, editMembers,
  deleteMembers, viewRoles, editRoles, assignRoles, etc
  rather than putting calling view, edit, delete actions in
  MemberRelationshipsController and OrganizationRolesControllers.
 
  Any thoughts? Opinions? Suggestions?
 
  Thanks,
  Bill
 
  
  View this message in context: Understanding MVC Architecture
  Sent from the CakePHP mailing list archive at Nabble.com.
 
  --
  Our newest site for the community: CakePHP Video Tutorials
  http://tv.cakephp.org
  Check out the new CakePHP Questions site http://ask.cakephp.org and 
 help
  others with their CakePHP related questions.
 
 
  To unsubscribe from this group, send email to
  [hidden email] /user/SendEmail.jtp?type=nodenode=5663027i=1 For 
 more options, visit this group at
  http://groups.google.com/group/cake-php

 -- 
 Our newest site for the community: CakePHP Video Tutorials 
 http://tv.cakephp.org
 Check out the new CakePHP Questions site http://ask.cakephp.org and 
 help others with their CakePHP related questions.


 To unsubscribe from this group, send email to
 [hidden email] /user/SendEmail.jtp?type=nodenode=5663027i=2 For 
 more options, visit this group at http://groups.google.com/group/cake-php


 
 If you reply to this email, your message will be added to the 
 discussion below:
 http://cakephp.1045679.n5.nabble.com/Understanding-MVC-Architecture-tp5657637p5663027.html
  

 To start a new topic under CakePHP, email 
 ml-node+s1045679n125572...@n5.nabble.com
 To unsubscribe from CakePHP, click here 
 http://cakephp.1045679.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=1255722code=YmlsbC5zdG9sdHpAYm9vc3RlcndlYnNvbHV0aW9ucy5jb218MTI1NTcyMnwtNTU0NTk2MTUy.
 NAML 
 http://cakephp.1045679.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
  



--
View this message in context: 
http://cakephp.1045679.n5.nabble.com/Understanding-MVC-Architecture-tp5657637p5663601.html
Sent from the CakePHP mailing list archive at Nabble.com.

-- 
Our newest site for the community: CakePHP Video Tutorials 
http://tv.cakephp.org 
Check out the new CakePHP Questions site http://ask.cakephp.org and help others

Re: Understanding MVC Architecture

2012-04-24 Thread lowpass

On Tue, Apr 24, 2012 at 8:12 PM, bs28723
bill.sto...@boosterwebsolutions.com wrote:
 Thanks for the reply.  It just seems like I am putting 100 functions in the
 one controller and a 100 views in the one folder. Just managing the code and
 the single file could get complicated.

Then you should probably be breaking things up a bit.

Also, keep in mind that it's always better to put as much code into
your models rather than the controllers. You can always call its
methods by $this-Model1-Model2-doSomething() if they're associated.

 But from a user experience, they are managing the organization. These are
 just areas to manage.

Yet in some case, you'll be managing a specific Member. There
shouldn't really be any need to do so from the
OrganizationsController. For listing all of the Members within an Org,
sure. But then to edit one of them, you can go to the
MembersController. Once saved, redirect back to the
OrganizationsController.

Router::connect(
'/admin/orgs/:id',
array(
'admin' = 1,
'controller' = 'organizations',
'action' = 'view'
),
array('id' = '[0-9]+', 'pass' = array('id'))
);

public function admin_view($id = null)
{
// pull data for some org
}

Router::connect(
'/admin/orgs/:id/members',
array(
'admin' = 1,
'controller' = 'organizations',
'action' = 'members'
),
array('id' = '[0-9]+', 'pass' = array('id'))
);

public function admin_members($id = null)
{
// pull data for some org and list members
}

When you list the members, create a link pointing to the MembersController:

foreach($data['Member'] as $member) {
$this-Html-link(
$member['name'],
array(
'admin' = 1,
'controller' = 'members',
'action' = 'edit',
'id' = $member['id']
),
array('title' = 'edit this member')
);
}


Router::connect(
'/admin/members/edit/:id',
array(
'admin' = 1,
'controller' = 'members',
'action' = 'edit'
),
array('id' = '[0-9]+', 'pass' = array('id'))
);

public function admin_edit($id = null)
{
// validate and save ...

// redirect back to org's member list
$route = array(
'admin' = 1,
'controller' = 'organizations',
'action' = 'members',
'id' = $this-request-data['Member']['organization_id']
);
$this-redirect($route);
}

 So, maybe my question should be...

 What is a better way to manage the code?  Maybe I should create components
 to manage the code related to a Model?

No, don't do that. If you start creating components to handle
model-specific tasks then you'd definitely be going in the wrong
direction.

Also, it's difficult to tell by just seeing the model names and not
the entire schema, but my hunch is that you might be able to normalize
things so that you have fewer models overall. But that really depends
on what exactly you need to do.

-- 
Our newest site for the community: CakePHP Video Tutorials 
http://tv.cakephp.org 
Check out the new CakePHP Questions site http://ask.cakephp.org and help others 
with their CakePHP related questions.


To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at 
http://groups.google.com/group/cake-php

Re: Understanding MVC Architecture

2012-04-24 Thread bs28723

Great ideas. I will see about pushing more into the models. I have not
really done much with the router, but that gives me some ideas on how I
can do some things.

The data is fairly normalized, I am sure there is room for improvement.
But it needs to scale.
Basic premise is Users manage their profile, and can do a few things.
Users can create organizations. The User/Owner of the Organization can
manage it. Users can join Organizations. Users can join multiple
organizations and have different roles.
If you are familiar with facebook groups then this concept is part of my
site. I an not trying to recreate facebook or anything like that, but
some of the features of signup, moderation or manage the group, are a
good analogy. The main point is that it has to scale and that there are
several many to many tables.

Which brings up another question - I had some challenges getting the
multiple roles and ACL working. So, I have basically used Controller
based authorization and isAuthorized routines. This works well. The
documentation talks about you could go to a model based authorization.
I assume it works the same, except that the isAuthorized routines will
be in the Models instead of the controllers. I can't seem to find a lot
of examples of why to do this? I don't know if this would be a good
idea or not. Do you have any ideas or thoughts about this?

Thanks again for the help.

--
View this message in context:
http://cakephp.1045679.n5.nabble.com/Understanding-MVC-Architecture-tp5657637p5663744.html
Sent from the CakePHP mailing list archive at Nabble.com.

--
Our newest site for the community: CakePHP Video Tutorials
http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others
with their CakePHP related questions.

To unsubscribe from this group, send email to
cake-php+unsubscr...@googlegroups.com For more options, visit this group at
http://groups.google.com/group/cake-php

97 matches

Mail list logo