Support Forum » User Profile

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 35 total)
  • Author
    Posts
  • in reply to: Search in Advanced Select by Post Meta Value #35882
    Austin PassyAustin Passy
    Participant

    So the answer is no. I will modify the query based on the current object.

    in reply to: Odd Condotional Logic Issues on 1.15.5 #34081
    Austin PassyAustin Passy
    Participant

    Thanks, this better represents our fields: https://pastebin.com/6f5KKpmA

    But I can't create (for testing purposes) ALL the fields across 20+ post types we have that also have conditions. At the current time, it seems the fields I have shared are the only ones affected, so I will continue to look into what the culprit might be.

    Note that our option is an int value, and it only seems to be an issue with 1 so might first thought was a boolean conversion issue with wp_json_encode.

    Thanks for looking. We are not using Oxygen btw.

    in reply to: Odd Condotional Logic Issues on 1.15.5 #34061
    Austin PassyAustin Passy
    Participant

    Diff comparison: https://imgur.com/a/0u8ezns

    in reply to: Odd Condotional Logic Issues on 1.15.5 #33995
    Austin PassyAustin Passy
    Participant

    Okay, I have tracked it down to the changes in the meta-box-conditional-logic class MB_Conditional_Logic from <script type="html/template" to <template.

    At this point I do not know why that is was is breaking my condition, but will have to look into it next week. If you have some insight to add hear please leave your comments.

    in reply to: Odd Condotional Logic Issues on 1.15.5 #33994
    Austin PassyAustin Passy
    Participant

    Thanks, but that is not the case here. I was toggling it on and off just for the video.

    As soon as I revert down to AIO 1.15.3, there is no issue. 1.15.5 there is.

    in reply to: Validation does not work for fields in group #31300
    Austin PassyAustin Passy
    Participant

    Any update on this? Field group validations would be a great addition.

    in reply to: Builder breaks when adding Divider field (in a Group) #24938
    Austin PassyAustin Passy
    Participant

    Video: https://webmshare.com/XEb3J

    in reply to: Builder breaks when adding Divider field (in a Group) #24937
    Austin PassyAustin Passy
    Participant

    Update: I noticed the extra divider that got added to the ending array (I did not add that in the builder). I removed it and the setting page still broke. I then removed the diver in the field group and the page loaded again.

    in reply to: WordPress 5.6.x Conditional Logic issues :hidden #24857
    Austin PassyAustin Passy
    Participant

    Video walk through (expires in 7 days): https://webmshare.com/rVW6x

    in reply to: WordPress 5.6.x Conditional Logic issues :hidden #24856
    Austin PassyAustin Passy
    Participant

    I have tracked down the underlying issue. In WordPress 5.6 (as mentioned above in the steps where it's broken vs working) having a hidden wysiwyg field blocks the publication when that field type is set to required as post meta. Until I toggle the option that shows the wysiwyg and then re-hides it will unblock the validation of required blocker.

    Let me try to get a video attached and follow up if it would help. I will also try to see what might have changed from core WP 5.5.x to 5.6.x with the wp_editor.

    Thanks.

    in reply to: jQuery.Deferred exception: options.ajax is undefined #24654
    Austin PassyAustin Passy
    Participant

    This is an issue with changes in WordPress 5.6. I have changed my post field type from advanced_select with ajax set to false to a standard post select field type to bypass this issue. Since the current fields only have a few options it's OK.

    Will keep an eye out of we run into this in the future though as it's not solved. Just used a workaround.

    in reply to: WordPress 5.6.x Conditional Logic issues :hidden #24653
    Austin PassyAustin Passy
    Participant

    I can confirm it's an issue with WordPress 5.6 with Polylang PRO installed. Still unclear as to the underlying issue. Will confirm as I know more in the coming weeks.

    in reply to: WordPress 5.6.x Conditional Logic issues :hidden #24606
    Austin PassyAustin Passy
    Participant

    I see the following console log (warning):
    JQMIGRATE: jQuery.isNumeric() is deprecated jquery-migrate.js:100:12
    console.trace() jquery-migrate.js:102:13
    jQuery 2
    isLogicCorrect https://.../wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-conditional-logic/conditional-logic.js?ver=1.5:279
    isLogicCorrect https://.../wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-conditional-logic/conditional-logic.js?ver=1.5:224
    runConditionalLogic https://...wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-conditional-logic/conditional-logic.js?ver=1.5:182
    jQuery 2
    runConditionalLogic https://.../wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-conditional-logic/conditional-logic.js?ver=1.5:177
    &lt;anonymous&gt; https://.../wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-conditional-logic/conditional-logic.js?ver=1.5:595
    jQuery 9
    &lt;anonymous&gt; https://.../wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-conditional-logic/conditional-logic.js?ver=1.5:594
    &lt;anonymous&gt; https:/.../wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box-conditional-logic/conditional-logic.js?ver=1.5:604
    <code></code>

    in reply to: Conditional Logic seems broken since update #24605
    Austin PassyAustin Passy
    Participant
    in reply to: Conditional Logic seems broken since update #24603
    Austin PassyAustin Passy
    Participant

    Confirmed working on WordPress 5.5.3 with MB: 5.3.8 & AIO: 1.13.3. So more than likely related to some of the JS changes that came in WordPress 5.6.x, will need to look at the 5.6 Field Guide.

    Maybe related to: ticket/52440?

Viewing 15 posts - 1 through 15 (of 35 total)