- Upload the 'order_entries' folder in this archive to your Symphony 'extensions' folder.
- Enable it by selecting the "Order Entries", choose Enable from the with-selected menu, then click Apply.
- You can now add the "Entry Order" field to your sections.
- Add the "Entry Order" field to your section and tick the "Show column" box.
- Click the column heading to sort table by the Entry Order field to enable drag and drop.
- When ordered ascending, drag entries within the table and the orders will be re-saved.
As of version 2.1.4 Order entries has an additional pagination order per entry. Through this one can set a particular section to be paginated or not.
When using normal pagination the extension makes sure that entries within the page start with the offset of that particular page. For Example if you're on page 3 with 20 entries per page, the first entry will take a minimum index of 41. As this is the least possible to be after the last one of the previous page.
Since Filtering made it to the core, some problems have arisen in regards to Order Entries. In it's previous form filtering and re-ordering would reset the index of that particular sort to start from 1.
This is not always the expected result, with the changes implemented in this version, the offset will start from the minimum index found in the entry.
So if you're sorting entries which were numbered 4, 5 and 6 they will keep the same index values when resorted.
However if you are sorting 4, 6 and 12 sorting would give the following indices; 4, 5 and 6.
Note that if you plan to use the sorting values only within the filtered views, and use that within your data sources this change will not impact your workflow.
Order Entries now supports an option to filter entries and order them separately. To activate this functionality you have to select which fields you would like to use for filtering from within the settings panel. Once saved, filtered views will have separate orders depending on your settings.
It is very important to note that with version 2.2 the "Filter value" used within the publish page matches whatever you put in your datasource. Sorting and order values are determined from the matching datasource parameter. If in the publish page was filtered by "Home" and your datasource filter says "home" the datasource ordering outputs will not match.
Note: If you set filtered ordering, and within the backend no filters unset all sorting is done without any backend filters, and your datasource contains a filter for the same field as 'filtered ordering' no ordering will take place. As there are no values set with the backend filters matching the ones in your datasource.
You have been asked to design a schema for a cooking website. Where each recipie has a number ingredients, thus you link your ingredients to your recipes using an association field. The client has also asked to be able to do a dedicated page per ingredient showing the suggested recipies, and they want to order all the supported recipes manually.
Within your recipes section, you add a 'filtered ordering' on the 'ingredients' field This will create a distinct sort order for each ingredient when filtered within your backend.
Thus the recipe 'Spagetti Bolognese' can be in 1st place for 'spagetti', 2nd place for 'tomato sauce' and 4th place for 'minced meat'. Whilst 'lasagna' could be in 3rd place for 'tomato sauce' and 3rd place for 'minced meat'. At the same time in the general recipie classification (no filters) 'Spagetti Bolognese' ranks 5th and 'Lasagna' 15th.