Whats the best way to achieve reciprocity between a HABTM self-referencing
model?
For example:
I have a model called Zones it HABTM other Zones. I have the join table
setup and everything is working like other HABTM models. But I want the
reverse connection to also be established. So instead
Router::connect(
'/products/:category',
array(
'controller' => 'categories',
'action' => 'index'
),
array(
'category' => '[-a-z]+',
'pass' => array('category')
)
);
Router::connect(
'/products/:category/:product',
array(
'controller' => 'products',
'action' => 'view'
),
array(
'category' => '[-a-z
Would that simply make using ajax pointless if you re-run the same
pagination just to fetch 1 record?
You have 20 datasets / records on the page, delete 1, why pull 20 records
(19 of them are already on the page) just to replace the 1 you deleted?
From: cake-php@googlegroups.com [mail
Hi Dave,
Use Ajax Pagination, and after delete a record, reload the page which you
are again.
On Tuesday, April 16, 2013 6:31:35 AM UTC-3, advantage+ wrote:
>
> What I am trying to do is create a standard pagination set, but the user
> has the ability to delete a record using AJAX.
>
>
>
> S
Yes you have to have "&" in front of $photo. This makes $photo a reference
to the element in $photos instead of a copy. If you don't have it then you
will be modifying a copy of the array element and not the element itself.
See http://www.php.net/manual/en/language.references.php for a discuss
hi david,...
a quick question,...
do I have to have "&" upfront of $photo
in foreach ($photos as &$photo)
and what is it stand for..?
thanks
chris
On Monday, April 15, 2013 11:17:31 PM UTC-7, david...@gmail.com wrote:
>
> You are doing a redirect inside of your loop which is kicking you
Hi,
You need to organize a database in different way to achieve what you want.
Create the following table:
nodes - to save the name of categories or products, content types, full
path as a slug.
id
parent_id
lft
rght
title
path
published (0,1)
type
closure - to save deep linking associat
Hi,
You need to organize a database in different way to achieve what you want.
Create the following table:
nodes - to save the name or category of products, content types, full path
as a slug.
id
parent_id
lft
rght
title
path
published (0,1)
type
closure - to save deep linking association
