Title: Custom Types Quick Edit Bug
Last modified: August 3, 2017

---

# Custom Types Quick Edit Bug

 *  [stevedbrock](https://wordpress.org/support/users/stevedbrock/)
 * (@stevedbrock)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/custom-types-quick-edit-bug/)
 * When I use the Quick Edit function in the list view extra table cells are being
   added to the table causing significant display bugs. If I reload the list it 
   looks fine again.
 * This appears to be a conflict between CPT-onomies and the Toolset Types plugin.
   It only occurs with custom types (which I’ve added using Toolset Types) and only
   if I have the CPT-onomies plugin installed and active. Default post types work
   fine, as do the custom types if I deactivate CPT-onomies. I’ll report the bug
   on the Toolset forum as well in hopes that between the two of you there might
   be some workaround or fix.

Viewing 1 replies (of 1 total)

 *  [innocuo](https://wordpress.org/support/users/innocuo/)
 * (@innocuo)
 * [8 years, 9 months ago](https://wordpress.org/support/topic/custom-types-quick-edit-bug/#post-9429113)
 * I also have this issue with CPT-onomies, but I don’t have that Toolset Types 
   plugin. This seems to be a bug in CPT-onomies js code.
 * First of all, it’s not a new issue. See [this issue from a year ago](https://wordpress.org/support/topic/quick-edit-issue/),
   and [this one from 9 years ago](https://wordpress.org/support/topic/quick-edit-js-error-table_columnscolumn_index/).
   Notice that neither have a reply from the plugin author, so expect this issue
   not to be solved ever.
 * Second, the issue is caused by bad, ugly, convoluted unnecessary javascript. 
   The issue is in assets/js/admin-edit.min.js, where the author overrides the default
   WordPress code to save the quick-edit form, to add some sort of weird checks 
   to the column values. That code is all over the place and simply bad: it loops
   through all the css classes of each column to figure out the names of the columns(
   when he could simply get them from the th ids at the top of the table), which
   causes fake values (for example: the code thinks “column-primary” is a displayed
   column, when it isn’t). Then, it loops again to figure out if a column is or 
   not to be updated. But it starts at index 1 when it should at index 0. After 
   that it makes multiple ajax requests to get the column values….anyway, I can’t
   find any reason for this code, other than maybe the author was on drugs? not 
   sure.
 * Long store short, it seems all that code that creates this issue doesn’t need
   to be there. The fix is to ignore it.
 * You probably can edit the file in the plugin folder cpt-onomies/assets/js/admin-
   edit.min.js. It’s a minified file so hard to edit, but look for the code `$wp_inline_edit_save.
   apply(this,arguments);`
    and add `return;` after that. That makes it ignore the
   rest of the code. So far, it seems to be working ok for me.

Viewing 1 replies (of 1 total)

The topic ‘Custom Types Quick Edit Bug’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/cpt-onomies_f2f2f2.svg)
 * [CPT-onomies: Using Custom Post Types as Taxonomies](https://wordpress.org/plugins/cpt-onomies/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/cpt-onomies/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/cpt-onomies/)
 * [Active Topics](https://wordpress.org/support/plugin/cpt-onomies/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cpt-onomies/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cpt-onomies/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [innocuo](https://wordpress.org/support/users/innocuo/)
 * Last activity: [8 years, 9 months ago](https://wordpress.org/support/topic/custom-types-quick-edit-bug/#post-9429113)
 * Status: not resolved