How to include pagination parameters in a cakephp 3.x route
I want my orders index to be sorted by id descending when I open the start page /
. Here are the routes I have tried so far:
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', 'sort' => 'id', 'direction' => 'desc']);
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', '?' => ['sort' => 'id', 'direction' => 'desc']]);
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', 'pass' => ['sort' => 'id', 'direction' => 'desc']]);
None of them work (i.e. the sorting parameters are ignored), even though the request object looks fine when I use the second option with the ?
.
How do I have to setup the route?
Edit:
/?sort=id&direction=desc
This url display what I want to see at /
.
cakephp cakephp-3.0
add a comment |
I want my orders index to be sorted by id descending when I open the start page /
. Here are the routes I have tried so far:
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', 'sort' => 'id', 'direction' => 'desc']);
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', '?' => ['sort' => 'id', 'direction' => 'desc']]);
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', 'pass' => ['sort' => 'id', 'direction' => 'desc']]);
None of them work (i.e. the sorting parameters are ignored), even though the request object looks fine when I use the second option with the ?
.
How do I have to setup the route?
Edit:
/?sort=id&direction=desc
This url display what I want to see at /
.
cakephp cakephp-3.0
add a comment |
I want my orders index to be sorted by id descending when I open the start page /
. Here are the routes I have tried so far:
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', 'sort' => 'id', 'direction' => 'desc']);
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', '?' => ['sort' => 'id', 'direction' => 'desc']]);
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', 'pass' => ['sort' => 'id', 'direction' => 'desc']]);
None of them work (i.e. the sorting parameters are ignored), even though the request object looks fine when I use the second option with the ?
.
How do I have to setup the route?
Edit:
/?sort=id&direction=desc
This url display what I want to see at /
.
cakephp cakephp-3.0
I want my orders index to be sorted by id descending when I open the start page /
. Here are the routes I have tried so far:
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', 'sort' => 'id', 'direction' => 'desc']);
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', '?' => ['sort' => 'id', 'direction' => 'desc']]);
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', 'pass' => ['sort' => 'id', 'direction' => 'desc']]);
None of them work (i.e. the sorting parameters are ignored), even though the request object looks fine when I use the second option with the ?
.
How do I have to setup the route?
Edit:
/?sort=id&direction=desc
This url display what I want to see at /
.
cakephp cakephp-3.0
cakephp cakephp-3.0
asked Nov 19 '18 at 18:57
David AlbrechtDavid Albrecht
149111
149111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can use a RedirectRoute
which will issue a HTTP 301 redirect:
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', '?' => ['sort' => 'id', 'direction' => 'desc']], ['routeClass' => 'RedirectRoute']);
Alternatively you can set pagination parameters in the controller and add ordering there. Note, that this ordering will persist even if you click on another column to sort by that and the generated SQL will have something like: ORDER BY Orders.created ASC, Orders.id DESC
.
If this behavior is not desired, you can avoid that by not setting default ordering when sort
and direction
query params exist.
Something like this:
class OrdersController extends AppController
{
/**
* Index method
*
* @return CakeHttpResponse|void
*/
public function index()
{
$query = $this->getRequest()->getQueryParams();
if (empty($query['sort']) || empty($query['direction'])) {
$this->paginate['order'] = ['Orders.id' => 'desc'];
}
$orders = $this->paginate($this->Orders);
$this->set(compact('orders'));
}
}
I used the pagination parameters solution, thank you. However I will leave the question open. It was possible to define pagination parameters in routes in cakephp 2.x and I would like to understand why it does not work in 3.x any longer.
– David Albrecht
Nov 20 '18 at 17:38
1
As far as I can tell, from a quick glance at theRoute
class, it seems that theRequest
object is not being updated from theRoute
. I might be missing something though. I suppose you could make a hacky custom route class and update it.
– Timur Asaliev
Nov 21 '18 at 8:18
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53380993%2fhow-to-include-pagination-parameters-in-a-cakephp-3-x-route%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can use a RedirectRoute
which will issue a HTTP 301 redirect:
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', '?' => ['sort' => 'id', 'direction' => 'desc']], ['routeClass' => 'RedirectRoute']);
Alternatively you can set pagination parameters in the controller and add ordering there. Note, that this ordering will persist even if you click on another column to sort by that and the generated SQL will have something like: ORDER BY Orders.created ASC, Orders.id DESC
.
If this behavior is not desired, you can avoid that by not setting default ordering when sort
and direction
query params exist.
Something like this:
class OrdersController extends AppController
{
/**
* Index method
*
* @return CakeHttpResponse|void
*/
public function index()
{
$query = $this->getRequest()->getQueryParams();
if (empty($query['sort']) || empty($query['direction'])) {
$this->paginate['order'] = ['Orders.id' => 'desc'];
}
$orders = $this->paginate($this->Orders);
$this->set(compact('orders'));
}
}
I used the pagination parameters solution, thank you. However I will leave the question open. It was possible to define pagination parameters in routes in cakephp 2.x and I would like to understand why it does not work in 3.x any longer.
– David Albrecht
Nov 20 '18 at 17:38
1
As far as I can tell, from a quick glance at theRoute
class, it seems that theRequest
object is not being updated from theRoute
. I might be missing something though. I suppose you could make a hacky custom route class and update it.
– Timur Asaliev
Nov 21 '18 at 8:18
add a comment |
You can use a RedirectRoute
which will issue a HTTP 301 redirect:
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', '?' => ['sort' => 'id', 'direction' => 'desc']], ['routeClass' => 'RedirectRoute']);
Alternatively you can set pagination parameters in the controller and add ordering there. Note, that this ordering will persist even if you click on another column to sort by that and the generated SQL will have something like: ORDER BY Orders.created ASC, Orders.id DESC
.
If this behavior is not desired, you can avoid that by not setting default ordering when sort
and direction
query params exist.
Something like this:
class OrdersController extends AppController
{
/**
* Index method
*
* @return CakeHttpResponse|void
*/
public function index()
{
$query = $this->getRequest()->getQueryParams();
if (empty($query['sort']) || empty($query['direction'])) {
$this->paginate['order'] = ['Orders.id' => 'desc'];
}
$orders = $this->paginate($this->Orders);
$this->set(compact('orders'));
}
}
I used the pagination parameters solution, thank you. However I will leave the question open. It was possible to define pagination parameters in routes in cakephp 2.x and I would like to understand why it does not work in 3.x any longer.
– David Albrecht
Nov 20 '18 at 17:38
1
As far as I can tell, from a quick glance at theRoute
class, it seems that theRequest
object is not being updated from theRoute
. I might be missing something though. I suppose you could make a hacky custom route class and update it.
– Timur Asaliev
Nov 21 '18 at 8:18
add a comment |
You can use a RedirectRoute
which will issue a HTTP 301 redirect:
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', '?' => ['sort' => 'id', 'direction' => 'desc']], ['routeClass' => 'RedirectRoute']);
Alternatively you can set pagination parameters in the controller and add ordering there. Note, that this ordering will persist even if you click on another column to sort by that and the generated SQL will have something like: ORDER BY Orders.created ASC, Orders.id DESC
.
If this behavior is not desired, you can avoid that by not setting default ordering when sort
and direction
query params exist.
Something like this:
class OrdersController extends AppController
{
/**
* Index method
*
* @return CakeHttpResponse|void
*/
public function index()
{
$query = $this->getRequest()->getQueryParams();
if (empty($query['sort']) || empty($query['direction'])) {
$this->paginate['order'] = ['Orders.id' => 'desc'];
}
$orders = $this->paginate($this->Orders);
$this->set(compact('orders'));
}
}
You can use a RedirectRoute
which will issue a HTTP 301 redirect:
$routes->connect('/', ['controller' => 'Orders', 'action' => 'index', '?' => ['sort' => 'id', 'direction' => 'desc']], ['routeClass' => 'RedirectRoute']);
Alternatively you can set pagination parameters in the controller and add ordering there. Note, that this ordering will persist even if you click on another column to sort by that and the generated SQL will have something like: ORDER BY Orders.created ASC, Orders.id DESC
.
If this behavior is not desired, you can avoid that by not setting default ordering when sort
and direction
query params exist.
Something like this:
class OrdersController extends AppController
{
/**
* Index method
*
* @return CakeHttpResponse|void
*/
public function index()
{
$query = $this->getRequest()->getQueryParams();
if (empty($query['sort']) || empty($query['direction'])) {
$this->paginate['order'] = ['Orders.id' => 'desc'];
}
$orders = $this->paginate($this->Orders);
$this->set(compact('orders'));
}
}
edited Nov 20 '18 at 12:55
answered Nov 20 '18 at 12:48
Timur AsalievTimur Asaliev
763
763
I used the pagination parameters solution, thank you. However I will leave the question open. It was possible to define pagination parameters in routes in cakephp 2.x and I would like to understand why it does not work in 3.x any longer.
– David Albrecht
Nov 20 '18 at 17:38
1
As far as I can tell, from a quick glance at theRoute
class, it seems that theRequest
object is not being updated from theRoute
. I might be missing something though. I suppose you could make a hacky custom route class and update it.
– Timur Asaliev
Nov 21 '18 at 8:18
add a comment |
I used the pagination parameters solution, thank you. However I will leave the question open. It was possible to define pagination parameters in routes in cakephp 2.x and I would like to understand why it does not work in 3.x any longer.
– David Albrecht
Nov 20 '18 at 17:38
1
As far as I can tell, from a quick glance at theRoute
class, it seems that theRequest
object is not being updated from theRoute
. I might be missing something though. I suppose you could make a hacky custom route class and update it.
– Timur Asaliev
Nov 21 '18 at 8:18
I used the pagination parameters solution, thank you. However I will leave the question open. It was possible to define pagination parameters in routes in cakephp 2.x and I would like to understand why it does not work in 3.x any longer.
– David Albrecht
Nov 20 '18 at 17:38
I used the pagination parameters solution, thank you. However I will leave the question open. It was possible to define pagination parameters in routes in cakephp 2.x and I would like to understand why it does not work in 3.x any longer.
– David Albrecht
Nov 20 '18 at 17:38
1
1
As far as I can tell, from a quick glance at the
Route
class, it seems that the Request
object is not being updated from the Route
. I might be missing something though. I suppose you could make a hacky custom route class and update it.– Timur Asaliev
Nov 21 '18 at 8:18
As far as I can tell, from a quick glance at the
Route
class, it seems that the Request
object is not being updated from the Route
. I might be missing something though. I suppose you could make a hacky custom route class and update it.– Timur Asaliev
Nov 21 '18 at 8:18
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53380993%2fhow-to-include-pagination-parameters-in-a-cakephp-3-x-route%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown