| # |
Jan 28th 2014, 17:13 |
dereuromark |
;) |
| # |
Jan 28th 2014, 17:13 |
biesbjerg |
dereuromark: thank you for the idea about calculating the position diff and using move up/down - works like a charm! :-) |
| # |
Jan 28th 2014, 17:12 |
nurulhuda |
good night |
| # |
Jan 28th 2014, 17:04 |
styks1987 |
it is like it is not detecting that it is a delete request and it just looks for the method of 1 |
| # |
Jan 28th 2014, 17:02 |
styks1987 |
yes 'routes'=>true in bootstrap. And /plugin_name/cotroller.json works |
| # |
Jan 28th 2014, 17:01 |
Neon1024 |
Are you loading the plugins routes file in your CakePlugin::load()? |
| # |
Jan 28th 2014, 17:00 |
styks1987 |
and Router::parseExtensions(); |
| # |
Jan 28th 2014, 17:00 |
styks1987 |
in the plugins routes.php |
| # |
Jan 28th 2014, 17:00 |
styks1987 |
likely, but I am using the default routes Router::mapResources('attachments'); |
| # |
Jan 28th 2014, 16:59 |
Neon1024 |
styks1987: Sounds like a routing issue |
| # |
Jan 28th 2014, 16:59 |
Froobly |
in friendsofcake/crud, why is beforeRender() called twice? :s |
| # |
Jan 28th 2014, 16:56 |
styks1987 |
it says Action AttachmentsController::1() could not be found. |
| # |
Jan 28th 2014, 16:48 |
styks1987 |
I have a function called delete in the controller |
| # |
Jan 28th 2014, 16:48 |
styks1987 |
I am trying to send a delete request to a plugin controller but it keeps telling me the function does not exist. /plugin_name/controller.json works but /plugin_name/controller/id.json via DELETE request returns a 404 |
| # |
Jan 28th 2014, 16:32 |
biesbjerg |
I'm doing it the easy way for now by only making it possible to reorder within the same parent |
| # |
Jan 28th 2014, 16:32 |
biesbjerg |
ah, yes |
| # |
Jan 28th 2014, 16:32 |
dereuromark |
by moving a record somewhere else it might have a different parent_id |
| # |
Jan 28th 2014, 16:31 |
biesbjerg |
don't understand what you mean by "first modify parent_id" though |
| # |
Jan 28th 2014, 16:31 |
biesbjerg |
dereuromark: might also work |
| # |
Jan 28th 2014, 16:29 |
dereuromark |
you first modify parent_id and afterwards move it up/down until the correct position is reached |
| # |
Jan 28th 2014, 16:29 |
biesbjerg |
jose_zap :) |
| # |
Jan 28th 2014, 16:29 |
dereuromark |
biesbjerg: bad.. calc the diff to the current structure and then modify accordingly |
| # |
Jan 28th 2014, 16:28 |
biesbjerg |
gives me* |
| # |
Jan 28th 2014, 16:28 |
biesbjerg |
dereuromark: jqueryUI sortable gives be an array of id's in the new order |
| # |
Jan 28th 2014, 16:27 |
jose_zap |
let me suggest then that you read it again, http://www.sitepoint.com/hierarchical-data-database-2/ |
| # |
Jan 28th 2014, 16:27 |
dereuromark |
biesbjerg: you can leverage the trees behavior up/down to make it work |
| # |
Jan 28th 2014, 16:27 |
biesbjerg |
Got an idea, maybe I can use a position field and reorder using TreeBehavior::reorder() according to position :) |
| # |
Jan 28th 2014, 16:26 |
biesbjerg |
since it uses lft/rght values |
| # |
Jan 28th 2014, 16:25 |
biesbjerg |
which is why I don't understand your suggestion to use a custom field (e.g. position INT) and still have TreeBehavior return data in tree-structure in the correct order ;) |
| # |
Jan 28th 2014, 16:24 |
biesbjerg |
I already knows how the hierachy and lft/rght works and is calculated |
| # |
Jan 28th 2014, 16:24 |
jose_zap |
also it will explain why you cannot do that |
| # |
Jan 28th 2014, 16:24 |
jose_zap |
I recommend you read the theory be hid MPPT, once you understand how it works it makes you think of better ways to access your data |
| # |
Jan 28th 2014, 16:23 |
jose_zap |
P |
| # |
Jan 28th 2014, 16:23 |
jose_zap |
ehmm. no |
| # |
Jan 28th 2014, 16:22 |
biesbjerg |
If I don't I will get wrong order when using TreeBehaviors methods |
| # |
Jan 28th 2014, 16:22 |
biesbjerg |
Don't know why, but seems wrong to me to add another field. Wouldn't it be better to reorder using lft/rght values? |
| # |
Jan 28th 2014, 16:21 |
jose_zap |
you could add other column to order within levels, though |
| # |
Jan 28th 2014, 16:21 |
jose_zap |
that means it orders following the outer shape of the tree from left to right |
| # |
Jan 28th 2014, 16:20 |
jose_zap |
trees can be ordered in different ways, the order that tree behaviour uses naturally is pre-order |
| # |
Jan 28th 2014, 16:20 |
jose_zap |
one think is tree hierarchy, another is position in the tree |
| # |
Jan 28th 2014, 16:19 |
biesbjerg |
jose_zap: Hmm.. parent_id only says who the parent is (if any), not the position of the node |