Can you provide screenshots of the fields you’re editing here? I am not able to work out in my head which ones you’re referring to. We shouldn’t have anything affecting anything outside of our own pages, and the forced lowercase and underscores should only be affecting the name/slug field.
I added 3 pictures and explained the problem on image. Such as my taxonomy is art category, and Name: Architeture and Slug: architecture, when i want to chance NAMEArchitecture to Architecture and Interior Design, name field converting all space to _ symbol and A to a or I to i… Problem start last update 25 March 2016. All taxonomy and post category do this… But i chance name with quick edit…
Thanks and sorry bad english
Same problem here. Some script is converting taxonomy name change as I type with underscores for spaces and lowercasing all.
line 37 of cptui.js, targeting #name instead of #slug
Confirmed bug but in a way that isn’t perhaps what’s expected.
I was managing to avoid loading the cptui.js file in the post screen, but I was not taking the term screen into account. Because of that, the cptui.js file was being loaded, and the field attributes were matching in such a way that we were affecting the label unintentionally.
Will be pushing out a fix for that this week. Please use the quick edit in the meantime.
Thank you for the patience.
If anyone wants to help test, https://github.com/WebDevStudios/custom-post-type-ui/archive/cptuijs-screen-fix.zip
PLEASE NOTE: disable your current copy of CPTUI before activating this new copy with the likely fixes. Avoid testing on production if possible. Once confirmed working for multiple people, we’ll move to get the fix out the door for everyone.
@michael Beckwith
Its really perfect pluging for me and sometimes can be bug, no problem 🙂 … At the moment, I am using qtranslateX so i cant use quick edit at same time…
“If anyone wants to help test, https://github.com/WebDevStudios/custom-post-type-ui/archive/cptuijs-screen-fix.zip ” / i am simple user so its complex works for me.
@michael Beckwith @efrap
in cptui.min.js file; (“#name”) to (“#sluq”) solved my problem. Does it make any problem in the future?
Best Regards
You’re going to not want to rely on changing the js because we’re not planning to change that part as any implemented fix.
The version I linked above simply makes sure cptui.js/cptui.min.js isn’t loaded at all on those pages, which should remove the conflict as well.
i just uploaded all files with Ftp to wp-content/pluging/cptui and solved…. Correct way, right?
Thank you so much and good luck….
Yes, that’s one way to help test. Thanks.
Sounds like we’re good to go with the fix. Feel free to keep it for the moment, and we’ll be pushing out version 1.3.2 soon with this one included.
Thanks again.
After updating from 1.2.4 to 1.3.1 , this is also happening with regular post terms, not just those created/registered using your plugin. Thanks for a rapid release of 1.3.2.
Yeah, this one wasn’t something specific to code registering taxonomies for CPTUI, it was simply js being enqueued in corners I missed.
1.3.2 will probably early next week, but everyone should feel free to use the patched 1.3.1 version above.
I’ve tested the patched version and it resolves the issue I was having when editing regular post terms.
Excellent. Hoping to take care of that update today.
