Profile: martinE-4

Problem: 403 Forbidden err on new cust. posts for UPDATE in Wordpress EDIT (QUICKEDIT OK)

Solution: Please try to follow the basic debug steps.

You can find the proposed solution in this case with the following reply: => https://toolset.com/forums/topic/403-forbidden-err-on-new-cust-posts-for-update-in-wordpress-edit-quickedit-ok/#post-1243898

Relevant Documentation: https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/#php-debugging

Problem: I would like to understand the advantages of using a single checkbox custom field as opposed to using a single term in a custom taxonomy. I would also like to know if it's possible to migrate a custom field checkbox to be a single term in a custom taxonomy.

Solution: The advantage of a checkbox vs. a taxonomy term are a bit subjective. When you create Query Filters in wp-admin, you can create more powerful filters for custom fields than you can create for terms, but in practical use that's probably not a real advantage. You could argue that it's less likely for other site admins to be able to create a problem by adding other terms to this custom taxonomy. It's also easier to set up a checkbox field that doesn't have a term archive associated with it, since taxonomy terms are usually set up to have archives by default. You can assign custom fields to a many-to-many relationship, while it's not always easy to assign a taxonomy term to that same relationship. Managing this checkbox status in Forms might be a challenge if it's set up as a flat taxonomy because there's no simple checkbox input for flat taxonomies. You would have to type the term name.

Those are the main things I can think of right now. Migrating a checkbox to a term would require custom code, a custom SQL statement that directly manipulates the database, or some manual intervention in a CSV export / import process.