Divi 5’s Blog module always lists posts by date, newest first, and puts sticky posts at the top of the first page. Divi’s Loop Builder can sort posts, but the Blog module can’t. Divi Doctor adds Order By, Order and Ignore Sticky Posts to the Blog module. This page covers each option, how sticky posts and archives are handled, and the limits.
Switch it on
- Go to Divi Doctor → Features.
- Under Blog module, find the Order By, Order and Ignore Sticky Posts card and click Enable.
The card’s checks confirm that the Divi 5 engine and Divi’s Blog module were found. Existing Blog modules keep Divi’s order until you change their settings.
Sort a Blog module
- Open the page in the Visual Builder and open the Blog module’s settings.
- In Content → Content, below Post Offset Number, choose an Order By and an Order.
- To show sticky posts in their normal place, switch on Ignore Sticky Posts.
- Check the builder preview. It shows the same order as the live page.
- Save the page, clear any page cache, and check the page logged out.
The options
| Option | What it does | Default |
|---|---|---|
| Order By | What the posts are sorted by. The values are the Loop Builder’s (see below). Hidden while Posts For Current Page is on. | Publish Date |
| Order | Descending shows the newest date, the highest number or Z first. Ascending shows the oldest date, the lowest number or A first. Hidden while Posts For Current Page is on, and when Order By is Random or None. | Descending |
| Ignore Sticky Posts | Shows sticky posts in their normal place instead of first on page 1. Works with Posts For Current Page on or off. | Off |
A module left on Publish Date and Descending, with Ignore Sticky Posts off, keeps Divi’s order exactly. These options have one value for all screen sizes.
Order By values
| Value | Sorts by |
|---|---|
| Publish Date | The date the post was published. This is Divi’s order. |
| None | No sort order: the posts come in the order the database returns them. |
| ID | The post’s ID. |
| Title | The post title, alphabetically. |
| Post Name | The post’s slug, alphabetically. |
| Last Modified Date | When the post was last edited. |
| Random | A new random order on every page load. |
| Author | The author’s user ID, so posts are grouped by author. It doesn’t sort by the author’s name. |
| Comment Count | The number of comments. |
Sticky posts
Divi’s Blog module lists sticky posts first on page 1, then the other posts. With these options:
- With a new Order By or Order, sticky posts still come first on page 1, and they’re sorted the same way among themselves.
- With Ignore Sticky Posts on, the module treats no post as sticky. Sticky posts appear in their normal place in the order you chose.
- This only applies to that module. Other Blog modules, and the rest of the site, keep their sticky posts.
Archives and Posts For Current Page
When Posts For Current Page is on, for example in a Theme Builder archive template, the module shows the archive’s posts in the archive’s own order. Order By and Order are hidden and not used. Ignore Sticky Posts still works.
How it works
While a Blog module with these settings renders, Divi Doctor sets the order on that module’s own post query, and on the query Divi uses for its sticky posts. Nothing else is touched: other queries on the page, including shortcodes or modules inside the listed posts, keep their order, and no extra query runs. Modules that keep Divi’s order get nothing at all. The builder preview is sorted the same way.
Limits
- Divi 5 only.
- Random shows a new order on every page load, so with pagination a post can show on two pages or on none.
- With Posts For Current Page on, Order By and Order don’t apply.
- These are content settings, so like Divi’s other Blog content settings they aren’t saved in presets. Set them on each module.
- Turning the feature off brings back Divi’s order straight away. The settings stay saved in your modules and are ignored.
Questions
How do I change the post order in the Divi 5 Blog module?
Switch on Order By, Order and Ignore Sticky Posts in Divi Doctor → Features, under Blog module. Then, in the Blog module’s Content → Content, below Post Offset Number, choose an Order By and an Order. Without it, Divi 5’s Blog module always lists posts by date, newest first. The builder preview shows the same order as the live page.
Can I sort the Divi Blog module alphabetically by title?
Yes. Set Order By to Title, then set Order to Ascending to show A first, or Descending for Z first. Other values include Last Modified Date, Random, Comment Count, Post Name, ID and Author. Author groups posts by the author’s user ID; it doesn’t sort by the author’s name.
How do I stop sticky posts showing first in the Divi Blog module?
Switch on Ignore Sticky Posts in the Blog module’s Content → Content. The module then treats no post as sticky, and sticky posts appear in their normal place in the order you chose. This only applies to that module: other Blog modules and the rest of the site keep their sticky posts. It works with Posts For Current Page on or off.
Does Order By work in a Divi Theme Builder archive template?
No. When Posts For Current Page is on, as in a Theme Builder archive template, the module shows the archive’s posts in the archive’s own order. Order By and Order are hidden and not used there. Ignore Sticky Posts still works, so sticky posts can still appear in their normal place.
Can I save the Divi Blog module’s Order By setting in a preset?
No. These are content settings, so like Divi’s other Blog content settings they aren’t saved in presets. Set them on each module. They have one value for all screen sizes, and a module left on Publish Date and Descending, with Ignore Sticky Posts off, keeps Divi’s order exactly.
Why do posts repeat across pages with Random order in the Divi Blog module?
Because Random shows a new order on every page load, so with pagination a post can show on two pages or on none. None is different: it has no sort order, and the posts come in the order the database returns them. Publish Date with Descending is Divi’s own order.
If the order doesn’t change on the live page, clear the page cache first. See also Features and bug fixes in the FAQ.