The added security is in that the Presentation layer is what is exposed to
the world and is more vulnerable. In the event that the Presentation layer
is hacked, it would not have access to the Database layer. There is added
security in front of the Application layer (which has access to the
Dat
'className' => 'Person',
'joinTable' => 'person_follows',
'foreignKey' => 'table_id',
'associationForeignKey' => 'id',
'conditions' => array('PersonFollow.table_nam
John,
I have another similar challenge I’m working on and I thought you may be able
to help.
Here’s my stackoverflow:
http://stackoverflow.com/questions/27826627/cakephp-use-both-foreignkey-and-conditions-in-hasmany
Any help would be appreciated. Thanks.
—
Matt
--
Matt Myers
Sent with
Thanks John! This looks great. I'll give it a try.
--
Matt
On Wednesday, October 15, 2014 12:35:40 PM UTC-6, John Andersen wrote:
>
> Hi Matt
>
> Created a test setup and got the result you wanted by defining each model
> as follows:
>
> class LinkedinPerson extends AppModel {
> public $has
akePHP are you using?
>
> Kind regards
> John
>
> On Monday, 13 October 2014 22:09:11 UTC+3, Matt Myers wrote:
>>
>> // in LinkedinPerson
>> public $hasMany = array(
>> 'LinkedinRecommendation' => array(
>> 'className
// in LinkedinPerson
public $hasMany = array(
'LinkedinRecommendation' => array(
'className' => 'LinkedinRecommendation',
'foreignKey' => false,
'dependent' => true,
),
)
// in LinkedinRecommendation
public $belongsTo = array(
'LinkedinPerson' => array(
I've been hitting my head over this for quite some time now. When I login
using the Auth Component as such:
$this->Auth->login()
It will login just fine and define the following authUser:
User
User.Person
User.Company
But when I login in another situation like so:
$this->Auth->login($user['Us
