Custom Fields
Re-Envisioned
Support MB Custom Taxonomy I can't activate the check box

  • Creator
    Topic
  • #24802
    Resolved Igor Gouvêa
    Participant

    I created a new taxonomy. Click on the "advanced" tab. Having clicked on a deactivated check box for activation and does not work. No check.
    If I click on one that is activated it is disabled and does not activate again.
    The plugins are all up to date. WordPress is up to date. I use the Solicitor theme.

Viewing 10 replies - 1 through 10 (of 17 total)
  • Author
    Replies
  • #24804
    Igor Gouvêa
    Participant

    More information:

    I disabled all plugins, leaving the theme Twenty Nineteen. Still not working.

    Here is an image that shows my problem. I can't enable these checkboxes:
    -Hierarchical
    -Show admin column
    - Prepended permalink structure
    - hierarchical URL

    This also happens in the Type of Post, tab advanced with the fields:
    -Hierarchical
    - Exclude from search
    - Prepended permalink structure

    And as I said above. If I deselect any field that is marked, it will not be possible to mark it again.

    https://cutt.ly/HzcxvUS

    My plugin MB:
    https://cutt.ly/2zcvbKI
    https://cutt.ly/bzcvkPV

    #24808
    Long Nguyen
    Moderator

    Hi Igor,

    Please follow the step Debugging Information here https://metabox.io/support/topic/how-to-create-a-new-topic/.

    If there are no error messages, please do the step Private Website Info. Let me know how it goes.

    #24817
    Igor Gouvêa
    Participant

    Hello Long

    I disabled all plugins and activated thema Twenty Twenty-One.

    The problem persisted. So I debugged it. I added two lines to wp-config.php (define ('WP_DEBUG', true); define ('SCRIPT_DEBUG', true);)

    Follows the image with the error.

    https://cutt.ly/TzbPhdV

    Thank you very much in advance.

    #24819
    Igor Gouvêa
    Participant

    Additional Information

    Site hosted by HOSTINGER
    PHP 7.4 and WordPress 5.7 (I updated yesterday to see if it solved the problem)

    #24820
    Igor Gouvêa
    Participant
    #24846
    Long Nguyen
    Moderator

    Hi,

    I've received your site credentials on our ticket system. This problem is so weird, I've not seen it before.

    Try to install and activate the plugin Meta Box AIO on your site and re-check this issue. Then it works as well, screen record https://share.getcloudapp.com/BluYw0Qd.

    Please try to upgrade the license to fix this issue by using MB AIO.

    #24848
    Igor Gouvêa
    Participant

    hello Long

    I realized that it worked with Meta Box AIO.

    However, the license I purchased was a Core Extensions Bundle.

    Where do I download the Meta Box AIO? Because it is not on my list of plugins.

    Three days ago I paid for a product that doesn't work. When I bought the package for $
    99 (I live in Brazil and 99 dollars for us is a lot of money, our currency is devalued), the purchase of the AIO was not requested. I ask you to respond faster, so that I can count the investment and work. I am wasting time and money. Because in my understanding I paid for a product that doesn't work. As you can see there is nothing in the environment. Only wordpress and its plugin. And it doesn't work properly.

    Please give me a quick fix. Send the link to download the Meta Box AIO so that it can work.

    I am sure that a company that determines a tool as good as the Meta Box has no interest in causing damage to its customers.

    Thanks

    #24886
    Sam Stout
    Participant

    This is a bug with MB Custom Post Types & Custom Taxonomies (mb-custom-post-type) Version: 2.0.9 the only reason AIO works is because it is still using MB Custom Post Types & Custom Taxonomies Version: 2.0.8

    I have tested this on multiple versions of WordPress and PHP with only mb-builder, meta-box and mb-custom-post-type as the only active plugins. The results are the same the checkboxes are not clickable on the advanced tab in Version: 2.0.9. Please provide a download link MB Custom Post Types & Custom Taxonomies (mb-custom-post-type) Version: 2.0.8.

    Maybe consider pulling MB Custom Post Types & Custom Taxonomies Version: 2.0.9 from the public repo until this bug is fixed as it does not seem to be currently production ready.

    #24887
    Sam Stout
    Participant

    Nevermind I found it. For anyone still experiencing this issue. You can download MB Custom Post Types & Custom Taxonomies Version: 2.0.8 from https://wordpress.org/plugins/mb-custom-post-type/advanced/
    Scroll down to the bottom of the page > change the select box from Development Version to 2.0.8 > Click download

    #24894
    Sam Stout
    Participant

    More info for troubleshooting the bug.

    Steps to reproduce:
    - Clean install of WordPress 5.7
    - Load plugins: Meta Box Version 5.3.9 and MB Custom Post Types & Custom Taxonomies Version: 2.0.9
    - Go to Meta box > Post Types > Add New or existing saved post type > Advanced Tab
    - Click on any unchecked check box

    Expected Behaviour:
    the check box is checked

    What actually happens:
    The check box is highlighted but remains unchecked.
    The following console error is produced:

    react-dom.js?ver=16.13.1:82 Warning: Received NaN for thecheckedattribute. If this is expected, cast the value to a string.
    in input (created by h)
    in label (created by h)
    in div (created by h)
    in div (created by h)
    in h (created by x)
    in x
    in div (created by TabPanel)
    in div (created by TabPanel)
    in TabPanel (created by Y)
    in Y (created by G)
    in s (created by G)
    in G
    printWarning @ react-dom.js?ver=16.13.1:82
    error @ react-dom.js?ver=16.13.1:54
    validateProperty$1 @ react-dom.js?ver=16.13.1:5651
    warnUnknownProperties @ react-dom.js?ver=16.13.1:5718
    validateProperties$2 @ react-dom.js?ver=16.13.1:5742
    validatePropertiesInDevelopment @ react-dom.js?ver=16.13.1:5785
    diffProperties @ react-dom.js?ver=16.13.1:6186
    prepareUpdate @ react-dom.js?ver=16.13.1:7636
    updateHostComponent$1 @ react-dom.js?ver=16.13.1:18919
    completeWork @ react-dom.js?ver=16.13.1:19072
    completeUnitOfWork @ react-dom.js?ver=16.13.1:22324
    performUnitOfWork @ react-dom.js?ver=16.13.1:22300
    workLoopSync @ react-dom.js?ver=16.13.1:22265
    performSyncWorkOnRoot @ react-dom.js?ver=16.13.1:21891
    (anonymous) @ react-dom.js?ver=16.13.1:11224
    unstable_runWithPriority @ react.js?ver=16.13.1:2685
    runWithPriority$1 @ react-dom.js?ver=16.13.1:11174
    flushSyncCallbackQueueImpl @ react-dom.js?ver=16.13.1:11219
    flushSyncCallbackQueue @ react-dom.js?ver=16.13.1:11207
    flushPendingDiscreteUpdates @ react-dom.js?ver=16.13.1:21982
    flushDiscreteUpdates @ react-dom.js?ver=16.13.1:21962
    finishEventHandler @ react-dom.js?ver=16.13.1:761
    batchedEventUpdates @ react-dom.js?ver=16.13.1:795
    dispatchEventForLegacyPluginEventSystem @ react-dom.js?ver=16.13.1:3691
    attemptToDispatchEvent @ react-dom.js?ver=16.13.1:4390
    dispatchEvent @ react-dom.js?ver=16.13.1:4312
    unstable_runWithPriority @ react.js?ver=16.13.1:2685
    runWithPriority$1 @ react-dom.js?ver=16.13.1:11174
    discreteUpdates$1 @ react-dom.js?ver=16.13.1:22022
    discreteUpdates @ react-dom.js?ver=16.13.1:803
    dispatchDiscreteEvent @ react-dom.js?ver=16.13.1:4291

    More info:
    Another console error is produced on page load. This is also present on version 2.0.8 but as far as I can tell it isn't breaking anything:

    Warning:valueprop onselectshould not be null. Consider using an empty string to clear the component orundefinedfor uncontrolled components.
    in select (created by v)
    in div (created by v)
    in div (created by v)
    in v (created by x)
    in x
    in div (created by TabPanel)
    in div (created by TabPanel)
    in TabPanel (created by Y)
    in Y (created by G)
    in r (created by G)
    in G
    printWarning @ react-dom.js?ver=16.13.1:82

Viewing 10 replies - 1 through 10 (of 17 total)
  • You must be logged in to reply to this topic.