<p>This is only possible with the <code>id</code> parameter in combination with <a href="https://craftcms.com/docs/templating/craft.entries#fixedOrder" rel="nofollow"><code>fixedOrder</code></a>. </p>

<pre><code>{% set entries = craft.entries.id([307, 287, 488]).fixedOrder(true) %}
</code></pre>

<p>You can look up your singles' IDs in the URL of the entries in the CP.</p>

<p>example.com/admin/entries/section1/<strong>307</strong>-section1/</p>

CC BY-SA 3.0
2016-03-02T02:08:35.427Z
Thanks!  Worked perfectly!  Should have looked at the docs better :)
biko
CC BY-SA 3.0
2016-03-01T08:37:42.470Z
2016-03-01T08:37:42.470Z
carlcs
<p>When querying multiple singles by section slugs, is it possible to maintain the order of the results as the query?  Currently the return result is sorted by the default <code>postDate desc</code>.</p>

<pre><code>craft.entries.section(['section1', 'section2', 'section3'])
</code></pre>

<p>returns an array with the order
section1, section2, section3</p>

<p>Documentation doesn't seem to answer this question.
<a href="https://craftcms.com/docs/templating/craft.entries#order" rel="nofollow">https://craftcms.com/docs/templating/craft.entries#order</a></p>

<entries><order>
Sort single entries by section with same query order
# Sort single entries by section with same query order

(Asked by: username_0 on 2016-03-01)

When querying multiple singles by section slugs, is it possible to maintain the order of the results as the query?  Currently the return result is sorted by the default postDate desc.
craft.entries.section(['section1', 'section2', 'section3'])

returns an array with the order
section1, section2, section3
Documentation doesn't seem to answer this question.
https://craftcms.com/docs/templating/craft.entries#order

**Tags:** entries, order

---

## 1 answers

### Answer by username_1 on 2016-03-01. Score: 2 | Accepted answer

This is only possible with the id parameter in combination with fixedOrder. 
{% set entries = craft.entries.id([307, 287, 488]).fixedOrder(true) %}

You can look up your singles' IDs in the URL of the entries in the CP.
example.com/admin/entries/section1/307-section1/

> **Comments:**
> **username_0**: Thanks!  Worked perfectly!  Should have looked at the docs better :)  

---

