Title: [Plugin: Custom Taxonomy Sort] Breaks column sorting in Admin
Last modified: August 20, 2016

---

# [Plugin: Custom Taxonomy Sort] Breaks column sorting in Admin

 *  [aljuk](https://wordpress.org/support/users/aljuk/)
 * (@aljuk)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-custom-taxonomy-sort-breaks-column-sorting-in-admin/)
 * Very useful plugin but…
 * it breaks column sorting of taxonomies in the back end. ie. visit a taxonomy’s
   admin page and you can no longer sort the terms via the column headers. For some
   applications, with a high term count, this is an essential feature to have (eg.
   a catalogue site, where you need quick overviews of how many of this or that 
   product type you’re currently listing), and as great as this plugin is, it would
   be better if it didn’t break normal WP functionality.
 * [http://wordpress.org/extend/plugins/custom-taxonomy-sort/](http://wordpress.org/extend/plugins/custom-taxonomy-sort/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [Sea Jay](https://wordpress.org/support/users/jcollier/)
 * (@jcollier)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-custom-taxonomy-sort-breaks-column-sorting-in-admin/#post-2521194)
 * Yes, I am seeing this as well in 3.3.1.
 * There is an “Order” column, but it is not sortable.
 * Also, in Quick Edit and full Edit, order numbers are not displayed.
 * This is such an important plugin! I hope this can be resolved soon.
 * TIA!
 *  Plugin Author [Zack Tollman](https://wordpress.org/support/users/tollmanz/)
 * (@tollmanz)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-custom-taxonomy-sort-breaks-column-sorting-in-admin/#post-2521230)
 * Thanks for the error report! I’ll be checking into this soon.
 *  Plugin Author [Zack Tollman](https://wordpress.org/support/users/tollmanz/)
 * (@tollmanz)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-custom-taxonomy-sort-breaks-column-sorting-in-admin/#post-2521233)
 * Hi Guys,
 * Sorry for the delay in getting to this issue. I agree that this is frustrating.
   Can you help me think through a better way to do this?
 * Here is the issue as I see it. I offer a manual and automatic mode for the sort.
   The idea is that if you are not a developer or don’t want to do anything order
   than turn on the plugin and have it sort by the custom order, you run the plugin
   in automatic mode. If you do so, EVERY place that the terms are displayed will
   be sorted according to the custom sort order. The alternative to this is the 
   manual sort mode where you can control the sort order by placing an argument 
   in the call to get_terms. The custom sort will then only be applied in cases 
   where the get_terms arguments have been properly modified. In manual mode, the
   sort order on the taxonomy page will not be affected.
 * Would the correct solution in your opinion be to override the sort, regardless
   of mode on the taxonomy page? Does that seem logical?
 * Thanks for the input and helping me provide a better experience.
 * Best,
 * Zack

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘[Plugin: Custom Taxonomy Sort] Breaks column sorting in Admin’ is closed
to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/custom-taxonomy-sort.svg)
 * [Custom Taxonomy Sort](https://wordpress.org/plugins/custom-taxonomy-sort/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/custom-taxonomy-sort/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/custom-taxonomy-sort/)
 * [Active Topics](https://wordpress.org/support/plugin/custom-taxonomy-sort/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/custom-taxonomy-sort/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/custom-taxonomy-sort/reviews/)

 * 3 replies
 * 3 participants
 * Last reply from: [Zack Tollman](https://wordpress.org/support/users/tollmanz/)
 * Last activity: [14 years, 4 months ago](https://wordpress.org/support/topic/plugin-custom-taxonomy-sort-breaks-column-sorting-in-admin/#post-2521233)
 * Status: not resolved