Answers.Body: <p>I think this is what are you searching for:</p>
  
  <p><a href="http://buildwithcraft.com/docs/config-settings#pageTrigger" rel="nofollow">http://buildwithcraft.com/docs/config-settings#pageTrigger</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-09T11:43:41.500Z
Answers.LastActivityDate: 2014-12-09T11:43:41.500Z
Answers.UserDisplayName: Cipick
Body: <p>Is it possible to use a <code>page</code> query parameter for paginating entries with <code>{% paginate %}</code> instead of a dynamic segment?</p>
  
  <p>So instead of <code>http://example.com/articles/p2</code> i would like to use <code>http://example.com/articles?page=2</code>.</p>
  
  <p>This would simplify interoperability with client side MVC frameworks because the query parameter would be clearly separated from a dynamic route for a single entry in <code>articles</code> (i.e. <code>http://example.com/articles/a-single-article</code>).</p>
  
  <p>The only solution I can think of at the moment is to not use <code>{% paginate %}</code> altogether and instead calculate <code>limit</code> and <code>offset</code> for <code>craft.entries.find(...)</code> manually from <code>craft.request.getQuery("page")</code>. I hope there is an easier way?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-02T17:50:51.693Z
Comments.Text: Unfortunately, the `pageTrigger` setting just changes the segment. Looking at Craft's source, as best I can tell the segments are the only thing that can be used with the built in `paginate` tags. Christian, were you able to figure something out? I hesitate to resort to writing a bunch of custom code to read/update `craft.request`.
Comments.UserDisplayName: Janson Hartliep
Tags: <pagination>
Title: Paginate entries with 'page' query parameter?
ThreadText: # Paginate entries with 'page' query parameter?
  
  (Asked by: username_0 on 2014-10-09)
  
  Is it possible to use a `page` query parameter for paginating entries with `{% paginate %}` instead of a dynamic segment?
  
  So instead of `http://example.com/articles/p2` i would like to use `http://example.com/articles?page=2`.
  
  This would simplify interoperability with client side MVC frameworks because the query parameter would be clearly separated from a dynamic route for a single entry in `articles` (i.e. `http://example.com/articles/a-single-article`).
  
  The only solution I can think of at the moment is to not use `{% paginate %}` altogether and instead calculate `limit` and `offset` for `craft.entries.find(...)` manually from `craft.request.getQuery("page")`. I hope there is an easier way?
  
  **Tags:** pagination
  
  > **Comments:**
  > **username_1**: Unfortunately, the `pageTrigger` setting just changes the segment. Looking at Craft's source, as best I can tell the segments are the only thing that can be used with the built in `paginate` tags. username_0, were you able to figure something out? I hesitate to resort to writing a bunch of custom code to read/update `craft.request`.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2014-12-09. Score: 3
  
  I think this is what are you searching for:
  
  <http://buildwithcraft.com/docs/config-settings#pageTrigger>
  
  
  ---
  
  