Columns size error after saving quick edit
I have an issue with the columns being compressed after saving from the quick edit menu.
see screenshot: https://www.evernote.com/l/ALGHX5-ZhfFDXr564z3OSxdZcRGCa5-53lQ
Hi Shae,
I am able to reproduce the issue. But I think there is more going on.
Can you test for me if you have indeed all fields available in the quick edit screen.
I’m not sure if this is a bug since 4.7 but if there is not a column for the field you like to edit in quick edit, then the value is empty in the quick edit screen. Also the value does not seems to be updated when saving all fields in the Quick edit screen.
Update: Besides the issue that I addressed above, I cannot reproduce the issue where the layout is compressed.
Can you maybe send me an export of your columns on that specific overview to support@admincolumns.com? Which version of Admin Columns do you use?
It looks like it is a conflict between Admin Columns Pro and this plugin: CPT-onomies: Using Custom Post Types as Taxonomies
I’ve contacted support and hopefully can get this worked out. Any other help would be greatly appreciated.
I’ve installed the CPT-axonomy pluging and try to reproduce the problem but without any luck.
Can you tell me how you setup your environment with this plugin and which columns you have on the overview?
We still want to have a look on how to solve this issue.
Thanks for the help.
I’ve exported my Custom Post Type and My ACF fields if you want to test. https://www.dropbox.com/sh/j3rw40q04ijrve3/AABQ4TU68BPhS36Dhzh6XlcJa?dl=0
Screen Recording of issue: https://www.dropbox.com/s/3pnvl8vk2760dfy/Untitled.m4v?dl=0
I am running a clean install of WP and all is running latest versions of the following:
ACF pro
Admin Columns Pro
Admin Columns – Advanced Custom Fields add-on
CPT-onomies
Custom Post Type UI
Thanks for the files.
I was able to create the same environment and reproduce the issue, and I found that the conflict is caused by JS in the CPT-onomies plugin file: /assets/js/admin-edit.min.js
In our plugin we use Ajax to get a row with the same columns as we would normally should get while it looks that CPT-onomies plugin expect that the default columns are used. I can join your discussion with their developer if that helps.
Great! thanks again.
I posted your comments on the support thread. I’ll follow up as soon as I hear anything.
You must be logged in to reply to this topic.