Support Forum
Support › MB Custom Post Type › CustomTaxonomy - does not save number of records to display
Hi,
2 CustomTaxonomies works well, but 1 CustomTaxonomy does not save the number of records to display at dashboard and always display only 20 terms... :((
All settings seems the same!
How to resolve?
Hello,
You can try to deactivate all plugins except Meta Box, MB extension plugins and switch to a standard theme of WordPress and recheck this issue.
Also, please try to register the custom taxonomy with code and see how it goes. Refer to the documentation https://docs.metabox.io/extensions/mb-custom-post-type/#getting-php-code-1
You can try to deactivate all plugins except Meta Box, MB extension plugins and switch to a standard theme of WordPress and recheck this issue.
As always with you, Peter - your answers are completely Useless. Does your forum have any more competent stuff?
PS I found the reason and it very simple. Suppose you with your "default negligent" attitude cannot find it for 2000 years.
And yes, seems its a bug-flaw and potentially stability vulnerability of your plugin...
OK, i will share of critical bug which I've found - it consist of 2 smaller shortcomings:
1) When admin create a new Taxonomy there is no uppercase/lowercase check or formatting. Then I save a new Taxonomy with name "Shops". But at WP dashboard Taxonomies lists pages setting of "how much taxonomies must be shown at 1 page" have this format and save settings with lowercase ONLY, thus settings with "show 100 items per page" was saved not for "Shops" but for "shops"!
2) That it seems your MB has a critical flaw with absent of "connections backward maintain". For example when at MB CustomTaxonomy I've change "Shops" to "shops" - at CustomTaxonomyTerms dashboard all terms from this taxonomy just disappear!!! Thus your MB does not have functions to rename CustomTaxonomies to save their connection!!! At 2023 its really severe defect!!!
Both problems are very important and pretty easy to resolve.
Cheers.
PS To resolve problem (2) I was forced to make auto-replace SQL script directly at DB via phpMyAdmin. Which not "user friendly" at all!