Yes, This is a big problem. When a category is selected, some other categories are automatically marked and selected.
A client just reported this to me yesterday. Apparently, when you check a category, ALL categories starting with the same digit get selected, too. For example: If you have a category with id=6 and a lot of categories so you have categories 60…69, 600…699 etc. all those get selected along that category 6.
This seems to be a side effect from a code change between WP 6.7 and WP 6.7.1 due to issues with keeping the both category tabs (most used/all categories) in the classic editor in sync (it only happens with the classic editor, not with the block editor, and I tested various plugins that bring back the classic editor, it seems not to matter which one [e.g. “Classic Editor”, “Disable Gutenberg”, etc.] is used.)
It would be great if somebody could create an issue for this, I don’t have the time to document everything properly for a report right now. Downgrade to WP 6.7 or even 6.6.2 and clearing all caches to make sure the “bad” file version won’t be loaded from cache solves the issue for the moment. Maybe @azaozz could have a look at this?
-
This reply was modified 1 year ago by
OldGrumpyDE. Reason: added some details, mentioned @azaozz
Update: This has already been noted and hotfixed. See https://wordpress.org/support/topic/most-used-post-categories-not-saving/page/2/#post-18153124
TLDR: Should be fixed in 6.7.2 and a plugin for the time being is also available, see link above.
@oldgrumpyde Right, fixed in WP core. Also the hotfix was added to the latest version of Classic Editor. Please let me know if it doesn’t work properly on your site(s).
The latest release I see is still 1.6.6.
When is WP 6.7.2 schedule?
@galbaras, Classic Editor 1.6.7 was just released. Please give it a spin and let us know if it doesn’t resolve the issue for you.
Per the latest schedule update, WP 6.7.2 isn’t planned until mid- to late-January. This issue wasn’t classed as immediately urgent due to it being addressable through the Classic Editor plugin, which the majority of affected users have installed.
Marking this issue as resolved for now.
The update to classic editor fixed the issues for us, thanks 🙂