Arrange Content Around Its Purpose

• A website does not always need every collection presented in the same order. A set of pages may have a preferred sequence, or a selected group of content may need a particular editorial priority. Changing publication dates merely to influence that sequence mixes two different decisions: when something was published and where it should appear in an ordered list.
• Custom Post Order separates those concerns. Dragging items saves a native WordPress menu-order value that supported queries can use in ascending order. The content remains the same record with the same date and sticky setting. This provides an ordering workflow without pretending that every list on the website will immediately change; the saved sequence must be consumed by a supported query where order application is enabled.

Reorder From the WordPress Content List

• The drag-and-drop interface appears on enabled WordPress list screens when that option is active. This makes ordering part of the same environment where editors already review titles, statuses, and other content information. Instead of keeping a separate spreadsheet of priority values, an authorized user can arrange the relevant list and let WP PowerSuite save its menu order.
• Reordering requires the configured capability, which defaults to permission to edit other users' posts. This keeps sequence changes within the intended editorial workflow rather than giving every account a new way to reorganize content. The list interface is an editing tool, while the query-application settings decide where the stored order affects output. An admin list's default query order is a separate Pro control, not something to confuse with the availability of free drag-and-drop editing.

Control the Queries That Use Your Sequence

• Saving a custom order is only half the job. The query that retrieves content must use that order for it to affect the displayed list. WP PowerSuite provides a frontend main-query option that is on by default, with separate Pro controls for archive, search, and admin query application. Those additional contexts start off, allowing you to choose where a custom sequence belongs.
• This matters when a website contains different kinds of lists. A manually curated collection and a search-results view may have different priorities, and another template may already request its own ordering. Respect Existing Order is enabled by default. Review those interactions rather than assuming the drag-and-drop sequence should override every existing query, page-builder element, or plugin-generated list on the site.

Extend Ordering to Custom Content With Pro

Reset Order Without Deleting Content

• A curated sequence can become unnecessary after a redesign or a change in editorial priorities. The Pro Reset action clears the relevant menu-order values to zero, with an optional parent scope, rather than deleting content or altering its publication dates. This gives administrators a way to remove the ordering values when they are no longer wanted.
• Reset should not be mistaken for restoring a historical version of a previous sequence. It clears the stored order values; the resulting display then depends on the query and other ordering rules in use. The module also provides notices for detected conflicts with other ordering plugins. Review overlapping tools so two independent systems are not being asked to control the same content sequence without an intentional policy.

Keep Post Ordering Separate From Taxonomy Ordering